> For the complete documentation index, see [llms.txt](https://docs.amis13.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.amis13.tech/archive/web3crypt-rpcs/taiko.md).

# Taiko

Ethereum's high transaction costs are a concern, but Taiko offers a solution that reduces these costs while maintaining Ethereum's core properties of censorship resistance, permissionlessness, and security.

Taiko is a highly configurable, open-source, and community-run Ethereum-equivalent rollup. It can be set up as a ZK rollup, an optimistic rollup, or a hybrid, with no centralized control. The Taiko Protocol consists of smart contracts on Ethereum, and its governance, managed by the Taiko DAO, is built into these contracts. Supporting organizations include Taiko Labs for R\&D, the Taiko Treasury for funding, the Taiko Foundation for ecosystem growth, and the Taiko Security Council for emergency management.

Docs: <https://docs.taiko.xyz/start-here/getting-started/>

<figure><img src="/files/n0jE3M50xvN8IJ6KnI3u" alt=""><figcaption></figcaption></figure>


---

# 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.amis13.tech/archive/web3crypt-rpcs/taiko.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.
