> For the complete documentation index, see [llms.txt](https://hub.bsvblockchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.bsvblockchain.org/wiki/introduction/bitcoin-satoshi-vision.md).
# Bitcoin Satoshi Vision
Bitcoin Satoshi Vision (Bitcoin SV) was created to maintain the integrity of the Bitcoin public ledger by reverting back to the original Bitcoin protocol with the intention of keeping it stable and secure, and allowing it to scale massively in order to accommodate global demand for open public ledger technology. BSV Blockchain will maintain the vision set out by Satoshi Nakamoto’s visionary 2008 white paper titled [Bitcoin: A Peer-to-Peer Electronic Cash System](https://bsvassociation.org/wp-content/uploads/2025/06/bitcoin.pdf) which includes:
* Scaling network systems and developing robust mining client software in order to accommodate global demand for ledger space.
* Allowing a distributed small world network to form at the center of a Mandala network connecting billions of people through their devices.
* Elevating Miners into their role as service provider.
* Generating on-chain economic activity sufficient to allow transaction fees to supplant block subsidies as their primary funding mechanism.
* Driving a culture of using transaction fees to price transactions as a service.
* Leveraging economic incentives to build network security.
* Allowing the Bitcoin network to become a global infrastructure platform for financial and information exchange processes.
1. Past ledger duplications The Bitcoin ledger has twice been duplicated by Miners to implement features that modify the functionality of the node clients used to build the ledger.
2. Segregated Witness and the change from BTC to BCH The first duplication took place on August 1st, 2017 when Miners opted to create a new version of the protocol including Segregated Witness (SegWit), that modified the usage of digital signatures in transactions on the network. From block height [478559](https://whatsonchain.com/block-height/478559) Miners renamed the network to Bitcoin Cash (BCH). Miners who elected to support the addition of SegWit cloned the ledger giving all Bitcoin holders a duplicate set of coins thus creating the Bitcoin Core network. Shortly afterwards, the BTC protocol was modified to allow users to create and submit transactions using [SegWit](https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki) style scripts to the network for addition to the ledger.
3. Canonical Transaction Ordering (CTOR) and the change from BCH to BSV In the second half of 2018, nChain released a new mining client called SV Node with the goal of scaling the network and locking down protocol rules. Developers of the BitcoinABC node client which was predominantly used by Miners on the Bitcoin Cash network, released a roadmap that included a modification to the structure of blocks called Canonical Transaction Ordering ([CTOR](https://medium.com/@Bitcoin_ABC/benefits-of-canonical-transaction-order-ec30ae62d955)). This, enforced a rule that required transactions inserted into the Merkle tree to be ordered by TXID and the addition of new opcodes, [OP\_CHECKDATASIG and OP\_CHECKDATASIGVERIFY](https://github.com/bitcoincashorg/bitcoincash.org/blob/master/spec/op_checkdatasig.md). The Miners who supported the development of SV Node did not endorse the addition of these changes, and they were not implemented in the node client. On November 15th 2018, the CTOR update was enabled in nodes following the BitcoinABC rule set. At block [556766](https://whatsonchain.com/block-height/556766), Bitcoin Miners using the changed protocol, duplicated the ledger and began adding blocks that used CTOR and the new opcodes into the new blockchain.
4. Mining on the Bitcoin network with BitcoinSV Development of SV Node, is funded by Miners who understand that the future of Bitcoin is through massive global scaling and who have begun works to build new infrastructure and software to improve the transactional capacity of the network. SV Node is currently the predominant mining client used by Miners on the Bitcoin network to mine blocks that extend the original Bitcoin ledger.
5. Bitcoin V1.0 and the return to Genesis Since the release of SV Node, Bitcoin has undergone a series of upgrades which have removed limits that have impacted the network's throughput and re-enabled features that had been disabled or removed. In February 2020, the Bitcoin network underwent the Genesis upgrade, which removed all remaining limitations on the Bitcoin protocol in favour of Miner-configurable setting allowing boundaries to be determined by economics and technical capability. The removed consensus rules included, limits on transaction size, script size, multi-signature usage, block size and more. The full list of changes is available (). The Bitcoin network is the highest performing public ledger network in the world.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://hub.bsvblockchain.org/wiki/introduction/bitcoin-satoshi-vision.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.