> For the complete documentation index, see [llms.txt](https://docs.decoda.vip/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decoda.vip/1-introduction/welcome-to-decoda.md).

# Welcome to Decoda

The blockchain is often described as a public ledger. In reality, it is a dark forest. Data exists, but context is absent.

**Decoda is the ultimate analytical lens for the Base ecosystem.**

We didn't just build a scanner; we engineered a new way to see. From raw data to profound clarity, Decoda architectures autonomous provenance into a seamless experience. It is not enough to simply see the data. You must understand it.

#### The Decoda Difference

* **Intelligence, Refined:** We act as the signal in the noise.
* **Beyond the Byte Level:** Sovereign analytics that bring institutional-grade clarity to every wallet interaction.
* **Verified Truth:** Powered by ZK-based logic for ranking precision without compromise.

**Note:** Decoda is optimized specifically for the Base Chain, leveraging its speed and low costs to deliver real-time, high-fidelity insights.


---

# 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://docs.decoda.vip/1-introduction/welcome-to-decoda.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.
