How to return stuck transaction (instead of pushing it to receiver's addres) ? - page 2.

mocacinno

legendary

Activity: 3584

Merit: 5243

https://merel.mobi => buy facemasks with BTC/LTC

Quote from: EarnOnVictor on September 26, 2022, 03:36:10 AM

This time is too long, I would advise you to forget about the transaction. I know it's because of the current higher value of Bitcoin that makes you feel concerned, but you have to let go, the technology then is not like today because the wallet you used for the transaction matters which you did not mention in your explanation.

I'm glad you now know better, Opt-In Replace-by-Fee is a good option if your money is stuck to push it forward. But reversing a Bitcoin transaction in your case after almost a decade is not feasible though I had read the suggestions of many people which might not work because of the number of years involved and they probably did not consider the wallet used for the transaction.

Next time, be sure of the payment, mempool and fees associated before pressing the Go button.

It has nothing to do with time... If you interprete the op's posts, it seems the transaction isn't confirmed. If the op makes sure it's never broadcasted again and he is able to spend the unspent output in a new transaction, his funds are safe and he doesn't have to "forget about the transaction". If the transaction ended up in a block 7 years ago, you would have been 100% correct since a confirmed transaction with more than a handfull of confirmations could be seen as irreversible (even a single confirmation makes it irreversible from a normal user's point of view, unless they're willing to spend a lot of money on a 51% attack or if they're extremely unlucky and the block including their transaction becomes stale whilst the block in the longest chain doesn't include their transaction)

Also, a transaction is wallet-agnostic, if you are able to access or export the private keys from the initial wallet, it doesn't matter if said wallet was created 7 years ago, you should be able to use the unspent output in a new transaction. Sure it's possible it'll require some extra steps, but if the value of the unspent output makes it worth your wile to take these steps, it shouldn't be impossible.

EarnOnVictor

hero member

Activity: 826

Merit: 641

Leading Crypto Sports Betting & Casino Platform

This time is too long, I would advise you to forget about the transaction. I know it's because of the current higher value of Bitcoin that makes you feel concerned, but you have to let go, the technology then is not like today because the wallet you used for the transaction matters which you did not mention in your explanation.

I'm glad you now know better, Opt-In Replace-by-Fee is a good option if your money is stuck to push it forward. But reversing a Bitcoin transaction in your case after almost a decade is not feasible though I had read the suggestions of many people which might not work because of the number of years involved and they probably did not consider the wallet used for the transaction.

Next time, be sure of the payment, mempool and fees associated before pressing the Go button.

nc50lc

legendary

Activity: 2534

Merit: 6080

Self-proclaimed Genius

Quote from: BlackBoss_ on September 25, 2022, 10:26:48 PM

You can use either

- Replace by fee RBF
- Child pay for parents CPFP

Quote from: bitmover on September 26, 2022, 01:53:31 AM

If you can't see the money, the transaction might have Confirmed or you just need to resend/rebroadcast it

If he would use rebroadcast or rbf, it will be sent to the original receiver.
Based on the second paragraph of OP, he doesn't want the transaction to be sent to the 'destination address'.

@Gorilla22 in case you're talking about Electrum, instead of "abandon transaction", Electrum has "remove" which will delete a local transaction.
In both wallets' case, a local transaction is just saved in your wallet and not known by the Bitcoin network, but it affects your wallet's ability to spend the coins it intended to spend.
You can regain that balance after abandoning/removing the local transaction but only if you still haven't spent the particular UTXO(s) that was used by the local txn.

mocacinno

legendary

Activity: 3584

Merit: 5243

https://merel.mobi => buy facemasks with BTC/LTC

To be completely on the safe side, i'd advice you to combine 2 of the above advices:

1) abandon the transaction
2) spend the unspent output in a new transaction funding one of your addresses.

It's an infinitely small chance, but somebody might have captured the transaction 7 years ago. If he/she decides to broadcast it again, your funds will be gone. So, if you abondon the transaction, then spend the unspent output, you should be safe.

Now, in all honesty, if you just abondon the transaction, you're probably fine... The odds of somebody broadcasting a transaction that was saved 7 years ago is very small (to say the least). It's just that if it was me, i'd go for 100% safe, not 99,9% Wink

witcher_sense

legendary

Activity: 2450

Merit: 4415

🔐BitcoinMessage.Tools🔑

It is a little bit odd that you have been in the cryptocurrency space for so long and haven't yet bothered to read how transactions behave after they get into mempool. If the mempool was congested at that time and you accidentally had set a very low fee, there was a little chance that your transaction got through. Bitcoin full nodes allocate a limited amount of memory for mempool and keep only those transactions that pay above a certain limit. This limit depends on how congested the bitcoin mempool is: transactions with low fee rates may never appear for some nodes, and, therefore, never get propagated to miners' full nodes. Transactions that never get a confirmation get removed from the network as if there weren't any actions on your part. Only those transactions that miners add into a successful block will matter due to the immutability of the blockchain, but other transactions lose their significance forever.

bitmover

legendary

Activity: 2352

Merit: 6089

bitcoindata.science

Quote from: Gorilla22 on September 25, 2022, 10:00:34 PM

I sent a transaction with too low fee.
It was 5-7 years ago, and as much as I remember, it was still "stuck" several months after I sent it.
That time it was small money, so I just resent that transaction.
It is not very big amount of btc even now, but it still would be great to get it back.

As others said , that transaction is not in the mempool anymore.

The lowest fee possible fot a transaction is 1 sat/vbyte, and transactions with that fee gets Confirmed almost in daily basis. Só your transaction is not stuck and the btc is still with you.

What do you mean by "get your it back"?? Can't you see that money in your wallet?
Do you have the transaction id?

If you can't see the money, the transaction might have Confirmed or you just need to resend/rebroadcast it

You can rebroadcast here https://www.blockchain.com/btc/pushtx

nc50lc

legendary

Activity: 2534

Merit: 6080

Self-proclaimed Genius

Quote from: Gorilla22 on September 25, 2022, 10:00:34 PM

It was 5-7 years ago, and as much as I remember, it was still "stuck" several months after I sent it.

From which client? Based from your other posts, I'll assume that it's Bitcoin Core.
If so, that "stuck transaction" may just be a locally saved transaction and you might have already spent its input.
If not, you can easily abandon it since it must not be in any node's mempool by now.

To "unstuck" it, just go to 'Transactions' tab and use "Right-click->Abandon transaction" and it will be dropped from your wallet.dat.
After abandoning it, the funds that it "locked" should be useable again (the transaction will have red texts).

Of course, I'd advice you to create a backup of your wallet before trying those steps.

pooya87

legendary

Activity: 3472

Merit: 10611

Quote from: Gorilla22 on September 25, 2022, 10:00:34 PM

I sent a transaction with too low fee.
It was 5-7 years ago, and as much as I remember, it was still "stuck" several months after I sent it.
But if my transaction arrives to its destination address it will be just lost for me.

If the transaction is unconfirmed, that means it is no longer in the mempool and everyone has already forgotten about it. Unless you send it again today!
If it had remained in the mempool, it would have been confirmed years ago.

Quote

The only option which is good for me is getting the transaction back to my wallet.
Is it still possible? How?

The only option is to double spend the same coins changing the destination. If the transaction were marked by RBF it is easier to double spend it, otherwise it is near impossible because almost all nodes reject double spend tranasctions.
Besides if the tx is currently in the mempool it will confirm soon since minimum fee is very low these days.

BlackBoss_

sr. member

Activity: 602

Merit: 387

Rollbit is for you. Take $RLB token!

Quote from: Gorilla22 on September 25, 2022, 10:00:34 PM

There are a lot of posts about stuck transactions, but they are almost always about "how to push transaction to its destination".

You can use either

- Replace by fee RBF
- Child pay for parents CPFP

For the first option, you must use this opt-in RBF when you broadcast that transaction initially.

If you did not use that option when make your transaction broadcast, later you can only use Child Pay for Parents. This option is more complex than RBF.

Gorilla22

jr. member

Activity: 42

Merit: 66

I sent a transaction with too low fee.
It was 5-7 years ago, and as much as I remember, it was still "stuck" several months after I sent it.
That time it was small money, so I just resent that transaction.
It is not very big amount of btc even now, but it still would be great to get it back.
And it is also a challenge :-)
And possibility to learn more about bitcoin.

There are a lot of posts about stuck transactions, but they are almost always about "how to push transaction to its destination".
But if my transaction arrives to its destination address it will be just lost for me.
The only option which is good for me is getting the transaction back to my wallet.
Is it still possible? How?

Topic: How to return stuck transaction (instead of pushing it to receiver's addres) ? - page 2. (Read 344 times)