bitcoin-dev

Anti-transaction replay in a hardfork

Anti-transaction replay in a hardfork

Original Postby Tom Harding

Posted on: January 26, 2017 15:58 UTC

The longer both forks persist, the more transactions become unavoidably fork-specific through the mixing in of new post-fork coins.

The rationality of actors in this situation essentially defines the limited solution that is possible. Upgraded software can create transactions guaranteed not to execute to one fork or the other, or that is not prevented from execution on either fork. This would result in much less chaotic markets and well-determined prices for the two currencies. However, none of this precludes the possibility of further forks on either side, and the difficulty consideration alone suggests a likely counter-fork by (part of) the existing network. Mining is a random process and the hashing power is going up and down which adds to the complexity of the situation.

Bitcoin Logo

TLDR

Join Our Newsletter

We’ll email you summaries of the latest discussions from authoritative bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.

Explore all Products

ChatBTC imageBitcoin searchBitcoin TranscriptsSaving SatoshiBitcoin Transcripts Review
Built with 🧡 by the Bitcoin Dev Project
View our public visitor count

We'd love to hear your feedback on this project?

Give Feedback