pull down to refresh

Last September I wrote After the Core/Knots Hard Fork... Which version will you run and why?

From my post #1205451

"Which is why I believe we will see an arbitrary-data hard fork in the next year, probably resulting in 2 separate chains..."

I posted this on September 3rd, 2025 in other words within two days of the formal activation date of the next hard fork, September 1st 2026, probably transforming the "Knots" software into its own separate chain through a consensus disagreement.

And before you say "oh but it's just a soft-fork" it's "a tightening of the consensus rules therefore a soft fork..."

Right, well that's like saying it's not a divorce it's just a 'disagreement' because we no longer live together, we live in separate houses by separate rules, and your money and transactions I think are invalid so you can't make them I think they "aren't real..."

But we're still "together."

OK

So having said that (and people are FREE to run whatever software they want and spend their hard-earned money on whatever tokens they want...)

How do I sell my fork-coins either of them without inadvertently exposing the other coins on the other chain? I see the influencers are really really pushing "run Knots" and that's their right - people can run whatever node they want to...

My understanding is that spending a coin on one chain could expose the private key of the other coin on the other chain, compromising its security. If this is true, how is this prevented or mitigated?

How do you sell some UTXOs safely on the chain you don't want, and keep the UTXOs on the chain you do? I haven't seen this emphasized anywhere else, and I thought it should be... so the PLEBS can be safe.

Thank you!

222 sats \ 1 reply \ @Murch 11 Feb
My understanding is that spending a coin on one chain could expose the private key of the other coin on the other chain, compromising its security. If this is true, how is this prevented or mitigated?

No, that’s not the case. The main issue is that any transaction on one chain can be replayed on the other, if they have compatible rules as in this possible split between Bitcoin and RDTS.

If there is a persistent chain split, people will need to separate their funds on the two chaintips. This could be for example achieved by sending a transaction that is only valid on one of the two chains (e.g., by violating one of the new rules RDTS introduces), or by simultaneously sending transactions to yourself on both chains at the same time with different recipient addresses, hoping that they both go through. If the feerates are sufficiently different on the two chaintips, you can send a transaction on the chain with the lower feerates first, and then spend the same UTXOs to a different address at a higher feerate on the other chain. Alternatively, you could wait for some coinbase outputs to mature and acquire a UTXO that descends from a coinbase output that only exists in one chaintip.

Once you have any UTXO that only exists on any one chain, you can use it to split all of your funds by spending that UTXO along with others from your wallet. All of the outputs of those transactions will only exist on that chaintip. Using such UTXOs to “vaccinate” your transactions against replay attacks, you can then reliably spend and/or sell funds on either chaintip.

reply
Alternatively, you could wait for some coinbase outputs to mature and acquire a UTXO that descends from a coinbase output that only exists in one chaintip.

Thank you I had never thought of this...

Once you have any UTXO that only exists on any one chain, you can use it to split all of your funds by spending that UTXO along with others from your wallet.

This is complicated (!) but good to know... thank you for your response.

reply

There are plenty of how-to articles from back in the BCH/BTC split in 2017

reply

I'll check them out thank you
Edit: what would I even search for? "Spend fork coins"
"How to send fork coins?"

reply
101 sats \ 2 replies \ @ek 11 Feb

You’re interested in replay protection. Here is explained how BCH implemented it.

reply
101 sats \ 0 replies \ @Murch 11 Feb

Note that this describes how BCH changed the protocol to make it impossible to replay transactions in either direction, because the transaction format was changed.

In the case of Bitcoin vs RDTS, the problem would be that both networks accept the same transaction format, except for the new rules introduced by RDTS.

reply

Thank you!

reply

I'll find you a few tomorrow

@remindme in 10 hours

reply

Here are some of Aaron's guides from the last time around we had stupid hardfork troubles

https://bitcoinmagazine.com/technical/beginners-guide-claiming-your-bitcoin-cash-and-selling-it

https://bitcoinmagazine.com/technical/bitcoin-beginners-guide-surviving-bgold-and-segwit2x-forks

Like back then, some of the hww might supply access to the forked coin and so you'd be able to spend directly from there

Additionally, it currently seems SegWit2x will fork without strong replay protection. This means that post-fork, BTC transactions and B2X transactions will look identical and could both be valid on both blockchains.
Therefore, spending coins on the BTC blockchain could make you accidentally spend the “equivalent” B2X on the SegWit2x blockchain, and the other way around. Instead of paying someone only BTC, you may unintentionally send B2X as well — or vice versa. The BTCs and B2Xs are initially “stuck together.”
"To be on the safe side, you should probably not spend an coins after the SegWit2x fork at all. As explained below, you’ll first need to “split” your coins"
reply