HUGE shoutout to Poolin for helping, and claiming the 1 BTC bounty.
Resolved.
Once again, thanks to Poolin and Alejandro (bitentrepreneur) for the help.
Topic: [~1 BTC Bounty] (Read 4751 times)
i am not too sure what you all are on about, but we mined the 'stuck' tx and got the bounty (if that's what you all are wondering about)
Out of curiosity, where did you get the TX?
i am not too sure what you all are on about, but we mined the 'stuck' tx and got the bounty (if that's what you all are wondering about)
But the mined transaction has different TXID, input and output amount than the one you've been broadcast(ing).
Chances is OP gave a different signed raw txn to "neutraLTC", it also contains a 1BTC output which looks like the bounty.
Chances is OP gave a different signed raw txn to "neutraLTC", it also contains a 1BTC output which looks like the bounty.
Yes, I have been wondering about that - perhaps they came and grabbed the first version of the TX and tried it and it worked (especially with the much higher than usual number of transactions in mempool at the moment).
The OP has been offline for two day - no doubt because they were exposed as a mult-alt scammer, so I doubt anyone will get any kind of thanks.
A bit OT but it's interesting that a lot of the smaller pools didn't step in to help.
Would have figured that one of the smaller ones, like Kano or CK that leaving it in their would have been a nice bump when they found a block.
Congrats to the OP on finally getting this done.
Can't believe that I have been reading and posting here since October of last year.
-Dave
Would have figured that one of the smaller ones, like Kano or CK that leaving it in their would have been a nice bump when they found a block.
Congrats to the OP on finally getting this done.
Can't believe that I have been reading and posting here since October of last year.
-Dave
Told you it isn't worth-it.
-snip-
As no-one else is claiming to have helped, I claim the $1,000 in bitcoin that the OP promised me for continually posting the TX:
Chances is OP gave a different signed raw txn to "neutraLTC", it also contains a 1BTC output which looks like the bounty.
BTW, you're still at my "isn't worth-it" comment
It's about the chance of being mined through re-brodcasting it to blockcypher, I have a reply a few weeks before that post so I thought you've already seen it after you edited your reply.
Sorry about not linking it sooner.
How can there be a slim chance? Should I keep re-broadcasting in hopes that a small miner would accept it?
Yes,Since 150+ nodes are still accepting it, there's a 'very very slim' chance that it will get into a mining nodes' mempool (that also accepts such transactions).
But re-broadcasting it after getting dropped isn't worth it, IMO.
Told you it isn't worth-it.
Confirmed with my own full node client. It took about 1 year 2 months to solve OP's problem, but at least Bitcoin prices currently at it's ATH (All time high).
OP, be careful with anyone who contact you since it's possible they're scammer who aim to steal your Bitcoin.
OP, be careful with anyone who contact you since it's possible they're scammer who aim to steal your Bitcoin.
As no-one else is claiming to have helped, I claim the $1,000 in bitcoin that the OP promised me for continually posting the TX:
Right now if the transaction that is continually broadcasted on Blockcypher is mined, Timelord receives the agreed bounty. I am not in need of anyone else to do what Timelord is doing at the current moment, but if Timelord gives up, I may talk to you privately.
Edit: As @nc50lc said, it's not a problem to figure out who mined it - and I'm not offering an extra bounty besides the transaction fee to any miners unless they contact me directly beforehand.
Edit: As @nc50lc said, it's not a problem to figure out who mined it - and I'm not offering an extra bounty besides the transaction fee to any miners unless they contact me directly beforehand.
Thank you in advance for your generosity.
Poolin.com has mined the transaction: https://explorer.poolin.com/tx/fd02fd81790a05ea2ab07bbcf5cdcb2cfd21f3f5676a5c0e8f7f5ca2ac75e694
if anyone else has any issues with a transaction please reach out to me for help.
Confirmed:
bc1q3lxgmg975we262tmfnsmwfa4gjt4kprpgcgvds 0.04836
Poolin.com has mined the transaction: https://explorer.poolin.com/tx/fd02fd81790a05ea2ab07bbcf5cdcb2cfd21f3f5676a5c0e8f7f5ca2ac75e694
if anyone else has any issues with a transaction please reach out to me for help.
I was having those "500 error" issues again during the week, but have just rebroadcast (and have reached out to someone for their help).
Will advise if anything comes of it.
Will advise if anything comes of it.
Has the problem of Leventturksoy been solved?
No. I encountered the same problem as you, do you have a solution to this problem？
Post your RAW Transaction and I'll accelerate it for you.
This is a problem encountered by my friend, and I will tell him to sign the transaction. Has the problem of Leventturksoy been solved?
I encountered the same problem as you, do you have a solution to this problem？
Post your RAW Transaction and I'll accelerate it for you.
If you havent found solution yet I might have a way with a big Pool that already confirmed me that could work it out.
Sent you a DM
Sent you a DM
Hi,I ran into the same problem. Can you tell me how to solve it？Thanks.
How is that possible? Please explain.
I encountered the same problem as you, do you have a solution to this problem？
If you havent found solution yet I might have a way with a big Pool that already confirmed me that could work it out.
Sent you a DM
Sent you a DM
Hi,I ran into the same problem. Can you tell me how to solve it？Thanks.
How is that possible? Please explain.
If you havent found solution yet I might have a way with a big Pool that already confirmed me that could work it out.
Sent you a DM
Sent you a DM
Hi,I ran into the same problem. Can you tell me how to solve it？Thanks.
If you havent found solution yet I might have a way with a big Pool that already confirmed me that could work it out.
Sent you a DM
Sent you a DM
It is better to create a separate signed transaction to move funds from stuck address to your target new address AND bitcoin address of the "tx pusher". In case of success you will have your funds on your new address, and the "tx pusher" will receive his bounty to his bitcoin address (as both outputs will be in the same transaction).
That's a bad idea. It's likely these funds will be stuck for many more years, and each signed transaction will remain equally valid. Once a signed transaction is out there, it can't be invalidated until OP manages to move his funds.Besides, it will mean trying to double spend on top of the current problem.
Probably you are right here. I wrote that from the position that all the transactions are not accepted by the network. However at this moment we have the case that the spending transaction is in blockcypher:
Code:
https://live.blockcypher.com/btc/tx/7da3515aa3a7492b9e99ef95b7a3e7bbaf500c474de68b3dc4c756d18729abdd/
However this transaction is not in blockchain.com and others. So, yes, different transactions posted in different places could compete with each other and stuck for much longer period of time.
OK, am back in business - https://live.blockcypher.com/btc/tx/7da3515aa3a7492b9e99ef95b7a3e7bbaf500c474de68b3dc4c756d18729abdd/ (every time I've re-broadcast it, the "confidence" has always been at or above 47-51%) - it looks like the error was only a temporary thing.
Fees are much lower now as evidenced by this guide: https://bitcoinfees.earn.com/ (it's a guide people)
The OP's already "double spent" these funds as there's a "fee too high" version and the current one I've been bumping without success. Have a look at the unedited version of the OP, the rawtransaction look very similar to each-other.
Fees are much lower now as evidenced by this guide: https://bitcoinfees.earn.com/ (it's a guide people)
Besides, it will mean trying to double spend on top of the current problem.
The OP's already "double spent" these funds as there's a "fee too high" version and the current one I've been bumping without success. Have a look at the unedited version of the OP, the rawtransaction look very similar to each-other.
It is better to create a separate signed transaction to move funds from stuck address to your target new address AND bitcoin address of the "tx pusher". In case of success you will have your funds on your new address, and the "tx pusher" will receive his bounty to his bitcoin address (as both outputs will be in the same transaction).
That's a bad idea. It's likely these funds will be stuck for many more years, and each signed transaction will remain equally valid. Once a signed transaction is out there, it can't be invalidated until OP manages to move his funds.Besides, it will mean trying to double spend on top of the current problem.
even if this method was desired a better bitcoin-ier way would be to use the cryptography option that bitcoin already offers.
the goal is to make two outputs, one to the owner and one to the one who claims the reward. that is the very definition of SIGHASH_SINGLE. you sign the input and the corresponding output of it (the fist output since there is only one input) and set the amount of it to the (total input value - tx fee - reward) then the person claiming the reward simply adds the new output equal to (reward) amount and then submits it to the block.
Jump to: