Anyone here know how to turn non-RBF transactions into RBF-enabled?
It's not possible to do to existing transactions in mempools since the field that signals for opt-in RBF is in each input's nSequence field.
Changing it into
0xfffffffd or lower will result with "
mandatory-script-verify-flag-failed" error.
Changing nSquence will also result with a different txid.
Applying those changes to an existing unconfirmed transaction to flag opt-in rbf will result with a different transaction,
basically replacement that even full-rbf nodes will reject for having the same fee as the original.
Some people having issues bumping unconfirmed transactions from TrustWallet and I want to help them fix their issue that is why I tried to search for a solution.
The suggested full-rbf above is the solution since it doesn't require that flag to be replaced
but the replacement need to follow replace-by-fee rules like paying for its own and the original transaction's bandwidth.
(
e.g.: if size are the same; +1sat/vB minimum by default)
To try in mainnet, you need to find a way to connect to nodes that enabled full-rbf to broadcast the replacement transaction.
Example (
Needs a Bitcoin Node):
https://petertodd.org/2023/why-you-should-run-mempoolfullrbf#full-rbf-peeringI'd like to test this but the problem is I don't have BTC I already exchange them into other crypto.
Use testnet on a wallet that can create transactions with disabled opt-in rbf flag.
However, you may not be able to accurately test full-rbf's behavior in testnet because the number of nodes that enabled -mempoolfullrbf is entirely different in mainnet.