> 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-network-topology/essentials-of-overlay-services/integration-with-spv-and-infrastructure-dependencies.md).

# Integration with SPV and Infrastructure Dependencies

<figure><img src="https://3421145409-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRTEKu4E7Fvtss3GI9CYU%2Fuploads%2Ftr80SQV7yHsnBhdqBtEZ%2FspV.gif?alt=media&amp;token=383fe5bf-92f3-4905-add0-b913a8d087fb" alt=""><figcaption></figcaption></figure>

All overlay systems within the **Mandala architecture** operate dedicated **Simplified Payment Verification (SPV)** mechanisms, ensuring both validity and scalable integration with the blockchain. Overlay services utilize **Merkle proofs** to verify the authenticity and integrity of transactions without necessitating access to the full blockchain data. This capability allows each overlay network to serve data back to applications with absolute certainty regarding its validity, thereby enhancing performance, scalability, and efficiency.

The infrastructure dependencies for overlay services include:

* **BSV Node Network**: Essential for new header announcements and transaction submissions.
* **Merkle Service**: Facilitates the efficient calculation of Merkle paths, with a scaled Merkle Service set to replace ARC's microservice BlockTx due to the anticipated increase in block sizes.
* **SPV Data Structures**: Widely utilized within wallets and applications to enable a peer-to-peer paradigm.

These dependencies collectively provide a **cost-effective**, **scalable**, and **secure** solution for businesses, ensuring data integrity and network resilience.


---

# 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/higher-learning/bsv-academy/bsv-network-topology/essentials-of-overlay-services/integration-with-spv-and-infrastructure-dependencies.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.
