> 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/higher-learning/bsv-academy/bsv-enterprise/technical-details/the-network.md). # The Network The BSV network is the infrastructure all network users (applications, services, and users) rely upon, with the nodes sitting tightly connected at its core. Nodes are defined as systems which gather and process transactions, timestamping them into blocks through the process defined in Section 5 of the Bitcoin white paper. Driven by BSV's game changing economic incentives, the network spontaneously forms into a densely connected and highly robust small world network which allows the most capable nodes in the system to succeed in their roles as transaction validators by building blocks to extend the public ledger. It is the role of these operators to use these highly capable, purpose-built machines to construct the blockchain at the core of the system as part of a competitive enterprise within which they compete in a rapidly repeating game. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://hub.bsvblockchain.org/higher-learning/bsv-academy/bsv-enterprise/technical-details/the-network.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.