> 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/bridging-trac.md).

# Bridging TRAC

TRAC is an ERC-20 token that originates on Ethereum. To use it on a DKG network — for funding nodes, staking, or publishing — you bridge it to that network. The TRAC token address on each chain is on the [Contract addresses](/general/contract-addresses.md) page.

## Base

Bridge TRAC from Ethereum to Base with [Superbridge](https://superbridge.app/base) (or any other Base bridge). See the [Base documentation](https://docs.base.org/) for more on bridging.

## Gnosis

Bridge TRAC from Ethereum to Gnosis with the [official Gnosis bridge](https://bridge.gnosischain.com/) or [OmniBridge](https://omnibridge.gnosischain.com/bridge).

## NeuroWeb

NeuroWeb is a permissionless, EVM-enabled Polkadot parachain; its native token is **NEURO** (used for gas). It evolved from the original OriginTrail Parachain via a December 2023 community governance vote. Dedicated docs live at [docs.neuroweb.ai](https://docs.neuroweb.ai/).

Bridge TRAC between Ethereum and NeuroWeb via [Snowbridge](https://app.snowbridge.network/). Step-by-step instructions are in the [NeuroWeb documentation](https://docs.neuroweb.ai/ethereum-neuroweb-trac-bridge).

### Adding TRAC on NeuroWeb to your wallet

The TRAC token address is the same on NeuroWeb mainnet and testnet:

```
0xFfFFFFff00000000000000000000000000000001
```

In MetaMask (connected to NeuroWeb): open **Assets → Import tokens** → paste the address above (the other fields auto-populate) → **Add custom token**. Your TRAC balance will then display.


---

# 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.origintrail.io/general/bridging-trac.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.