btc sent to scammer, unconfirmed zapwallettxes

[LoyceV]

even if transaction is not rbf, it is possible to aband transaction?

You can make your wallet abandon the transaction, but the other mempools won't remove it. So it doesn't help you.

[1715059271]

1715059271

[1715059271]

1715059271

[1715059271]

1715059271

[hosseinimr93]

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

With mempoolfullrbf=1, you only ask your node to accept and broadcast replacement transactions with higher fee even if the original transaction hasn't been flagged as RBF.
There is no way to change other nodes setting and almost all nodes will reject any transaction spending same UTXO(s) as a non-RBF transaction.

[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).

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.

I see. Well, that is unfortunate.

I suppose the lesson here maudo is that if you are dealing with someone that you have not dealt with before in a transaction without some form of escrow system, then the best thing to do is to use an updated client and ensure RBF is enabled. This is still not a sure-fire way to prevent being scammed though, as I am sure they will just hold you online until funds are confirmed...so overall, just take better precautions. Sorry for your loss.