> For the complete documentation index, see [llms.txt](https://gitbook.dabba.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.dabba.network/onchain-data.md).

# Onchain data

:warning:TESTNET

Playground: <https://dabba-onchain-mvp.vercel.app/><br>

The onchain representation of the Dabba network is represented by the following primitives:\
\
**NFTs**\
We use NFT's to represent the Hotspot device, Hotspot owner and LCO partner. Compressed NFTs are used for efficiency as well as cost.&#x20;

**Merkle trees**\
Bandwidth and Payments data are stored on chain using merkle trees for cost and efficiency. Raw data is available on IPFS/Arweave.

PDAs\
PDAs are used in conjunction with NFTs to store additional attributes and metadata

Registries\
Registries are used for lookup style data like city, state, etc.

Contracts\
Mint, stake and reward contracts will contain logic of token creation and interaction.


---

# 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://gitbook.dabba.network/onchain-data.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.