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

# TestNet

COTI Testnet serves as an experimental environment for developers and enthusiasts to explore COTI’s native blockchain technologies. It enables users to test new features, smart contracts, and the stability of network protocols without affecting the Mainnet. The Testnet offers an accessible platform for simulating transactions and network behavior, aiding in the detection and resolution of potential issues before deployment on the Mainnet. This sandbox environment is crucial for enhancing the robustness and reliability of COTI’s ecosystem.

To facilitate testing, developers can obtain free tokens from the Testnet Faucet (next page). This allows users to perform transactions and execute smart contracts without incurring any costs.

Testnet runs the same code as the COTI v2 Mainnet, designed to provide a pre-production environment for developers about to move to Mainnet.

| COTI TestNet                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| <ul><li>Network name: COTI Testnet</li><li>RPC URL: <a href="https://testnet.coti.io/rpc"><https://testnet.coti.io/rpc></a></li><li>WS URL: <a href="wss://testnet.coti.io/ws">wss\://testnet.coti.io/ws</a></li><li>Chain ID: 7082400</li><li>Currency symbol: COTI</li><li>Block explorer URL: <a href="https://testnet.cotiscan.io"><https://testnet.cotiscan.io></a></li><li>Testnet status page: <a href="https://uptime.coti.io/"><https://uptime.coti.io></a></li></ul> |

**Hard Forks**

<table><thead><tr><th width="219">Version</th><th width="223">Hard Fork</th><th>Block #</th></tr></thead><tbody><tr><td><a href="/coti-documentation/networks/release-notes/v1.1.4.md">v.1.1.4</a></td><td>hydrogen</td><td><ul><li>2,325,800</li><li>July 22, 2025 at 12:00 PM UTC</li></ul></td></tr><tr><td><a href="/coti-documentation/networks/release-notes/v1.2.0.md">v1.2.0</a></td><td>helium</td><td><ul><li>4,602,680</li></ul></td></tr></tbody></table>


---

# 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.coti.io/coti-documentation/networks/testnet.md?ask=<question>&goal=<user_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.