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

# Deployment Addresses

{% hint style="warning" %}
This document is currently subject to review before being finalized. If you notice a revision that needs to be made or have feedback, please [request a revision](https://github.com/connext/gitbook-docs/issues/new) or start a conversation with us on Discord at <https://discord.com/invite/everclear>
{% endhint %}

### Spoke Deployments

The contracts deployed to Spokes act as the entry point to execute actions in the Tokenomics system.

#### Deployments: Ethereum mainnet and Gnosis.

<table><thead><tr><th width="283">Name</th><th>Contract Address</th></tr></thead><tbody><tr><td>SpokeBridge</td><td>0x420148270e6144cF761eFCD184F3B7FBF034977f</td></tr><tr><td>SpokeGateway Proxy</td><td>0x949B77D01cbd5da47d07A7331967E4d9C164259B</td></tr><tr><td>SpokeGateway Implementation</td><td>0x9a5E2eF9f11bBd161580704b632cFDa7EEfd34a1</td></tr></tbody></table>

#### Deployments: Arbitrum, Optimism, BSC, and Polygon.

<table><thead><tr><th width="282">Name</th><th>Contract Address</th></tr></thead><tbody><tr><td>SpokeBridge</td><td>0x9707bfE566f883a1C1b6fBADC01E4eD7bC3DE7D4</td></tr><tr><td>SpokeGateway Proxy</td><td>0xF469AE6f97208FEAbc7B9b87aD29F124057085Ca</td></tr><tr><td>SpokeGateway Implementation</td><td>0x269e7A492789523a60DA4254431E6530b20Eeb6e</td></tr></tbody></table>

### Hub Deployments

The contracts deployed on Everclear's Hub chain receive messages from Spokes and execute actions related to Tokenomics.&#x20;

<table><thead><tr><th width="190">Name</th><th>Contract Address</th></tr></thead><tbody><tr><td>HubGateway Proxy</td><td>0xEc86D47d98EeeF824Ff79fAE2cFA3Fd57Ab87F9D</td></tr><tr><td>HubGateway Implementation</td><td>0xa5A054E9c75746c29C505d8b93be41F8eE6EA177</td></tr><tr><td>HubBridge</td><td>0xB562b53562627d635E202FB02E63bEC3cA904f17</td></tr><tr><td>vbCLEAR</td><td>0x1150F8902f051258A584897125269034f0246310</td></tr><tr><td>HubGauge</td><td>0x9831fE53Ca8A16b950c17fBC4C12289a61aF06A5</td></tr><tr><td>RewardDistributor</td><td>0xFBe70488c65cA4C5445f44f496ba034A126cF0b4</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 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://dao-docs.everclear.org/clear/deployment-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.