> For the complete documentation index, see [llms.txt](https://docs.chiliz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chiliz.com/quick-start/developer-toolbox.md).

# Developer Toolbox

Mainnet and Spicy Testnet RPC parameters, free CHZ testnet faucets, contract deployment and verification guides, and Docker node launch commands.

## Connect to Mainnet and Testnet

Chiliz Chain is available through a Mainnet for your production projects, and has a Testnet for testing purposes. The Chiliz Testnet is called Spicy Testnet.

{% tabs %}
{% tab title="Chiliz Chain Mainnet" %}

<table><thead><tr><th width="253">Parameter</th><th width="346">Value</th></tr></thead><tbody><tr><td>Network Name</td><td>Chiliz Chain</td></tr><tr><td>RPC endpoint</td><td>Recommended:<br><a href="https://rpc.ankr.com/chiliz">https://rpc.ankr.com/chiliz</a><br><br>Alternatives:<br><a href="https://chiliz-mainnet.gateway.tatum.io">https://chiliz-mainnet.gateway.tatum.io</a><br><a href="https://chiliz-rpc.publicnode.com">https://chiliz-rpc.publicnode.com</a></td></tr><tr><td>RPC Websocket</td><td>wss://chiliz-rpc.publicnode.com</td></tr><tr><td>Chain ID</td><td>88888</td></tr><tr><td>Currency Symbol</td><td>CHZ</td></tr><tr><td>Chiliz Block Explorer URL</td><td>Recommended:<br><a href="https://chiliscan.com">https://chiliscan.com</a><br><br>Alternative:<br><a href="https://scan.chiliz.com">https://scan.chiliz.com</a></td></tr></tbody></table>
{% endtab %}

{% tab title="Spicy Testnet" %}

<table><thead><tr><th width="253">Parameter</th><th width="312">Value</th></tr></thead><tbody><tr><td>Network Name</td><td>Spicy Testnet</td></tr><tr><td>RPC endpoint</td><td>Recommended:<br><a href="https://spicy-rpc.chiliz.com/">https://spicy-rpc.chiliz.com/</a><br><br>Alternatives:<br><a href="https://chiliz-testnet.gateway.tatum.io">https://chiliz-testnet.gateway.tatum.io</a><br><a href="https://chiliz-spicy-rpc.publicnode.com">https://chiliz-spicy-rpc.publicnode.com</a></td></tr><tr><td>RPC Websocket</td><td>Recommended:<br>wss://spicy-rpc-ws.chiliz.com/<br><br>Alternative:<br>wss://chiliz-spicy-rpc.publicnode.com</td></tr><tr><td>Chain ID</td><td>88882</td></tr><tr><td>Currency Symbol</td><td>CHZ</td></tr><tr><td>Spicy Block Explorer URL</td><td><p>Recommended:<br><a href="https://testnet.chiliscan.com/">https://testnet.chiliscan.com/</a></p><p><br>Alternative:<br><a href="https://spicy-explorer.chiliz.com/">https://spicy-explorer.chiliz.com/</a></p></td></tr></tbody></table>
{% endtab %}
{% endtabs %}

For more information, see the [Connect using RPC](/develop/basics/connect-to-chiliz-chain/connect-using-rpc.md) page.

## Obtain testnet tokens

You can obtain free test CHZ tokens through a faucet, allowing you to experiment on Spicy Testnet without the financial risk of testing on Chiliz Mainnet.

There are currently two faucets available:

* [Spicy Faucet](https://spicy-faucet.chiliz.com/).
* [Tatum's Chiliz Faucet for Testnet](https://tatum.io/faucets/chiliz).

For more details on faucets, go to our dedicated page:

{% content-ref url="/pages/Af9548Yd4RQMNgtsUkq9" %}
[Obtain Free Testnet Tokens](/develop/basics/obtain-free-testnet-tokens.md)
{% endcontent-ref %}

## Deploy and verify a contract

Building a smart contract is an essential part of the creative project that leads to a dApp for Chiliz Chain (or any blockchain, really).

There are two steps that you **must** go through once you have built your dApp's smart contract:

1. Deploying the contract on Chiliz Chain.

{% content-ref url="/pages/zTkQQLpwajpWEoLHUp1b" %}
[Deploy a Smart Contract](/develop/basics/deploy-a-smart-contract.md)
{% endcontent-ref %}

2. Verifying that contract.

{% content-ref url="/pages/Lxl4NxqCWg16RmKF2Iln" %}
[Verify a Smart Contract](/develop/basics/verify-a-smart-contract.md)
{% endcontent-ref %}

## Solidity & EVM version

When writing and compiling contracts for Chiliz Chain, use the recommended Solidity and EVM versions:

{% hint style="info" %}
**Recommended Solidity and EVM versions for Chiliz Chain:**

* **Solidity compiler version:** `0.8.30` (or lower)
* **Target EVM version:** `prague`
  {% endhint %}

## Run a Chiliz Chain Node

Running your own Chiliz Chain node provides control and privacy but demands more technical skill and resources.

This page gives you the essential parameters to launch your node:

```bash
docker run \
-v $(pwd)/my-datadir:/datadir \
--name ccv2-node \
-p 8545:8545 \
-p 8546:8546 \
chilizchain/ccv2-geth:latest \
--chiliz \ # for Chiliz Mainnet. Use --spicy for Spicy Testnet.
--datadir=/datadir \
--ipcdisable \
--http \
--http.addr=0.0.0.0 \
--http.api=eth,net,web3,debug,txpool \
--http.port=8545 \
--http.corsdomain="*" \
--http.vhosts="*" \
--ws \
--ws.addr=0.0.0.0 \
--ws.api=eth,net,web3,debug,txpool \
--ws.port=8546 \
--ws.origins="*" \
```

For more details, check this more complete page:

{% content-ref url="/pages/9YZsEmPaaQYP2h1RqyS1" %}
[Run a Chiliz Chain Node](/develop/basics/connect-to-chiliz-chain/run-a-chiliz-chain-node.md)
{% endcontent-ref %}

Also, you might be interested in running a Validator node:

{% content-ref url="/pages/ppcymFdm3NKLps6cECR9" %}
[Running a Validator node](/learn/about-validators/running-a-validator-node.md)
{% endcontent-ref %}


---

# 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.chiliz.com/quick-start/developer-toolbox.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.