Author

Topic: [SOLVED] Stuck Transaction - Major Confusuion (Read 2291 times)

newbie
Activity: 45
Merit: 0
newbie
Activity: 45
Merit: 0
September 28, 2015, 04:15:02 PM
#18
I'm open to whatever works, hehe.  Thanks for all your help guys!  I'm truly overwhelmed!

When I get the coins back, going to start a competition on our website with them and give them away.

Selfless bit of shameless advertising, but hey... Smiley

Check us out in the meantime if you haven't and perhaps you can win some coins when I get them back.

Will announce on twitter and the blog @cryptogrind when doing so.

https://www.cryptogrind.com/

 Grin Roll Eyes
legendary
Activity: 1778
Merit: 1026
Free WSPU2 Token or real dollars
September 28, 2015, 12:45:12 PM
#17
(lol)
We have now the "stuck"
1 stuck = 1 euro.

https://www.facebook.com/lestuckstrasbourg
copper member
Activity: 1498
Merit: 1499
No I dont escrow anymore.
September 28, 2015, 12:42:06 PM
#16
Instead of pushing over and over, wouldn't it be better to let it drop from the mempool? That way you then can spend those coins using a proper fee.

Whatever rjmacarthy prefers I guess. I rebroadcast manually so I can just stop doing so. Should probably be out of the mempool tomorrow.
legendary
Activity: 1358
Merit: 1001
https://gliph.me/hUF
September 28, 2015, 11:14:37 AM
#15
Instead of pushing over and over, wouldn't it be better to let it drop from the mempool? That way you then can spend those coins using a proper fee.
newbie
Activity: 45
Merit: 0
September 28, 2015, 04:19:53 AM
#14
Thanks shorena I have bitcoind installed I will give this a try next time.
copper member
Activity: 1498
Merit: 1499
No I dont escrow anymore.
September 28, 2015, 04:13:30 AM
#13
Transaction was removed from blockchain again, not sure what to do next...?

https://blockchain.info/tx/627740cb96fe41937b08d099d3674a3ed6780bc79dd33b41e9b9bbb8462d4ceb

Thanks.

I gave it a push, should be back. You (or others that want to help out) can do it as well btw. Take the rawtx code from above and copy it e.g. here -> https://blockchain.info/pushtx or here -> https://live.blockcypher.com/btc/pushtx/

Anyone that has access to a full node can do the same either via console:

Code:
sendrawtransaction 010000000107479badde5892c76aad23d8edeccb58f6a9733d7c2841ce2af57b856e5af74800000000fc004730440220130aa44baf6a6b8b21952b02504d221eb1d4682f51783069bda66d63634d879c02201075d22bc266cc16380187e757be87ac24bc81f997ff8c3ee76fd61c1bb85fa901473044022073d956bfeabc209aadf4d73f2f4738b1b1bdf1ed1edf5c6003a3bb736b7a4ed40220089b54ce81be403d1bec99c75602e70be11c6bda04e851ec3cc27ed02b8bcb55014c6952210210c1b41172ccac116a4ccd3bf60aeeb708f1c5af738e78f49b88b1ad784e31e9210237830c6846e0a4c3413dbd3b49bdc28e4f2c174c3677712c8e26d2aec3790286210333f4af2d5a408cf92ba7013d327abb073f3fabc57dfc809103326c2207e4c56a53aeffffffff0242a85e00000000001976a914c3517c5c4436a8ade78a40551c2b2cbc3de4fd7b88ac62fb0400000000001976a914c3517c5c4436a8ade78a40551c2b2cbc3de4fd7b88ac00000000

or if you use a headless server via terminal

Code:
bitcoin-cli sendrawtransaction 010000000107479badde5892c76aad23d8edeccb58f6a9733d7c2841ce2af57b856e5af74800000000fc004730440220130aa44baf6a6b8b21952b02504d221eb1d4682f51783069bda66d63634d879c02201075d22bc266cc16380187e757be87ac24bc81f997ff8c3ee76fd61c1bb85fa901473044022073d956bfeabc209aadf4d73f2f4738b1b1bdf1ed1edf5c6003a3bb736b7a4ed40220089b54ce81be403d1bec99c75602e70be11c6bda04e851ec3cc27ed02b8bcb55014c6952210210c1b41172ccac116a4ccd3bf60aeeb708f1c5af738e78f49b88b1ad784e31e9210237830c6846e0a4c3413dbd3b49bdc28e4f2c174c3677712c8e26d2aec3790286210333f4af2d5a408cf92ba7013d327abb073f3fabc57dfc809103326c2207e4c56a53aeffffffff0242a85e00000000001976a914c3517c5c4436a8ade78a40551c2b2cbc3de4fd7b88ac62fb0400000000001976a914c3517c5c4436a8ade78a40551c2b2cbc3de4fd7b88ac00000000

Bitcoin core does still report a low priority though:

Code:
error: {"code":-26,"message":"66: insufficient priority"}
newbie
Activity: 45
Merit: 0
September 28, 2015, 04:10:29 AM
#12
Transaction was removed from blockchain again, not sure what to do next...?

https://blockchain.info/tx/627740cb96fe41937b08d099d3674a3ed6780bc79dd33b41e9b9bbb8462d4ceb

Thanks.
copper member
Activity: 1498
Merit: 1499
No I dont escrow anymore.
September 27, 2015, 06:22:19 AM
#11
-snip-
If that would help?  That would be great, thanks.

It helps keeping the TX in the mempool, as the input gets older its priority increases and should eventually confirm.
newbie
Activity: 45
Merit: 0
September 27, 2015, 05:21:22 AM
#10
Hi guys, much appreciated.

The transaction is about 10 days old now.

However, the transaction has been re-broadcasted today:

https://blockchain.info/tx/627740cb96fe41937b08d099d3674a3ed6780bc79dd33b41e9b9bbb8462d4ceb

I will wait to see if it confirms this time.

Thanks.

If you want I can rebroadcast it from time to time.

raw tx:
Code:
010000000107479badde5892c76aad23d8edeccb58f6a9733d7c2841ce2af57b856e5af74800000000fc004730440220130aa44baf6a6b8b21952b02504d221eb1d4682f51783069bda66d63634d879c02201075d22bc266cc16380187e757be87ac24bc81f997ff8c3ee76fd61c1bb85fa901473044022073d956bfeabc209aadf4d73f2f4738b1b1bdf1ed1edf5c6003a3bb736b7a4ed40220089b54ce81be403d1bec99c75602e70be11c6bda04e851ec3cc27ed02b8bcb55014c6952210210c1b41172ccac116a4ccd3bf60aeeb708f1c5af738e78f49b88b1ad784e31e9210237830c6846e0a4c3413dbd3b49bdc28e4f2c174c3677712c8e26d2aec3790286210333f4af2d5a408cf92ba7013d327abb073f3fabc57dfc809103326c2207e4c56a53aeffffffff0242a85e00000000001976a914c3517c5c4436a8ade78a40551c2b2cbc3de4fd7b88ac62fb0400000000001976a914c3517c5c4436a8ade78a40551c2b2cbc3de4fd7b88ac00000000

If that would help?  That would be great, thanks.
copper member
Activity: 1498
Merit: 1499
No I dont escrow anymore.
September 26, 2015, 06:32:10 AM
#9
Hi guys, much appreciated.

The transaction is about 10 days old now.

However, the transaction has been re-broadcasted today:

https://blockchain.info/tx/627740cb96fe41937b08d099d3674a3ed6780bc79dd33b41e9b9bbb8462d4ceb

I will wait to see if it confirms this time.

Thanks.

If you want I can rebroadcast it from time to time.

raw tx:
Code:
010000000107479badde5892c76aad23d8edeccb58f6a9733d7c2841ce2af57b856e5af74800000000fc004730440220130aa44baf6a6b8b21952b02504d221eb1d4682f51783069bda66d63634d879c02201075d22bc266cc16380187e757be87ac24bc81f997ff8c3ee76fd61c1bb85fa901473044022073d956bfeabc209aadf4d73f2f4738b1b1bdf1ed1edf5c6003a3bb736b7a4ed40220089b54ce81be403d1bec99c75602e70be11c6bda04e851ec3cc27ed02b8bcb55014c6952210210c1b41172ccac116a4ccd3bf60aeeb708f1c5af738e78f49b88b1ad784e31e9210237830c6846e0a4c3413dbd3b49bdc28e4f2c174c3677712c8e26d2aec3790286210333f4af2d5a408cf92ba7013d327abb073f3fabc57dfc809103326c2207e4c56a53aeffffffff0242a85e00000000001976a914c3517c5c4436a8ade78a40551c2b2cbc3de4fd7b88ac62fb0400000000001976a914c3517c5c4436a8ade78a40551c2b2cbc3de4fd7b88ac00000000
newbie
Activity: 45
Merit: 0
September 26, 2015, 06:18:01 AM
#8
Hi guys, much appreciated.

The transaction is about 10 days old now.

However, the transaction has been re-broadcasted today:

https://blockchain.info/tx/627740cb96fe41937b08d099d3674a3ed6780bc79dd33b41e9b9bbb8462d4ceb

I will wait to see if it confirms this time.

Thanks.

copper member
Activity: 1498
Merit: 1499
No I dont escrow anymore.
September 26, 2015, 03:56:52 AM
#7
If you can... wait for some time to show it at blockchain... it's not uncommon for transactions to not appear as soon as you make them... hope you get it solved soon...

Its actually quite common for a TX to not show on blockchain.info due to some filters they have in place. Others show the TX just fine and so does bc.i now.

The question still remains how to double spend the TX and I cant help you with that OP because I dont know whether bitcore rebroadcasts the transaction and how to stop it. You essentially have two options.

You can wait until your TX has a high enough priority to be accepted without fee. A very rough estimate[2] for that would be to wait for ~2400 confirmations on the input[1] you use. The inputs currently has ~1500 confirmations, thus you would have to wait ~900*10 minutes or 6-7 days. This will only work if the TX is constantly rebroadcasted though to make sure miners do not forget about it.

The other options is to make sure the network forgets about the TX and use the input in a TX that pays a fee. For this you have to find out how to stop broadcasting the TX.

The third option would be to try child pays for parent (CPFP). You use the unconfirmed output of your transaction as an input in a new transaction a pay a higher than normal fee. AFAIK next to no miners have implemented CPFP yet, thus it might only complicate things further.


[1] https://www.blocktrail.com/BTC/tx/48f75a6e857bf52ace41287c3d73a9f658cbecedd823ad6ac79258dead9b4707
[2] based on the "bitcoin day", 1 BTC, 1 day worth of confirmations (144).
member
Activity: 87
Merit: 10
September 26, 2015, 03:47:23 AM
#6
Wait some time. The transactions would probably dispear from the mempool. Then you money will come back to you. Now you could have a look at here https://www.blocktrail.com/BTC/tx/627740cb96fe41937b08d099d3674a3ed6780bc79dd33b41e9b9bbb8462d4ceb
Confirmations status is REMOVED / EXPIRED
You will see your coins soon.
member
Activity: 114
Merit: 10
if i can't save earth, i'll damn sure avenge it
September 26, 2015, 03:40:53 AM
#5
If you can... wait for some time to show it at blockchain... it's not uncommon for transactions to not appear as soon as you make them... hope you get it solved soon...
newbie
Activity: 45
Merit: 0
September 25, 2015, 05:48:36 PM
#4
- snip -
using Bitcore,
- snip -

I assume you mean Bitcoin Core?

If so, then it should remember the transactions that it previously broadcast, and if they aren't confirmed, it should re-broadcast them again after a few days.  Bitcoin Core should continue to re-broadcast its unconfirmed transactions forever until they get confirmed.

There are some tools (such as pywallet) that can be used to remove the transaction from Bitcoin Core's wallet so that it won't keep broadcasting them and it is aware that the outputs are still unspent.

If you don't want to use pywallet, then you could create a backup of your wallet, and then dump all the private keys from the wallet.  Then you could delete the wallet.dat that's in the data directory so that Bitcoin Core creates a new empty wallet.  You could then import all the private keys from the old wallet.  Then the new wallet would have access to all the same addresses as the old wallet, but it wouldn't have the unconfirmed transaction.

While the idea is good, its easier with 0.11. now. You can remove all transactions from the wallet and rescan it by starting it with -zapwallettxes. It must be properly shut down in advance to avoid other issues.

That way you can keep the wallet file and dont have to use pywallet either. It will keep all labels and meta data (unless you use -zapwallettxes=2), but no longer be limited by the unconfirmed transaction. It will not rebroadcast it and after enough time has passed OP should be able to issue a new TX with the same inputs.

Thanks for the replies guys.

No, I actually mean http://bitcore.io/ (Bitcore)  I wrote a Javscript app which can build raw transactions and broadcast them with http://bitcore.io/guide/module/explorers/.

Basically like this: http://bitcore.io/guide/#Create_a_Transaction

I have the 3 private keys, but need to sweep the funds somehow out of the Multisig address.  However insight api thinks there are no unspent outputs for the address, so I am stuck.

Thanks.

 
copper member
Activity: 1498
Merit: 1499
No I dont escrow anymore.
September 25, 2015, 04:48:23 PM
#3
- snip -
using Bitcore,
- snip -

I assume you mean Bitcoin Core?

If so, then it should remember the transactions that it previously broadcast, and if they aren't confirmed, it should re-broadcast them again after a few days.  Bitcoin Core should continue to re-broadcast its unconfirmed transactions forever until they get confirmed.

There are some tools (such as pywallet) that can be used to remove the transaction from Bitcoin Core's wallet so that it won't keep broadcasting them and it is aware that the outputs are still unspent.

If you don't want to use pywallet, then you could create a backup of your wallet, and then dump all the private keys from the wallet.  Then you could delete the wallet.dat that's in the data directory so that Bitcoin Core creates a new empty wallet.  You could then import all the private keys from the old wallet.  Then the new wallet would have access to all the same addresses as the old wallet, but it wouldn't have the unconfirmed transaction.

While the idea is good, its easier with 0.11. now. You can remove all transactions from the wallet and rescan it by starting it with -zapwallettxes. It must be properly shut down in advance to avoid other issues.

That way you can keep the wallet file and dont have to use pywallet either. It will keep all labels and meta data (unless you use -zapwallettxes=2), but no longer be limited by the unconfirmed transaction. It will not rebroadcast it and after enough time has passed OP should be able to issue a new TX with the same inputs.
sr. member
Activity: 499
Merit: 250
September 25, 2015, 01:08:41 PM
#2
Nothing to confusuion may be server error check it in another blockchain site or wait a some time all it ill be fine
newbie
Activity: 45
Merit: 0
September 25, 2015, 12:28:59 PM
#1
Hi Guys,  wonder if anyone can help with this:  I sent a transaction without a fee by accident.

Check this out:

Transaction ID : 627740cb96fe41937b08d099d3674a3ed6780bc79dd33b41e9b9bbb8462d4ceb

Showing here:

https://insight.bitpay.com/tx/627740cb96fe41937b08d099d3674a3ed6780bc79dd33b41e9b9bbb8462d4ceb

But not here:

https://blockchain.info/search?search=627740cb96fe41937b08d099d3674a3ed6780bc79dd33b41e9b9bbb8462d4ceb

I sent this using a test app I wrote in Javascript using Bitcore, the address is a multisig address of which I have all the keys.

https://blockchain.info/address/39j4kyz9gjhW4V1zqMCtGZFE48LaP3KCDb

Is there any way to get the funds back?

Unspent transactions can be found here:

http://btc.blockr.io/api/v1/address/unspent/39j4kyz9gjhW4V1zqMCtGZFE48LaP3KCDb

But here they dont show:

http://bitcore.io/playground/#/unspent

Whats the deal with this?

Thanks.

Richard.

Jump to: