Yes, he was able to create a "psbt" (partially signed Bitcoin transaction) send it to me, and I signed and broadcast it from the wallet.

It was super, super close. The "toxic transaction" was in the next block several times while we worked on it. Got extremely lucky there was reasonable activity on chain this morning, it could have easily cleared, but the gods postponed it for nearly 4 hours! lol, never thought I'd be happy watching a transaction getting delayed....

Apparently, all transactions are able to be replaced, just gotta have the tools and know-how.

Learning a lot today.

Reply to this note

Please Login to reply.

Discussion

the universe works in mysterious ways

Also, I feel extremely lucky, because if the wallet holder had seen the pending incoming transaction, they could have done an RBF on their own and snatched the funds.

A few months back when mempool was backlogged I remember a transaction where someone had been trying to combine a bunch of small transactions and some good Samaritan bumped the fee for them.

Actually no they can’t RBF the transaction.

They could CPFP though (basically spend their own output with a lot of fees, making replacement very costly).

Am I mistaken or isn't it possible in most wallet software (eg Electrum) to just spend a UTXO again as long as it's not spent confirmed? I remember having done that in the past. So it's an "unknown" RBF

I am referring to the scammer RBFing

yes totally understand, wasn't clear sorry. I meant more the previous comments about needing the right tools and special technical skills. If you use the right wallet software you don't need any extra skills right? Or which tools do you use to create a PSBT in such scenarios?

Random bitcoin-cli commands and obscure tools

So the RBF trick in the original thread didn't work? I was about to print out that note and keep it next to my computer forever, for that time when inevitablyI will fuck up and need it xD

Not to change the destination address, just speed up existing, is the way rbf typically works.

I'm not positive, but to create the psbt, I think he used a btcpay server. I used Sparrow to sign it, he broadcast it, cuz on first few attempts I got an error.

So simply issuing a new transaction with higher priority to a different address using the same UTXOs wouldn't work?

Looking forward to learn about this, because I can totally see myself needing it some day.

That's pretty much how it was done, but few wallets support building a new transaction.

"BTCPay Server and Sparrow Wallet are two wallets that can be used to create partially signed Bitcoin transactions (PSBTs).

Explanation

BTCPay Server:

1. Log in to BTCPay Server

2. Choose the store to send from

3. Select "Bitcoin" under "Wallets"

4. Click Send

5. Enter the destination Bitcoin address and amount

Sparrow Wallet:

1. Import the PSBT transaction

2. Sign the transaction

3. Broadcast the transaction

PSBTs are a Bitcoin standard that allows multiple parties to sign the same transaction without exposing their private keys. This is useful when multiple parties want to add inputs to the same transaction.

PSBTs are a data format that allows wallets and other tools to exchange information about a Bitcoin transaction and the signatures needed to complete it."

Even though a switched to Wasabi Wallet a few months ago for the coinjoin feature, I had been using Sparrow all along before and keep it on my computer. It is really my favorite one.

That’s awesome! I wonder if we can create a small app to quickly generate this new psbt file on the fly 🪰