> 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/home-page.md).

# Home Page

Here we aim to provide a correct and up-to date set of information on the Bitcoin network and its features and functionality.

1. What is Bitcoin? **Bitcoin** is a peer to peer electronic cash system created by **Satoshi Nakamoto**. It was first detailed in the [Bitcoin Whitepaper](https://bsvassociation.org/wp-content/uploads/2025/06/bitcoin.pdf) in October 2008, and the source code was [released](https://www.mail-archive.com/cryptography@metzdowd.com/msg10142.html) in January 2009. The Bitcoin ledger and Blockchain were established with the generation of the Genesis block on the 3rd of January 2009 and the mining of Block 1 six days later on the 9th of January 2009. Bitcoin allows electronic payments to be sent directly from one party to another, without requiring a central institution or server to process transactions and/or store funds. The leaderless structure of the network is viewed as a resolution to The Byzantine Generals Problem allowing disconnected entities to follow a common direction without centralised instruction. This solves several issues previously seen as unsolvable in distributed networks, including the problem of preventing Double-spending of coins. 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. BitcoinSV will maintain the vision set out by Satoshi Nakamoto’s visionary 2008 white paper titled Bitcoin: A Peer-to-Peer Electronic Cash System 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.

## Topic central

**Wallets**

* Handcash
* Centbee
* RelayX
* Simply Cash
* ElectrumSV

**Node Software**

* [Bitcoin SV](https://bsvblockchain.org)

**Development Tools**

* bsv JS library
* gobitcoinsv.com

**Helpful Links**

* Opcodes used in Bitcoin Script
* Bitcoin Transactions
* Bitcoin Whitepaper
* Block Explorers
* Whatsonchain


---

# 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/home-page.md?ask=<question>&goal=<endgoal>
```

`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.
