Here is the audit path for you to confirm that the replay protection actually activated:
The final coinjoin tx that confirmed on both chains is f046581f06d353211cfcbbff0681a4f61ac33a8ffb33fc70719cd3b855818bc9
bc1pjhnedggvm9czj9lhdpd78hcxt56s0y2hz7vx8srt8zlfxy2lhees4t7ruu was spent and already confirmed on both chains.
Replay protection ancestor coinjoin tx on Core: bbd66083ac8330dde6509ad54a021082f33f15564d831c94b32ae08a7eb63586
Replay protection burn tx on Knots: 2ad1dc24a493b1f5c00d7cf29582a2b54bf6f57ca2d7b0caf8475067580edb8f
There was a 4th block mined on the Knots chain, so the burn tx now has 2 confirmations.
Is there still a market for blakies?
Who?
blake-coiners
That’s my pet name for the Blake2B fork token.
I thought they were still making up their minds whether they would fork off from their mandatory signaling chain or from Bitcoin mainchain's latest state on September 1st.
I burned their shitcoin once, I'll burn their shitcoin 1,000 times.
Sure, I just meant to point out that if they fork off from a future block, this replay protection would be undermined and it should perhaps be communicated in the context so that people don’t rely on these coinjoins for replay protection against a potential later forkpoint.
Good job!
Thanks, I missed getting into the first two Knots blocks because I found out too late that Sparrow doesn't support full-RBF (which was made default way back in Core v28...)
Remember back in the day when we just edited the hex and then
signrawtransaction?Was this the price for protection?
https://mempool.guide/tx/2ad1dc24a493b1f5c00d7cf29582a2b54bf6f57ca2d7b0caf8475067580edb8f
Knots coins are worth effectively zero, so no real coins were harmed: https://x.com/Kruwed/status/2086772990558056927
Oh right, forkcoins!
Now you have a second means of derisking!
https://twiiit.com/Kruwed/status/2086772990558056927
What!?
I thought it was all over days ago?
You can't turn off a blockchain.
I thought it stalled and that was it. Might be years till the next difficulty adjustment.
They'll have to any way reset difficulty when they change PoW
https://twiiit.com/Kruwed/status/2087459530120614097
replay protection is the real feature here and it works, nobody's arguing that. the burn is just the flex, and flexing on coins you already declared worthless is a grudge with a txid. first coinjoin linked burn on a fork wall, that's a milestone either way
The issue arises from Bitcoin Core's
mempoolpolicy rejecting transactions with duplicate inputs (knots) whenmempoolfullrbfis enabled, which is the default in recent versions. This affects CoinJoin transactions (e.g., Wasabi, JoinMarket) where multiple transactions may share the same inputs (knots) due to the CoinJoin protocol's design.Solution:
mempoolfullrbfin Bitcoin Core's configuration (bitcoin.conf):mempoolfullrbf=0This allows the mempool to accept transactions with duplicate inputs, enabling CoinJoin transactions to propagate correctly.mempoolfullrbfis required):wtxidrelay(enabled by default) to allow transactions with the same witness data (e.g., CoinJoin outputs) to propagate.This change is necessary to maintain compatibility with privacy-focused transactions while adhering to Bitcoin Core's default security policies.