> For the complete documentation index, see [llms.txt](https://docs.znsconnect.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.znsconnect.io/developer-guide/contract-address.md). # ZNS Contract Addresses List of Mainnets and Testnets {% hint style="success" %} All contracts are verified on their respective networks. {% endhint %}
### Lists of Mainnet chains of ZNS Integration
ChainContract AddressCover image
Ink Network0xFb2Cd41a8aeC89EFBb19575C6c48d872cE97A0A5ink.jpg
Unichain Network0xf180136DdC9e4F8c9b5A9FE59e2b1f07265C5D4DUnichain.jpg
Soneium Network0x2253F8BE85A2505b89fD5E8BcD3Bb915bbd8A6A3Soneium.jpg
Plume Mainnet0xf180136DdC9e4F8c9b5A9FE59e2b1f07265C5D4DPlume.jpg
Hemi Network0xf180136DdC9e4F8c9b5A9FE59e2b1f07265C5D4Dhemi.jpg
XRPL EVM Side Chain0xf180136DdC9e4F8c9b5A9FE59e2b1f07265C5D4DScreenshot 2025-04-02 at 13.29.28.png
Kaia Network0xf180136ddc9e4f8c9b5a9fe59e2b1f07265c5d4dKaia.jpg
Hyperliquid0x55B867a955e4384bcAc03eF7F2E492F68016C152Hyperliquid.png
Abstract Mainnet0xe0971a2B6E34bd060866081aE879630e83C4A0BDAbstract.jpg
BNB Chain Registry 0x7e2cf06f092c9f5cf5972ef021635b6c8e1c5bb2bnb chain.png
Blast Registry0x59B9Ac688e39A14b938AC8C3269db66D8aDB9aF6Blast.jpeg
Scroll Registry0xB00910Bac7DA44c0D440798809dbF8d51FDBb635Scroll.jpeg
Polygon Registry0x8ccD9c0A9C084412416A85Fd748c7f1E9b86442Dpolygon.jpeg
Taiko Registry0xFb2Cd41a8aeC89EFBb19575C6c48d872cE97A0A5Taiko.jpg
Zora Registry 0xf180136DdC9e4F8c9b5A9FE59e2b1f07265C5D4Dzora (1).jpg
Base Network0x55B867a955e4384bcAc03eF7F2E492F68016C152base.jpg
Berachain Mainnet0xFb2Cd41a8aeC89EFBb19575C6c48d872cE97A0A5Berachain_Orange.png
Sonic Network0xFb2Cd41a8aeC89EFBb19575C6c48d872cE97A0A5sonic.jpg
Coti Network0x4293b8907d403b397A4050ebc92a4722aa600720COTI.jpg
Katana Network0x55B867a955e4384bcAc03eF7F2E492F68016C152Katana.jpg
Kaia Network0x59b9ac688e39a14b938ac8c3269db66d8adb9af6Kaia.jpg
### Lists of Testnet chains of ZNS Integration
ChainContract Address
Somnia Testnet0xf180136DdC9e4F8c9b5A9FE59e2b1f07265C5D4DSomnia.jpg
Kite AI0xf180136DdC9e4F8c9b5A9FE59e2b1f07265C5D4DKITE AI.jpg
Tabi Testnet0xf180136DdC9e4F8c9b5A9FE59e2b1f07265C5D4Dtabi logo.jpeg
Creator Testnet0x12e82FEd1f64C10783Dd780151ac80e734AF9ae3Sign - 2.png
Monad Testnet0xf180136DdC9e4F8c9b5A9FE59e2b1f07265C5D4DMonad.jpg
Sahara Testnet0x59B9Ac688e39A14b938AC8C3269db66D8aDB9aF6Sahara AI.jpg
Nexus Testnet0xf180136DdC9e4F8c9b5A9FE59e2b1f07265C5D4Dnexus.jpg
--- # 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.znsconnect.io/developer-guide/contract-address.md?ask=&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.