> For the complete documentation index, see [llms.txt](https://help.zke.com/symbol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.zke.com/symbol/taiko.md).

# TAIKO

* Issue Time

  \--
* Total Supply

  1,000,000,000 TAIKO
* Circulation

  \--
* White paper

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

  <https://taiko.xyz/>
* X Twitter

  <https://twitter.com/taikoxyz/>
* Discord

  <https://discord.gg/taikoxyz>
* Block Explorer

  <https://taikoscan.io/token/0xA9d23408b9bA935c230493c40C73824Df71A0975>

Taiko is a fully permissionless and decentralized Ethereum-equivalent ZK-Rollup. This means using Taiko is exactly the same as using Ethereum. Not only does Taiko support all EVM opcodes, but it supports the full JSON-RPC execution client API. Taiko is an L2 that derives it’s security from Ethereum. There is no centralized sequencer or provers, all operations are permissionless and community driven. Learn more about Taiko under our core concepts in the sidebar.

{% hint style="info" %}
Trade on ZKE Exchange：<https://www.zke.com/&#x20>;

Twitter：<https://twitter.com/ZKE\\_com&#x20>;

Telegram：<https://t.me/ZKEGlobal>

Support: <https://support.zke.com>
{% endhint %}


---

# 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:

```
GET https://help.zke.com/symbol/taiko.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.