> 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/bitcoin-protocol-documentation/specification.md). # Specification - [Transactions](https://hub.bsvblockchain.org/bitcoin-protocol-documentation/specification/transactions.md): Data structure composition of a transaction - [Script](https://hub.bsvblockchain.org/bitcoin-protocol-documentation/specification/script.md): Understanding basics of Script and stack based compilation - [Opcodes](https://hub.bsvblockchain.org/bitcoin-protocol-documentation/specification/opcodes.md): Every Script opcode — value, operand, stack effect, and era status - [Signature Hashing](https://hub.bsvblockchain.org/bitcoin-protocol-documentation/specification/signature-hashing.md): Sighash flags and the transaction signature-hash (digest) algorithms - [Blocks](https://hub.bsvblockchain.org/bitcoin-protocol-documentation/specification/blocks.md): Block and block-header structure, serialization, and validity - [Consensus Rules](https://hub.bsvblockchain.org/bitcoin-protocol-documentation/specification/consensus-rules.md): The rules that define the protocol used for the blockchain - [Protocol Upgrade History](https://hub.bsvblockchain.org/bitcoin-protocol-documentation/specification/upgrade-history.md): The consensus upgrade timeline — which validity rules apply at which height --- # 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/bitcoin-protocol-documentation/specification.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.