I meant look at the miners. This industry consume a lot energy and network still overloaded. Imagine if everyone would have some bits. Whats then days of waiting or priority fees?
We want it to be spread worldwide but even now network is overloaded with payments
Topic: output is more than input. will it get confirmed? (Read 1102 times)
Looks like i just lost 140€ due to overloaded network.
Nonsense. You "lost" 140€ due to not knowing what you are doing, and sending a transaction that you now don't want sent.
I think I will use another coin like monero soon.
Good luck with that.
As bitcoin Is non economical at all
Non-economical? The smaller the amount you want to send, the less economical it becomes. For anything more than a few Euros worth, I've found it to be plenty economical.
I have found this in multIbit HD section..
Replace-by-fee (RBF) transactions
A change to Bitcoin Core in version 0.12+ involves replace-by-fee transaction support. RBF is an optional extension to a standard Bitcoin transaction that permits the sender to perform a repeat broadcast of an earlier failed transaction with a higher fee attached. Typically this is to "free up" an earlier transaction that has been accepted into the network as valid but because the fee is too low is being ignored by miners. Repeating the transaction with a higher fee allows the sender to override the earlier transaction in the hope that the miners will add it to a block.
MultiBit does not currently support the creation of these types of transactions and relies instead on setting an appropriate fee to the transaction to ensure timely inclusion.
RBF allows for your transaction to be replaced only if it is marked as replaceable. If the transaction is not tagged, nodes will ignore any other transactions spending the same input as another transaction in their mempool. Since you do not have it, RBF is not possible unless you can find a miner that is willing to do so for you. Try asking user macbook-air. Replace-by-fee (RBF) transactions
A change to Bitcoin Core in version 0.12+ involves replace-by-fee transaction support. RBF is an optional extension to a standard Bitcoin transaction that permits the sender to perform a repeat broadcast of an earlier failed transaction with a higher fee attached. Typically this is to "free up" an earlier transaction that has been accepted into the network as valid but because the fee is too low is being ignored by miners. Repeating the transaction with a higher fee allows the sender to override the earlier transaction in the hope that the miners will add it to a block.
MultiBit does not currently support the creation of these types of transactions and relies instead on setting an appropriate fee to the transaction to ensure timely inclusion.
I have found this in multIbit HD section..
Replace-by-fee (RBF) transactions
A change to Bitcoin Core in version 0.12+ involves replace-by-fee transaction support. RBF is an optional extension to a standard Bitcoin transaction that permits the sender to perform a repeat broadcast of an earlier failed transaction with a higher fee attached. Typically this is to "free up" an earlier transaction that has been accepted into the network as valid but because the fee is too low is being ignored by miners. Repeating the transaction with a higher fee allows the sender to override the earlier transaction in the hope that the miners will add it to a block.
MultiBit does not currently support the creation of these types of transactions and relies instead on setting an appropriate fee to the transaction to ensure timely inclusion.
Replace-by-fee (RBF) transactions
A change to Bitcoin Core in version 0.12+ involves replace-by-fee transaction support. RBF is an optional extension to a standard Bitcoin transaction that permits the sender to perform a repeat broadcast of an earlier failed transaction with a higher fee attached. Typically this is to "free up" an earlier transaction that has been accepted into the network as valid but because the fee is too low is being ignored by miners. Repeating the transaction with a higher fee allows the sender to override the earlier transaction in the hope that the miners will add it to a block.
MultiBit does not currently support the creation of these types of transactions and relies instead on setting an appropriate fee to the transaction to ensure timely inclusion.
So it mean I can pay 0 fee everytime I send BTC and it still get confirmed one day?
It is entirely possible. So long as a transaction is broadcast, there is always the possibility for it to be confirmed.So how to STOP broadcasting it?
Your only option to "cancel" the transaction is to create a double spend which spends the same input but to an output that you control.
If anyone could explain me how to double spend using Multibit I will pay 0.05 reward
I am not sure what seed generation method Multibit uses or else I can derive the private key and make a replacement transaction. You can try to stop and refrain from opening Multibit for several days and import the seed to another computer with a new installation.
[1]https://multibit.org/help/hd0.4/send-bitcoin.html
Looks like i just lost 140€ due to overloaded network.. I think I will use another coin like monero soon. As bitcoin Is non economical at all
Both of the transactions have several inputs and the total output amount is less than the input amount so you paid a fee and it satisfy the protocol rules.
However, other than the significantly low fees when compared to the average fee in the mempool, the transaction [1] spends an input[2] that is unconfirmed. Hence, the transaction[2] MUST BE to confirmed first before transaction [1] will confirm. They can be included in the same or different blocks.
[1] d8d6ec17b102812f0d989b469fce1993b22e7ea13a5fa5fa401f27d5d8fdf24f
[2] 5005f2baa7170c13ce5e104c7cd238479b75197b4aa32434963d06fd9625229f
However, other than the significantly low fees when compared to the average fee in the mempool, the transaction [1] spends an input[2] that is unconfirmed. Hence, the transaction[2] MUST BE to confirmed first before transaction [1] will confirm. They can be included in the same or different blocks.
[1] d8d6ec17b102812f0d989b469fce1993b22e7ea13a5fa5fa401f27d5d8fdf24f
[2] 5005f2baa7170c13ce5e104c7cd238479b75197b4aa32434963d06fd9625229f
is there a chance that it won't get confirmed as the deal i have paid for is closed.
how can i stop broadcasting that?
I see a "high priority" that is said from some internal Blockchain.info calculation. It will eventualy get confirmed, it may take a bit longer, but it will.
No need to stop broadcasting it.
I do not want it confirmed, because the deal I was paying is not active anymore.
So I do ask again, is there any chance I could stop broadcasting it and get dumped in mempool?
Sorry for my misunderstanding, I think there's no way to achieve that. The transaction will be confirmed.
EDIT
Ok, didn't know about the double-spend. Think it's time for me to leave this conversation
So it mean I can pay 0 fee everytime I send BTC and it still get confirmed one day?
It is entirely possible. So long as a transaction is broadcast, there is always the possibility for it to be confirmed.So how to STOP broadcasting it?
Your only option to "cancel" the transaction is to create a double spend which spends the same input but to an output that you control.
If anyone could explain me how to double spend using Multibit I will pay 0.05 reward
So it mean I can pay 0 fee everytime I send BTC and it still get confirmed one day?
It is entirely possible. So long as a transaction is broadcast, there is always the possibility for it to be confirmed.So how to STOP broadcasting it?
Your only option to "cancel" the transaction is to create a double spend which spends the same input but to an output that you control.
So it mean I can pay 0 fee everytime I send BTC and it still get confirmed one day?
It is entirely possible. So long as a transaction is broadcast, there is always the possibility for it to be confirmed.So how to STOP broadcasting it?
So it mean I can pay 0 fee everytime I send BTC and it still get confirmed one day?
It is entirely possible. So long as a transaction is broadcast, there is always the possibility for it to be confirmed.I was using MultibitHD do sending payment. And I am not sure how to find my private key or how to double spend using this wallet.. Please help
IIRC MultiBit makes it difficult to do advanced Bitcoin stuff. I think there is an option to clear all unconfirmed transactions (repair wallet or something like that) and then you can make the double spend.
So it mean I can pay 0 fee everytime I send BTC and it still get confirmed one day?
I was using MultibitHD do sending payment. And I am not sure how to find my private key or how to double spend using this wallet.. Please help
I was using MultibitHD do sending payment. And I am not sure how to find my private key or how to double spend using this wallet.. Please help
Mate, you do not read what I wrote.
I do not want it confirmed, because the deal I was paying is not active anymore.
So I do ask again, is there any chance I could stop broadcasting it and get dumped in mempool?
No. You can attempt a double spend but there is no guarantee that the double spend will work. I do not want it confirmed, because the deal I was paying is not active anymore.
So I do ask again, is there any chance I could stop broadcasting it and get dumped in mempool?
Both of the transactions have several inputs and the total output amount is less than the input amount so you paid a fee and it satisfy the protocol rules.
However, other than the significantly low fees when compared to the average fee in the mempool, the transaction [1] spends an input[2] that is unconfirmed. Hence, the transaction[2] MUST BE to confirmed first before transaction [1] will confirm. They can be included in the same or different blocks.
[1] d8d6ec17b102812f0d989b469fce1993b22e7ea13a5fa5fa401f27d5d8fdf24f
[2] 5005f2baa7170c13ce5e104c7cd238479b75197b4aa32434963d06fd9625229f
However, other than the significantly low fees when compared to the average fee in the mempool, the transaction [1] spends an input[2] that is unconfirmed. Hence, the transaction[2] MUST BE to confirmed first before transaction [1] will confirm. They can be included in the same or different blocks.
[1] d8d6ec17b102812f0d989b469fce1993b22e7ea13a5fa5fa401f27d5d8fdf24f
[2] 5005f2baa7170c13ce5e104c7cd238479b75197b4aa32434963d06fd9625229f
is there a chance that it won't get confirmed as the deal i have paid for is closed.
how can i stop broadcasting that?
I see a "high priority" that is said from some internal Blockchain.info calculation. It will eventualy get confirmed, it may take a bit longer, but it will.
No need to stop broadcasting it.
I do not want it confirmed, because the deal I was paying is not active anymore.
So I do ask again, is there any chance I could stop broadcasting it and get dumped in mempool?
Both of the transactions have several inputs and the total output amount is less than the input amount so you paid a fee and it satisfy the protocol rules.
However, other than the significantly low fees when compared to the average fee in the mempool, the transaction [1] spends an input[2] that is unconfirmed. Hence, the transaction[2] MUST BE to confirmed first before transaction [1] will confirm. They can be included in the same or different blocks.
[1] d8d6ec17b102812f0d989b469fce1993b22e7ea13a5fa5fa401f27d5d8fdf24f
[2] 5005f2baa7170c13ce5e104c7cd238479b75197b4aa32434963d06fd9625229f
However, other than the significantly low fees when compared to the average fee in the mempool, the transaction [1] spends an input[2] that is unconfirmed. Hence, the transaction[2] MUST BE to confirmed first before transaction [1] will confirm. They can be included in the same or different blocks.
[1] d8d6ec17b102812f0d989b469fce1993b22e7ea13a5fa5fa401f27d5d8fdf24f
[2] 5005f2baa7170c13ce5e104c7cd238479b75197b4aa32434963d06fd9625229f
is there a chance that it won't get confirmed as the deal i have paid for is closed.
how can i stop broadcasting that?
I see a "high priority" that is said from some internal Blockchain.info calculation. It will eventualy get confirmed, it may take a bit longer, but it will.
No need to stop broadcasting it.
Both of the transactions have several inputs and the total output amount is less than the input amount so you paid a fee and it satisfy the protocol rules.
However, other than the significantly low fees when compared to the average fee in the mempool, the transaction [1] spends an input[2] that is unconfirmed. Hence, the transaction[2] MUST BE to confirmed first before transaction [1] will confirm. They can be included in the same or different blocks.
[1] d8d6ec17b102812f0d989b469fce1993b22e7ea13a5fa5fa401f27d5d8fdf24f
[2] 5005f2baa7170c13ce5e104c7cd238479b75197b4aa32434963d06fd9625229f
However, other than the significantly low fees when compared to the average fee in the mempool, the transaction [1] spends an input[2] that is unconfirmed. Hence, the transaction[2] MUST BE to confirmed first before transaction [1] will confirm. They can be included in the same or different blocks.
[1] d8d6ec17b102812f0d989b469fce1993b22e7ea13a5fa5fa401f27d5d8fdf24f
[2] 5005f2baa7170c13ce5e104c7cd238479b75197b4aa32434963d06fd9625229f
is there a chance that it won't get confirmed as the deal i have paid for is closed.
how can i stop broadcasting that?
Both of the transactions have several inputs and the total output amount is less than the input amount so you paid a fee and it satisfy the protocol rules.
However, other than the significantly low fees when compared to the average fee in the mempool, the transaction [1] spends an input[2] that is unconfirmed. Hence, the transaction[2] MUST BE to confirmed first before transaction [1] will confirm. They can be included in the same or different blocks.
[1] d8d6ec17b102812f0d989b469fce1993b22e7ea13a5fa5fa401f27d5d8fdf24f
[2] 5005f2baa7170c13ce5e104c7cd238479b75197b4aa32434963d06fd9625229f
However, other than the significantly low fees when compared to the average fee in the mempool, the transaction [1] spends an input[2] that is unconfirmed. Hence, the transaction[2] MUST BE to confirmed first before transaction [1] will confirm. They can be included in the same or different blocks.
[1] d8d6ec17b102812f0d989b469fce1993b22e7ea13a5fa5fa401f27d5d8fdf24f
[2] 5005f2baa7170c13ce5e104c7cd238479b75197b4aa32434963d06fd9625229f
Your transaction fees are extremely low, so those transactions will likely take several hours to confirm. What wallet are you using?
Multibit HD , standart fees are set.
2 days already...
What are talking about?
input is 0.21 , output is more than that.Multibit HD , standart fees are set.
2 days already...
Looks like my outputs are bigger than inputs.
What are talking about?check incoming and outgoing transactions
Your transaction fees are extremely low, so those transactions will likely take several hours to confirm. What wallet are you using?
What are talking about?
Looks like my outputs are bigger than inputs.
What are talking about?
https://blockchain.info/address/14G7xx9xgk8arbkTfZvvf7p87XFy2Dx1oR
Looks like my outputs are bigger than inputs.
will it be confirmed or rejected by network?
it was seen by 60 peers and no confirmation yet
Looks like my outputs are bigger than inputs.
will it be confirmed or rejected by network?
it was seen by 60 peers and no confirmation yet
Jump to: