# Contract Addresses

All EcoRound contracts are deployed on a **Tenderly virtual fork of Base Mainnet** for the hackathon. This gives full mainnet state — real USDC, real Morpho — without spending real funds.

***

## Network

| Parameter    | Value                                                                                   |
| ------------ | --------------------------------------------------------------------------------------- |
| Network name | EcoRound Base (Tenderly)                                                                |
| Chain ID     | `84531`                                                                                 |
| RPC (public) | `https://virtual.rpc.tenderly.co/ecoround/ecoround/public/ecoround`                     |
| Explorer     | [Tenderly Dashboard](https://virtual.rpc.tenderly.co/ecoround/ecoround/public/ecoround) |

***

## Deployed Contracts

| Contract                 | Address                                      |
| ------------------------ | -------------------------------------------- |
| **FactoryMatch**         | `0x9ee150e66bca22083f6e5d279d4c5c00a9a7f582` |
| **USDC** (Base native)   | `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` |
| **Morpho ERC4626 Vault** | `0x050cE30b927Da55177A4914EC73480238BAD56f0` |
| **Keystone Forwarder**   | `0x5E342a8438B4f5d39e72875FCee6f76B39CCE548` |

> VaultMatch contracts are deployed dynamically per match by the FactoryMatch. Each match gets a unique vault address registered in the factory.

***

## Reading Vault Addresses

To find the vault address for a given match ID:

```solidity
address vault = FactoryMatch(FACTORY_ADDRESS).getVault(matchId);
```

Or via the API:

```
GET /api/v1/admin/matches/:id
→ { "vault_address": "0x..." }
```

***

## Tenderly Explorer

All transactions on the virtual fork are visible in the Tenderly dashboard. This includes:

* `createMatch()` calls from the admin panel
* `deposit()` and `claim()` calls from users
* `lockMatch()` and `resolveMatch()` calls from the CRE oracle

The Tenderly dashboard shows full transaction traces, state diffs, and event logs — making it easy to verify every protocol action.


---

# Agent Instructions: 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:

```
GET https://eco-round.gitbook.io/eco-round-docs/deployments/addresses.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.