btc sent to scammer, unconfirmed zapwallettxes

[maudo]

im still using bitcoin core since 2020, it runs fine but i just sent 190usd in btc to indian scamer that is gone right after seen bitcoins sent.
tx is still unconfirmed, and it's not RBF.
version 24 no longer supports zapwallettxes so im going back to v20. can zapwallettxes command help me to get my coins back?

[1715070301]

1715070301

[1715070301]

1715070301

[1715070301]

1715070301

[1715070301]

1715070301

[hosseinimr93]

can zapwallettxes command help me to get my coins back?

With using zapwallettxes command, you ask your node to remove the unconfirmed transactions, but your transaction has been probably broadcasted to many other nodes and there is no way to ask them to remove your transaction from their mempool.

You can try your chance and broadcast a new transaction with a higher fee, but it's very unlikely that your new transaction can be included in the blockchain.

[maudo]

i sent with 5.2 sat/vB . it's still unconfirmed, omg need to reverse these coins somehow

[HCP]

i sent with 5.2 sat/vB . it's still unconfirmed, omg need to reverse these coins somehow

Unless you set the transaction as RBF (which it appears you did not) or you know a very friendly mining operation, your chances of getting another transaction confirmed prior to your original are pretty much non-existant.

Most nodes will reject any new transaction spending those same UTXOs due to the fact that an existing transaction spending them already exists (ie. rejection due to double spend).

[BitMaxz]

I don't think you can still reverse the transaction if it's not RBF most of the nodes right now like the above said it most like be reject but you can try to broadcast your new transaction to some broadcasting sites listed here

Then use this tool below to generate a raw transaction and sign it in your Bitcoin core wallet and then broadcast it to any pushtx listed above.
- https://coinb.in/#newTransaction

Let's hope that there are still a few nodes that accept non-RBF transactions.

[hosseinimr93]

Then use this tool below to generate a raw transaction and sign it in your Bitcoin core wallet and then broadcast it to any pushtx listed above.
- https://coinb.in/#newTransaction

There is no need to use coinb.in.
With using zapwallettxes command, you remove the unconfirmed transaction from your mempool and you can broadcast the new transaction using bitcoin core itself.

Anyway, OP's transaction has been probably confirmed so far.

[maudo]

I don't think you can still reverse the transaction if it's not RBF most of the nodes right now like the above said it most like be reject but you can try to broadcast your new transaction to some broadcasting sites listed here

Then use this tool below to generate a raw transaction and sign it in your Bitcoin core wallet and then broadcast it to any pushtx listed above.
- https://coinb.in/#newTransaction

Let's hope that there are still a few nodes that accept non-RBF transactions.

just waked up surprisingly still unconfirmed, can you tell me more about how can i create new transaction there and sign with bitcoin core??

[nc50lc]

version 24 no longer supports zapwallettxes so im going back to v20. can zapwallettxes command help me to get my coins back?

Its equivalent feature is the "abandon transaction" but it can't be used to remove unconfirmed transaction that's included to your mempool.
The right-click menu option will not be clickable. But even with zapwallettexes, other nodes will simply keep your transaction in their mempools.

Your current option is to enable "full rbf" by adding the line: mempoolfullrbf=1 to your bitcoin.conf file which should enable you to (manually) create a replacement without the flag.
However, not all nodes and miners are configured with full rbf so the chance that it'll get confirmed before the previous transaction is quite low.
(so far, AFAIK, there's only one mining pool that's enabled full-rbf; but it's not one of the big pools)

[hosseinimr93]

just waked up surprisingly still unconfirmed,

You already said that you used the fee rate of 5.2 sat/vbyte for your transaction.
With that fee rate your transaction should have been confirmed by now, unless it has an unconfirmed parent with the very low fee rate.

Can you see your transaction in block explorers? Maybe, your transaction hasn't been broadcasted to the network and it's just a local transaction.

[LoyceV]

Can you see your transaction in block explorers? Maybe, your transaction hasn't been broadcasted to the network and it's just a local transaction.

Unlikely, OP said this:

indian scamer that is gone right after seen bitcoins sent.

But it doesn't make sense, this transaction should have been confirmed already. OP: can you share the txid? Any chance your Bitcoin Core was still syncing when you checked?

[n0nce]

i sent with 5.2 sat/vB . it's still unconfirmed, omg need to reverse these coins somehow

If you still can, try double-spending with a much higher fee rate. Most likely, the money is gone, anyway. So even 20sat/vB or 100 would be better than losing it all.

Since nobody asked yet: are you sure it is an Indian scammer? How were you confident about the deal in one second and right after sending you immediately knew it was an Indian scammer and that you need to abort the transaction?

[maudo]

i found him on fiverr, his location was set in india, i asked him if he can install me crash game script, then we went out of fiverr to telegram so he can do me discount, and right after i sent him btc for script installation our telegram chat is gone. end of story

[NeuroticFish]

i found him on fiverr, his location was set in india, i asked him if he can install me crash game script, then we went out of fiverr to telegram so he can do me discount, and right after i sent him btc for script installation our telegram chat is gone. end of story

It's interesting that you are still telling the not-so-relevant story and you don't post the tx id.
However, is the tx confirmed? Or did you manage to double-spend it?

[n0nce]

i found him on fiverr, his location was set in india, i asked him if he can install me crash game script, then we went out of fiverr to telegram so he can do me discount, and right after i sent him btc for script installation our telegram chat is gone. end of story

I see. I'm not familiar with such platforms, but I guess they have a built-in payment method which is more expensive due to fees. So he was able use that as an excuse to move the trade off-platform where there is no protection.
Anyways, without a transaction ID, there's not a lot we can discuss. The money is gone most probably, anyway, so all I can say is I hope you learnt your lesson. Bitcoin is not some PayPal thing with customer support. Payments are final. It is a feature, but it has to be used consciously. It is the reason escrow services exist on this forum for instance.

[maudo]

confirmed.. all is gone for good. not a best day in my life tbh

[BitMaxz]

confirmed.. all is gone for good. not a best day in my life tbh

Ow sorry next time don't deal to someone randomly the only problem is you deal to him outside from fiverr next time don't deal outside fiverr even there is a discount it isn't safe to deal without escrow.

I suggest enable RBF in your wallet as suggested above so that you can easily reverse the transaction.

Anyway, about the guide from my post above check this https://blog.coinb.in/guide_double_spend_rbf

[BenCodie]

I know that the transaction was already confirmed, though in the future if you ever have this issue I would suggest:
1. Downloading electrum right away (if you do not already have it on hand, which is handy in general and for these kinds of situations).
2. Exporting the private key from bitcoin core and importing it to electrum (from memory you can go to the developer console and use dumpprivkey).
3. Replace-by-fee to an address of your own.

The sad part about this is that I saw this thread this late. You were lucky that your fee was as low as it was to be able to have as much time as you did to solve the problem. It's a shame that you could not solve it in time...I'm sorry for your loss.

Also, you really should be keeping your client up to date. Using a client out-dated by over 2 years for any application let alone one that is finance-related is generally not the best security practice.

[hosseinimr93]

3. Replace-by-fee to an address of your own.

This was not possible at all. OP's transaction was not RBF-enabled and importing the private key into electrum couldn't change anything.
You can replace your transaction with a new one paying higher fee only if the original transaction has been flagged as RBF.
Take note that if OP's transaction was RBF-enabled, he/she could replace it with a new one using bitcoin core itself and without any need to electrum.
 

[LoyceV]

I know that the transaction was already confirmed, though in the future if you ever have this issue I would suggest:
1. Downloading electrum right away (if you do not already have it on hand, which is handy in general and for these kinds of situations).
2. Exporting the private key from bitcoin core and importing it to electrum (from memory you can go to the developer console and use dumpprivkey).

Electrum can't do anything Bitcoin Core can't (at least in this case). Once the transaction is in mempool, it will instantly show up as unconfirmed transaction in Electrum and any attempt to broadcast the same inputs in a different transaction will be rejected.

[maudo]

I know that the transaction was already confirmed, though in the future if you ever have this issue I would suggest:
1. Downloading electrum right away (if you do not already have it on hand, which is handy in general and for these kinds of situations).
2. Exporting the private key from bitcoin core and importing it to electrum (from memory you can go to the developer console and use dumpprivkey).

Electrum can't do anything Bitcoin Core can't (at least in this case). Once the transaction is in mempool, it will instantly show up as unconfirmed transaction in Electrum and any attempt to broadcast the same inputs in a different transaction will be rejected.

Ok then how about with mempoolfullrbf=1 ? even if transaction is not rbf, it is possible to aband transaction?