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

# Contract Addresses

## yoVaults

<table><thead><tr><th width="113.19140625">yoVault</th><th width="156.55859375">Deposit Chains</th><th width="284.44921875">yoVault and token address</th><th width="471.328125">Underlying Asset</th></tr></thead><tbody><tr><td>yoETH</td><td>Base, Ethereum</td><td>0x3a43aec53490cb9fa922847385d82fe25d0e9de7</td><td>WETH on Base: 0x4200000000000000000000000000000000000006<br><br>WETH on Ethereum: 0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2</td></tr><tr><td>yoUSD</td><td>Base, Ethereum, Arbitrum, Katana, X-Layer</td><td>0x0000000f2eb9f69274678c76222b35eec7588a65</td><td>USDC on Base: 0x833589fcd6edb6e08f4c7c32d4f71b54bda02913<br><br>USDC on Ethereum:<br>0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48<br><br>USDC on Arbitrum:<br>0xaf88d065e77c8cC2239327C5EDb3A432268e5831<br><br>vbUSDC on Katana:<br>0x203A662b0BD271A6ed5a60EdFbd04bFce608FD36<br><br>USD₮0 on X-Layer:<br>0x779Ded0c9e1022225f8E0630b35a9b54bE713736</td></tr><tr><td>yoUSDT*</td><td>Ethereum</td><td>0xb9a7da9e90d3b428083bae04b860faa6325b721e</td><td>USDT on Ethereum: 0xdac17f958d2ee523a2206206994597c13d831ec7</td></tr><tr><td>yoUSD Edge</td><td>Base, Ethereum, Arbitrum</td><td>0x5dd8bfa6c5c68d05d25ef6143e05c11e26c4cdb7</td><td>USDC on Base: 0x833589fcd6edb6e08f4c7c32d4f71b54bda02913<br><br>USDC on Ethereum:<br>0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48<br><br>USDC on Arbitrum:<br>0xaf88d065e77c8cC2239327C5EDb3A432268e5831</td></tr><tr><td>yoGOLD</td><td>Ethereum</td><td>0x586675A3a46B008d8408933cf42d8ff6c9CC61a1</td><td>XAUt on Ethereum: 0x68749665FF8D2d112Fa859AA293F07A622782F38</td></tr><tr><td>yoBTC</td><td>Base, Ethereum</td><td>0xbcbc8cb4d1e8ed048a6276a5e94a3e952660bcbc</td><td>cbBTC on Base: 0xcbb7c0000ab88b473b1f5afd9ef808440eed33bf<br><br>cbBTC on Ethereum:<br>0xcbb7c0000ab88b473b1f5afd9ef808440eed33bf</td></tr><tr><td>yoEUR</td><td>Base, Ethereum</td><td>0x50c749ae210d3977adc824ae11f3c7fd10c871e9</td><td>EURC on Base: 0x60a3E35Cc302bFA44Cb288Bc5a4F316Fdb1adb42<br><br>EURC on Ethereum:<br>0x1aBaEA1f7C830bD89Acc67eC4af516284b1bC33c</td></tr><tr><td>yoSOL</td><td>Solana</td><td><strong>Mint:</strong> yoSoLJkgRYFwmt8apEDVKxHy6FktjYEWLvxB6NyJuNj<br><br><strong>Program:</strong> yvSoLSBaLoqZ2yQttGbaYzHDXr9Bo9UdqtiRDiVaMxP</td><td>SOL on Solana:<br>So11111111111111111111111111111111111111111</td></tr></tbody></table>

\*yoUSDT accepts **USDT** as the deposit asset, whereas yoUSD accepts USDC. Both vaults have the same underlying exposure and yield.

## yoGateway

<table><thead><tr><th width="154.6640625">Contract</th><th width="244.69921875">Address</th><th width="144.69921875">Chains</th><th>Description</th></tr></thead><tbody><tr><td>yoGateway</td><td>0xF1EeE0957267b1A474323Ff9CfF7719E964969FA</td><td><p>Base, </p><p>Ethereum, Arbitrum</p></td><td>Single entry point into all yoVaults to facilitate integrations. <a href="/pages/5ArS74Cet0964KiJS2Nh">Learn more</a>.</td></tr><tr><td>Vault Registry</td><td>0x56c3119DC3B1a75763C87D5B0A2C55E489502232</td><td><p>Base, </p><p>Ethereum, Arbitrum</p></td><td>Authoritative registry of all active yoVaults. </td></tr></tbody></table>

## Core Protocol

<table><thead><tr><th width="150.8515625">Contract</th><th width="254.55859375">Address</th><th width="138.390625">Chain</th><th width="284.625">Description </th></tr></thead><tbody><tr><td>YO Oracle</td><td>0x6E879d0CcC85085A709eBf5539224f53d0D396B0</td><td>EVMs</td><td>This contract is used to manage the oracle data for yoVaults. It is used to store the latest price for each vault.</td></tr><tr><td>YO Timelock</td><td>0x38cE5e45D0f5d03E83863bb19B3b1A272C186F48</td><td>EVMs</td><td>Authority that gates contracts upgrades behind a 48 hr timelock.</td></tr><tr><td>YO Admin Multisig</td><td>0x67b6F699F1c8040414032a3C2C88a54db144FCd2</td><td>EVMs</td><td>Overall manager for all yoVaults, including contract upgrades, and whitelisting new protocols and pools.</td></tr><tr><td>YO Admin Multisig</td><td>9PVwkaG7tEqxVW5jZmeYjXiWMgnvQi6crDB67j2mbovq</td><td>Solana</td><td>Overall manager for all yoVaults, including contract upgrades, and whitelisting new protocols and pools.</td></tr><tr><td>YO Operator Multisig</td><td>0x93e5260ac975b475af8bf818c14deee7fefd5927</td><td>EVMs</td><td>Allowed only to rebalance assets among whitelisted contracts.</td></tr><tr><td>YO Operator Multisig</td><td>EF9p1k8UzKG6jNxkPRVemyaCD9eHiRf6MDfo57AmM717</td><td>Solana</td><td>Allowed only to rebalance assets among whitelisted contracts.</td></tr><tr><td>Roles authority</td><td>0x9524e25079b1b04D904865704783A5aA0202d44D</td><td>EVMs</td><td>Manages which addresses have specific roles within the yoVaults</td></tr><tr><td>Onchain worker</td><td>0x5c28b54e7e1f9aafbdc5c563c1a460106f41bd58</td><td>EVMs</td><td>Allowed to execute arbitrary tasks like harvest rewards or unwind positions to refill vaults' idle capital.</td></tr><tr><td>Redeemer</td><td>0x0439e941841f97dc1334d1a433379c6fcdcc2162</td><td>EVMs</td><td>Processes async withdrawals as soon as liquidity is available</td></tr><tr><td>Emergency pauser</td><td>0xaa06ac3cb11b84c1d1094818341b4796c2b43c71</td><td>EVMs</td><td>Can pause individual vaults should it detect anomalies</td></tr></tbody></table>

Individual address roles can be verified using the RolesAuthority contract on the respective chain.&#x20;

### Onchain Adapters

<table><thead><tr><th width="231.89453125">Contract</th><th width="283.78515625">Address</th><th width="326.52734375">Description</th></tr></thead><tbody><tr><td>YoApprovalRegistry</td><td>0xB4b3F5C964A360bBd7201f72a55D0c48B8aD7021 (EVMs)</td><td>Controls which contracts can use assets for each vault. Contracts not declared here cannot be set as "spenders" in token approval transactions. Each vault requires its own set of permitted contracts. </td></tr><tr><td>YoMorphoMarketRegistry</td><td>0xcB9737BdD076251744704cc37CE961E8417fDd7f <br>(EVMs)</td><td>Controls which Morpho Markets can be allocated to from each vault. Permissions are granted individually by vault.</td></tr><tr><td>YoSwapPairRegistry</td><td>0xcff9d39441eB668C7fffa752aD1eA47930bB8A76<br>(EVMs) </td><td>Controls which swap routes are permitted for each vault and how to validate the price of the swaps.</td></tr><tr><td>YoERC4626VaultRegistry</td><td>0x7bad596c26e175384Bd9985Cb97C6c3f7e158b6F<br>(EVMs)</td><td>Controls which ERC4626 vaults can be allocated to for each vault. Permissions are granted individually by vault. </td></tr><tr><td>YoChainlinkOracle</td><td>0x2800FC940a9B3BCB2CDE3c70797b21296BEcbf07<br>(EVMs)</td><td>Fetches the onchain price of a specific swap pair from whitelisted oracle sources</td></tr><tr><td>YoMorphoAdapter</td><td><p>0x93A3A3325dE6aB429523D144b41A032e7D7456Ab (EVMs)<br><br>0x946FD049C47BeFF53a32588C67df6a5A16B805F0 (HyperEVM only)     </p><p>       0x2BcB71309554A5DC31932Cb3D5A547Cd8cc5ED26 (Monad only)     </p></td><td>Onchain adapter to interact with Morpho Markets that enforces the receiver of market shares and assets is always the corresponding yoVault. Never holds user assets. </td></tr><tr><td>YoSwapAdapter</td><td>0xa425d3c9A1c048BE1183d8e396406bdA813b4826 (EVMs)</td><td>Onchain adapter that routes swaps through a whitelisted DEX aggregator, while enforcing price protections directly onchain. Never holds users assets.</td></tr><tr><td>YoERC4626Adapter</td><td>0x206fF3F58F57d00c48aF6010De6dC26f913eFd64 (EVMs)</td><td>Onchain adapter that lets yoVaults interact with ERC4626-compliant third-party vaults, while enforcing that the receiver of the vault shares and assets is always the corresponding yoVault. Never holds users assets.</td></tr><tr><td>YoIPORAdapter</td><td>0x4409446B49E24861697d566e5c6D68C0d8F3C50f<br>(EVMs)</td><td>Onchain adapter that lets yoVaults interact with IPOR-Fusion third-party vaults, while enforcing that the receiver of the vault shares and assets is always the corresponding yoVault. Never holds users assets.</td></tr><tr><td>YoLidoAdapter</td><td>0xF837334c5c48F16A8A73aFFb09859Bb7FDB467E0<br>(Ethereum)</td><td>Onchain adapter that lets yoVaults interact with the Lido ETH staking protocol, while enforcing that the receiver of the assets is always the corresponding yoVault. Never holds users assets.</td></tr><tr><td>YoCCTPAdapter</td><td><p>0x4d8aC89776B548356e30372521F4835fa67eD298 (Ethereum)</p><p></p><p>0x6ab918019D5F7C155AAb21b7Bd22c0aC7897b4c5 (Arbitrum)</p><p></p><p>0xe1CFEcD5292fa1e6B098cA85E10181E3675C7fa4 (Base)<br><br>0xBb3c2B36E8517E03515C08F8A31e2746649917f4 (HyperEVM)</p></td><td>Ensures transfers of assets via the Cross-chain Transfer Protocol by Circle are relayed securely</td></tr><tr><td>YoMayanAdapter</td><td>0xbAF91d1A64e9A86C400E3DEeA4Eb97Cf631252dA (Ethereum &#x26; Base)</td><td>Ensures transfers of assets via the Mayan protocol are relayed securely</td></tr><tr><td>YoCcipAdapter</td><td>0x41E2Ae2271FD724DB474fD8F25012DeAdF2ad39f (Ethereum)<br><br>0x66C55881460Db8878BE2AfFbA36A15434cb12382 (Base)</td><td>Ensures transfers of assets via the Cross-chain Interop Protocol by Chainlink are relayed securely</td></tr><tr><td>YoAcrossAdapter</td><td>0x4A7104BE83093C3e1520259DA83d02461d6C7876 (Ethereum)<br><br>0xed8E485c8e48917090830822Fa86465A2366f8cC (Base)</td><td>Ensures transfers of assets via the Across protocol are relayed securely</td></tr></tbody></table>

## YO token

| Contract                             | Address                                    |
| ------------------------------------ | ------------------------------------------ |
| YO token                             | 0x1925450f5e5fb974b0aae1f3408cf5286fbd1a72 |
| Mint authority                       | 0xAE11F170491EDF4a139e32386153936792A3D262 |
| Genesis airdrop wallet               | 0x3502a1Ad809a0D948c42Ae3e76B3893aB5bc38a5 |
| Genesis airdrop distributor contract | 0x18A381Ba65F56D00516EB93eCb5C480aBA9E6aEc |
| Ecosystem fund                       | 0xa978230949A0d877d8ef5F1492488945D975e61F |
| Community fund                       | 0x5457E23c1f339c38dd52FD75e64Af97162Def04C |
| Core contributors allocation         | 0x0c580Ba64C5c06E941AEB98E95509c48b32BE89b |
| Investor allocation                  | 0x73AF93301E42190e71ed0E65E06E300d63C7e07d |


---

# 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.yo.xyz/protocol/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.