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
22 changes: 22 additions & 0 deletions _pages/concept.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
---
layout: page
title: Concept
permalink: /concept/
---

# Background
The Bitcoin blockchain contains coins. New coins on the Bitcoin blockchain are created by Bitcoin miners. Users can buy the rights to coins through an exchange service. Users can transfer their rights to Bitcoin coins (or part thereof) via Bitcoin transactions.

Digital wallets provide users with the ability to execute transactions on the Bitcoin blockchain. Each digital wallet contains a user’s private key and is therefore a mechanism which allows users to secure their rights, as well as transfer their rights to other users via transactions.

The Bitcoin blockchain computer code is open source (it can be legally copied and modified by a third party). Some incompatible changes to the Bitcoin software are also known as hard forks i.e. changes which modify the rules used to validate transactions and blocks. The launch of any incompatible modifications to the Bitcoin blockchain software will cause different nodes to no longer agree on transaction history. When this happens Bitcoin itself is not really affected. However, at the time when these changes take effect, the Bitcoin blockchain does split and from that point onwards two blockchains exist.

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 essentially stuck together.

This is where chainspl.it comes in.

Chainspl.it is a service which helps users safely split their coins across forks. Chainspl.it is non custodial, meaning all of the signing takes place on the user’s end.

Please see our ["Introducing chainspl.it, Easily handle forked coins"]("https://www.youtube.com/watch?v=wWkdfnqjpug&feature=youtu.be&a="){:target="_blank"} YouTube video.