Quote from: WanderingPhilospher on Today at 01:28:27 AM

Quote

That's what I did, I created a lock with rbf completely disabled and it's not pocibel boot or anything superimposed I said that and everyone here laughed in my face and told me to prove it.. why prove it if I already knew.. lol

Holy cheese and grits and gravy. How many tests have to be ran before people finally get it that disabling RBF is not fool proof?!?! Public tests have been ran a few times, to show that even with RBF off/disabled, a tx can still be changed, diverted to another address.

hotmoney ate up how much forum real estate to say something totally false:

Quote

Non-RBF transactions cannot be modified or replaced.

Geesh.

Quote from: mcdouglasx on February 23, 2025, 09:46:01 PM

It seems that the solvers do not disclose the paths they followed, especially for searching addresses without exposed public keys, thus the "Large Bitcoin Collider" does not maintain its course. Nowadays, we only see developers omitting to share their information, as the current era is all about criticizing everything, being rude, and unproductive. Each time, the end draws closer, the day when this post will be buried forever. However, I keep hope in those closed circles, where the few members have a respectful approach to sharing ideas.

The last solver did explain how it was all done.

@wondring_philosopher, did you at least get a donation for inventing the Marapool method, or are we just handing out free genius points these days? Grin

And seriously, why are people still stuck on RBF like it’s some unsolved mystery? Enable it, disable it—makes zero difference. The last puzzle transaction went through just fine with RBF on, and the funds got swept without a hitch. So, can we please move on? No need for another AI-generated essay to ‘educate’ us—it’s already clearer than a blockchain explorer on a sunny day.