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

# Tech Specs

Onta Network represents a groundbreaking payment infrastructure that seamlessly bridges traditional financial systems with blockchain technology. This innovative platform enables frictionless, compliant offline payments through its comprehensive suite of technologies. By leveraging advanced account systems, stablecoin payment capabilities, decentralized identity infrastructure, and robust compliance features, Onta Network creates a secure, user-friendly ecosystem that eliminates the traditional barriers to cryptocurrency adoption. The platform is designed to deliver the security and transparency benefits of blockchain while maintaining the simplicity and convenience of conventional payment methods. Through its eight core technical features, Onta Network establishes a new paradigm for digital transactions that prioritizes user experience, regulatory compliance, and seamless integration with existing financial infrastructure.

Onta Network is powered by 8 key technologies:

* **VaultLink**—Passkey-secured smart wallets eliminating seed phrases;
* **NeuroID**—W3C DID and VC with selective disclosure via ZKP;
* **Sentinel**—Protocol-level compliance without compromising privacy;
* **ZeroPulse**—instant and gasless stablecoin payment layer;
* **TapCore**—Industry-first NFC tap-to-pay on POS terminals;
* **CardHash**—Converting payment cards into blockchain wallets;
* **TraceShield**—auditable on-chain transactions protected by ZKP;
* **SyncMesh**—Direct integration with global payment networks.


---

# 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://docs.onta.network/basics/interactive-blocks.md?ask=<question>&goal=<user_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.