> 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/legal-compliance-through-verifiable-proof/regulatory-requirements-satisfied-by-spv-proofs.md).
# Regulatory Requirements Satisfied by SPV Proofs
Different regulatory frameworks impose specific record-keeping requirements that SPV proofs can satisfy. **Financial regulations** such as anti-money laundering (AML) laws require businesses to maintain transaction records showing parties involved, amounts transferred, and dates. SPV proofs provide all of this information in a format that demonstrates the records haven't been backdated or altered—a common concern in traditional compliance systems.
**Securities regulations** require broker-dealers and financial institutions to maintain detailed records of transactions, often with same-day reporting requirements for certain transaction types. SPV's ability to generate proofs immediately after block inclusion (average 5 minutes) enables real-time regulatory reporting with cryptographic verification of timing.
**Tax regulations** across jurisdictions require businesses to maintain records of income, expenses, and asset transfers. For businesses operating on blockchain platforms, SPV proofs provide the documentation necessary to substantiate tax filings. The timestamp in the block header provides indisputable proof of when transactions occurred, eliminating disputes about tax period attribution.
---
# 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/legal-compliance-through-verifiable-proof/regulatory-requirements-satisfied-by-spv-proofs.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.
