-
Notifications
You must be signed in to change notification settings - Fork 11
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
tpmccallum
wants to merge
8
commits into
chainsplit:master
Choose a base branch
from
tpmccallum:patch-1
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
hkjn
reviewed
Nov 7, 2017
_pages/concept.md
Outdated
|
||
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. |
There was a problem hiding this comment.
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
Thank you @hkjn |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.