> For the complete documentation index, see [llms.txt](https://dc-ai.gitbook.io/dcai-ecosystem/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dc-ai.gitbook.io/dcai-ecosystem/technical-infrastructure/why-base-chain.md).

# Why Base Chain?

**Hyper-Scalability:** Architected for high-frequency transactions and concurrent computation, enabling seamless AI-data interactions and near-instant user confirmations. DCAI brings the AI inference cost further down via our DCAI-EMBEDDING database engine.\
\
**Ultra-Low Latency Fees:** Gas optimization on Base unlocks micro-economies and frictionless on-chain intelligence execution.\
\
**Zero-Trust Security:** Inherits Ethereum’s L1 cryptographic finality through rollup mechanisms, ensuring tamper-proof consensus.\
\
**Developer-Centric Stack:** Equipped with state-of-the-art development tools, Base catalyzes rapid iteration and third-party innovation.\
\
**Frictionless Interoperability:** Native bridges and standards compliance enable integration with the Base mainnet and its vast liquidity landscape.\
\
DCAI utilizes Base Chain as the operational core for its smart contracts, staking system, tokenomics, and node infrastructure—ensuring high performance and compatibility across all layers of the ecosystem.


---

# 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://dc-ai.gitbook.io/dcai-ecosystem/technical-infrastructure/why-base-chain.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.