Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Created concept.md providing backround and concept #5

Open
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

tpmccallum
Copy link
Contributor

No description provided.

Needs further vetting to prevent misquote or quote (out of context) in any way.
Updating the concept to include some comments by JW Weatherman on the Introducing chainspl.it YouTube video.

Please share as widely as possible for editing to ensure that all information is accurate.
Just a few tweaks ....
Please remember that the facts in this page need to be vetted by experts before publishing.
The branding is becoming more consistent; moving away from UTXO terminology (UTXO splitter etc.). This document has not been updated to reflect the chainsplit branding. It is hoped that as new documents become available (which talk about split propagation, splitcoins etc) the removal of UTXO wording (whilst technically more correct that using the term "coin") will make it easier to understand.

It is important to remember that the blockchain contains every historical transaction and therefore when the blockchain splits each blockchain contains an identical history, right up until the chain split. Due to this shared transaction history, a user who holds rights to coins on the Bitcoin blockchain, before a blockchain split, automatically holds the identical rights to coins on the other chain, at the time of the blockchain split.

If neither of the chains are sporting a new and unique transaction mark, a problem arises whereby, a transaction on one chain is valid on the other chain. In this case transactions on one chain can be replayed on the other chain. A replay is not automatic, nor is it in any way part of the default operation of either chain. A replay attack can be carried out by a malicious party. The point being, that whilst a signed transaction on one chain can be repeated on the other chain, the coins are essetially stuck together.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: s/essetially/essentially

Fixed spelling; essentially
@tpmccallum
Copy link
Contributor Author

Thank you @hkjn

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants