> 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/how-spv-supports-legal-compliance-in-blockchain-technology/spv-fundamentals-and-architecture/a-note-on-full-nodes-vs.-spv.md). # A note on full nodes vs. SPV When this course compares SPV to running a full node, it does so purely to illustrate the **dramatic efficiency gains** SPV provides — not to suggest that running a full node is a realistic alternative for most developers. In practice, **full nodes exist to support mining**. They validate every transaction and every block so that miners can build on top of a verified chain and claim block rewards. If you are not a miner, there is no operational reason to run a full node — doing so would consume hundreds of gigabytes of storage and significant bandwidth **with no corresponding benefit**. **The practical baseline for non-miners:** SPV is not the "lightweight alternative" to a full node — it is the correct architecture. The comparison exists to help you understand what SPV's cryptographic proofs are equivalent to, not to frame full node operation as a valid choice for compliance applications. --- # 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/how-spv-supports-legal-compliance-in-blockchain-technology/spv-fundamentals-and-architecture/a-note-on-full-nodes-vs.-spv.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.