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

# Contract addresses

{% hint style="info" %}
DKG V10 is live on **Base and Gnosis mainnet** and on **Base Sepolia testnet**. NeuroWeb mainnet is not yet selectable. The checked-in [`network/*.json`](https://github.com/OriginTrail/dkg/tree/main/network/README.md) files are the source of truth for network availability and active Hub addresses.
{% endhint %}

## TRAC token

TRAC is the ERC-20 utility token used across the DKG. The token contract address is different on each chain — use the one for the network your node operates on.

On **mainnet**, TRAC is the original token contract (unchanged from V8). On the active V10 testnet (**Base Sepolia**), V10 uses a freshly redeployed test-TRAC contract (different from the V8 one).

### Mainnet

| Network | TRAC token address                           |
| ------- | -------------------------------------------- |
| Base    | `0xa81a52b4dda010896cdd386c7fbdc5cdc835ba23` |
| Gnosis  | `0xEddd81E0792E764501AaE206EB432399a0268DB5` |

### Testnet

| Network      | TRAC token address                           |
| ------------ | -------------------------------------------- |
| Base Sepolia | `0x2A58BdD13176D85906D804cdbFFA0D9119282DC8` |

{% hint style="info" %}
The test-TRAC faucet currently serves **Base Sepolia** only — that is the active V10 testnet. See the [deployments folder](https://github.com/OriginTrail/dkg/tree/main/packages/evm-module/deployments/README.md) for canonical deployed-network addresses.
{% endhint %}

## DKG smart contracts

The full set of DKG V10 contract deployments (Hub, Staking, Conviction, Random Sampling, ParametersStorage, …) lives in [`packages/evm-module/deployments`](https://github.com/OriginTrail/dkg/tree/main/packages/evm-module/deployments/README.md) — one file per deployed network, listing contract addresses and versions.

The **Hub** is the entry point — it resolves the addresses of every other V10 contract on a given network, so in most cases the Hub address is all you need. Note that V10 Hub addresses are **new** (they differ from V8 on every network, including mainnet).

| Network                | V10 Hub address                              |
| ---------------------- | -------------------------------------------- |
| Base (mainnet)         | `0x99Aa571fD5e681c2D27ee08A7b7989DB02541d13` |
| Gnosis (mainnet)       | `0x882D0BF07F956b1b94BBfe9E77F47c6fc7D4EC8f` |
| Base Sepolia (testnet) | `0xC056e67Da4F51377Ad1B01f50F655fFdcCD809F6` |

{% hint style="info" %}
Use the matching checked-in [network configuration](https://github.com/OriginTrail/dkg/tree/main/network/README.md) for node setup. The [deployments folder](https://github.com/OriginTrail/dkg/tree/main/packages/evm-module/deployments/README.md) contains the complete contract set for deployed networks.
{% 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, and the optional `goal` query parameter:

```
GET https://docs.origintrail.io/general/contract-addresses.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.