|
Title: Blockchain.info Transaction Confirmation Failed Post by: btctr4d3r on July 08, 2013, 03:46:40 PM Hello,
I tried to send BTC from my Blockchain.info account to another on 28 of June: https://blockchain.info/tx/66b6bcc0554a88849e2117fd709db0c0256235cb907e1426b1156e04cd60e640 The transaction already failed a bunch of times, the BTC is sent back to my Blockchain.info account but a few hours later it tries again. Is there any way to cancel this transaction altogether? What can I do beside waiting for it to be confirmed? Best regards, btctr4d3r Title: Re: Blockchain.info Transaction Confirmation Failed Post by: fraenk on July 08, 2013, 05:01:18 PM i think i read somewhere that blockchain.info will stop repopulating the transaction after some time... but i am unable to find the link!
also (beware, purely theoretical and may go wrong), after the tx fails, you could try creating a new valid transaction with the same inputs... your "old" transaction should be then denied when it repropagates due to double spend ?! good luck... P.S.: looks like faucet dust?! sucks! Title: Re: Blockchain.info Transaction Confirmation Failed Post by: fraenk on July 08, 2013, 05:03:36 PM you could also try contacting piuk (https://bitcointalk.org/index.php?action=profile;u=17928 (https://bitcointalk.org/index.php?action=profile;u=17928)) who is running blockchain.info directly!
not sure if he will answer though... sure he's a busy person! Title: Re: Blockchain.info Transaction Confirmation Failed Post by: Stephen Gornick on July 08, 2013, 07:11:26 PM What can I do beside waiting for it to be confirmed? The size of the transaction is a little over 35K. "the reference implementation will round up the transaction size to the nearest thousand bytes and then add a fee of - http://en.bitcoin.it/wiki/Transaction_fees Your fee paid of 0.0035 is [Edit: v0.8.2 and above the fee is 0.0001 BTC per 1K]. Title: Re: Blockchain.info Transaction Confirmation Failed Post by: DannyHamilton on July 08, 2013, 07:16:58 PM What can I do beside waiting for it to be confirmed? The size of the transaction is a little over 35K. "the reference implementation will round up the transaction size to the nearest thousand bytes and then add a fee of 0.0005 BTC per thousand bytes" - http://en.bitcoin.it/wiki/Transaction_fees Your fee paid of 0.0035 is way too low. Pay 0.018 BTC (calculated using 36K X 0.0005 BTC, which is worth under $1.50) and the transaction will likely confirm. It sounds like the OP is already aware of "why" it isn't confirming. Their question is what to do about it now that the transaction has already been created and sent. Your advice of: Quote Your fee paid of 0.0035 is way too low. Pay 0.018 BTC Doesn't really give any information about how to modify an existing transaction with a 0.0035 BTC fee and change that fee to 0.018 BTC. Title: Re: Blockchain.info Transaction Confirmation Failed Post by: malevolent on July 08, 2013, 07:20:51 PM What can I do beside waiting for it to be confirmed? The size of the transaction is a little over 35K. "the reference implementation will round up the transaction size to the nearest thousand bytes and then add a fee of 0.0005 BTC per thousand bytes" - http://en.bitcoin.it/wiki/Transaction_fees Your fee paid of 0.0035 is way too low. Pay 0.018 BTC (calculated using 36K X 0.0005 BTC, which is worth under $1.50) and the transaction will likely confirm. What? I thought it was 0.0001 BTC per kB now, so in this case it should be 0.0036 BTC. Title: Re: Blockchain.info Transaction Confirmation Failed Post by: DannyHamilton on July 08, 2013, 07:25:35 PM What? I thought it was 0.0001 BTC per kB now, so in this case it should be 0.0036 BTC. That depends on how many users have upgraded to rules in the latest reference client. If many people are still running older clients, then their clients will continue to refuse to relay transactions that pay less than 0.0005 BTC. It's not clear how many miners have adjusted to the new fee structure yet as well. Title: Re: Blockchain.info Transaction Confirmation Failed Post by: Stephen Gornick on July 09, 2013, 03:44:42 AM What? I thought it was 0.0001 BTC per kB now, so in this case it should be 0.0036 BTC. Thanks, I updated the Wiki page to reflect the new fee. Incidentally, the size gets rounded up, so the number used for the calculation if there is even one byte over 35K means 36 is the needed value. Your fee was 0.0035 so the logic in the code would by default leave your transaction as low priority. Doesn't really give any information about how to modify an existing transaction with a 0.0035 BTC fee and change that fee to 0.018 BTC. There is no way to modify the fee for an existing transaction. If it was sent using Blockchain.info, eventually it will stop retrying and the funds will again show as spendable. Is suppose what could be attempted is to take one of the inputs and try to double spend it: - https://blockchain.info/create-double-spend Then that would invalidate this transaction, causing the funds to immediately become spendable once again. |