Quote from: wilspen on Today at 07:05:36 PM

Quote from: kTimesG on Today at 06:58:57 PM

Quote from: GR Sasa on Today at 06:55:31 PM

fucking hell, i couldn't replace the transaction by any higher fee i got the error saying insufficient fees. wtf

Weird. All I got was "Error: txn-mempool-conflict" when trying to push the new TX (key was cracked in seconds).

So I guess it depends on how to push a raw TX bypassing this error. I'm sure a P2P node can bypass this problem. So not sure what exactly was proven here, except some mempool rules depending on who you broadcast the TX to.

Is it not clear what was proven? hears at least 4 RBF in the transaction, and the transaction was sent with the RBF deactivated, finally, to the guy who said he found wallet 66 and is scared, it's proven that he will lose the BTCs if he tries to transfer, and to the rest of the people who are looking for it, it is worth reflecting on whether it is worth wasting energy looking for a key when they could lose the funds, perhaps the only way to make the transfer securely is through a miner, but even then it would be risky, you have to trust too much in the miner, hahaha

I have no idea what actually went down, I didn't understand anything from the live stream. All I know was I tried pushing around 20 or so transactions with higher fees (no RBF, classic TX) and none went through due to "mempool rules" errors. I searched for different broadcasters to push the raw TX (even chinese lol). I am 100% sure there had to exist a way to push a completely valid TX with a higher fee.

Also did the mempool.space API worked? Maybe I had an error in my script but it didn't seem to return any data for the outgoing transaction which was supposed to be used as an input, during all of the time. Someone can shed light if their API worked or not?