> 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/images-and-media.md).

# Solution

### Design Philosophy

Designing a viable Web3 payment network requires more than technical execution—it demands a clear methodology for resolving the deep structural tensions between traditional finance and decentralized systems. Our approach is guided by three core trade-offs:

* **Compliance vs. Permissionlessness**\
  Regulatory compliance is essential for legal and commercial viability. Yet blockchain’s promise lies in its openness and neutrality. We believe the solution is not to dilute either side, but to build transparent, rule-based systems that align with regulation without undermining the foundational values of Web3.
* **User Familiarity vs. System Innovation**\
  Effective payments must match users’ behavioral expectations. We retain the seamless experience of Web2—no gas fees, support for refunds, intuitive interfaces—while fundamentally rearchitecting the backend to leverage the efficiency and trustlessness of decentralized infrastructure.
* **Infrastructure Robustness vs. Deployment Agility**\
  Payments require reliability, security, and feature completeness. But global adoption also depends on speed and adaptability. Our system is engineered to be lightweight yet comprehensive, ensuring rapid integration with minimal overhead while solving real-world problems at scale.

We see these tensions not as barriers, but as design constraints that force better solutions. Onta Network is built from the ground up with these principles in mind: **pragmatic, modular, and globally scalable.**

<br>


---

# 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/images-and-media.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.