Quote from: kTimesG on Today at 09:12:56 AM

Quote from: Akito S. M. Hosana on Today at 08:58:01 AM

Quote from: kTimesG on Today at 08:05:44 AM

Not sure what's the fuss about.

So you’re dead certain that you or no one else is gonna get nicked for this? Bruteforcing a private key’s just some basic shit, is it? I’m proper baffled, mate. Especially knowing the feds are all over us. Tongue

Of course I'm not, the creator may rightfully claim the funds.

Other individuals: not so much. While in the mempool, the order of TXs cannot be established, that is all I am saying. For example, a node can simply set a replacement's TX "first seen" tag to BEFORE the original transaction, making it thus the "initial transaction".

That’s not how the mempool works. “First-seen” timestamps are local-only; they never leave the node, so you can’t fake one to make a replacement look like the original. A transaction can bump another only by spending the same inputs and paying a higher fee, that’s BIP-125, full stop. Why is everyone in this thread repeating myths instead of checking the actual spec?