Need help, stop TX with my own node. REWARD

OddEvenBets.com

full member

Activity: 1022

Merit: 100

Quote from: NeuroticFish on March 28, 2019, 02:31:19 AM

I didn't try it to the very end, but the steps from this tutorial seem correct: https://steemit.com/bitcoin/@profitgenerator/tutorial-how-to-fix-unconfirmed-transactions
And you can use it with Electrum, in case you didn't have Bitcoin Core installed and synced.

The only problem is that you have to carefully edit the file and there may be a few more places than in the tutorial. (And obviously make backup of the wallet first!)

Thanks, but I'm late..

NeuroticFish

legendary

Activity: 3668

Merit: 6382

Looking for campaign manager? Contact icopress!

I didn't try it to the very end, but the steps from this tutorial seem correct: https://steemit.com/bitcoin/@profitgenerator/tutorial-how-to-fix-unconfirmed-transactions
And you can use it with Electrum, in case you didn't have Bitcoin Core installed and synced.

The only problem is that you have to carefully edit the file and there may be a few more places than in the tutorial. (And obviously make backup of the wallet first!)

Edit: Nevermind, you are too late, the transaction has 2 confirmations now. Sorry.

OddEvenBets.com

full member

Activity: 1022

Merit: 100

Quote from: Heisenberg_Hunter on March 28, 2019, 01:38:45 AM

0.67 sats/byte is infinitesimally smaller fee. There are chances, it stays in the mempool for a very longer time unless a miner decides to add them to a block. There is also a possibility, the transaction might even be rejected and returned back to your wallet. As nc50lc said, try using a coinb.in or try using the -zapwallettxes command to erase the tx from your local mempool and respend the same input.

To use the -zapwallettxes more successfully, you need to shut down the core and also should delete mempool.dat from the wallet folder. Once you have deleted the .dat file, and started the core with the command, the older unconfirmed transactions will be erased and you can spend the same coins to correct address with the higher fee. By this way, you can double spend the already spent coins.

I am not sure if this works but try the following things out,

1. Close the bitcoin core.
2. Go to the bitcoin directory/folder present in the documents folder.
3. Delete the mempool.dat file.
4. Restart the wallet with -zapwallettxes=1 command.

If this doesn't work, add the -zapwallettxes command in the bitcoin.conf file.
This can probably clear up the unconfirmed transactions in your wallet and respend the same input with higher tx. Hence the new tx gets confirmed and the older one gets rejected by the network.

Ok.
I'm late ... tx was been confirmed Embarrassed

Heisenberg_Hunter

legendary

Activity: 1584

Merit: 1280

Heisenberg Design Services

0.67 sats/byte is infinitesimally smaller fee. There are chances, it stays in the mempool for a very longer time unless a miner decides to add them to a block. There is also a possibility, the transaction might even be rejected and returned back to your wallet. As nc50lc said, try using a coinb.in or try using the -zapwallettxes command to erase the tx from your local mempool and respend the same input.

To use the -zapwallettxes more successfully, you need to shut down the core and also should delete mempool.dat from the wallet folder. Once you have deleted the .dat file, and started the core with the command, the older unconfirmed transactions will be erased and you can spend the same coins to correct address with the higher fee. By this way, you can double spend the already spent coins.

I am not sure if this works but try the following things out,

1. Close the bitcoin core.
2. Go to the bitcoin directory/folder present in the documents folder.
3. Delete the mempool.dat file.
4. Restart the wallet with -zapwallettxes=1 command.

If this doesn't work, add the -zapwallettxes command in the bitcoin.conf file.
This can probably clear up the unconfirmed transactions in your wallet and respend the same input with higher tx. Hence the new tx gets confirmed and the older one gets rejected by the network.

nc50lc

legendary

Activity: 2534

Merit: 6080

Self-proclaimed Genius

I still don't see another transaction in blockexplorers using that transaction's input. I'll be too late if you leave it that way.

If you used the coinb method, you need to broadcast it using the broadcast tab after creating the signed transaction.
It won't automatically broadcast after clicking "send"; copy the raw Tx, click "broadcast" tab and paste it there, click "submit".
Take note: you need to include the specific input's tx id for coinb to know the exact input to spend (it's in the online blockexplorers).

If that helped, you can keep the reward.

OddEvenBets.com

full member

Activity: 1022

Merit: 100

Quote from: nc50lc on March 27, 2019, 08:54:00 PM

You need to quickly "double-spend" the inputs before it get confirmed.
(luckily, the tx fee is too low and it's still unconfirmed)

I don't know the exact way to make a double spend transaction on core but you need it ASAP so try this:

Enable "Coin Control" in the setings. (Tick "replace-by-fee" too - might be needed)
Select the input used in that particular unconfirmed transaction.
Then make a new transaction using it with different address and REALLY high transaction fee like 50sat/b.

This could be inaccurate or wrong.

I have command line only..

nc50lc

legendary

Activity: 2534

Merit: 6080

Self-proclaimed Genius

You need to quickly "double-spend" the inputs before it get confirmed.
(luckily, the tx fee is too low and it's still unconfirmed)

I don't know the exact way to make a double spend transaction on core but you need it ASAP so try this:

Enable "Coin Control" in the setings. (Tick "replace-by-fee" too - might be needed)
Select the input used in that particular unconfirmed transaction.
Then make a new transaction using it with different address and REALLY high transaction fee like 50sat/b.

This could be inaccurate or wrong.

-Edit-
Or use coinb.in's transaction push and generator to manually create the transaction.
Don't forget to make the transaction fee higher!
You just need to export the address' private key from core.

OddEvenBets.com

full member

Activity: 1022

Merit: 100

Hello,

I sent by mistake 0.0035BTC https://www.blockchain.com/btc/tx/121189b2a15e1e973e8f922c1eba27851083b52e2bb442357a63e72b3c382017

Who can help make double spend TX?

How to stop TX with my own node.
Please help.

Topic: Need help, stop TX with my own node. REWARD (Read 307 times)