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

# Contract Addresses

Maple publishes every deployed contract address in its public address registry. The registry is the source of truth, so this page links to it rather than copying addresses that can go stale.

| Chain            | List of addresses                                                                              |
| ---------------- | ---------------------------------------------------------------------------------------------- |
| Ethereum Mainnet | [list](https://github.com/maple-labs/address-registry/blob/main/MapleAddressRegistryETH.md)    |
| Base L2          | [list](https://github.com/maple-labs/address-registry/blob/main/MapleAddressRegistryBASEL2.md) |

{% hint style="info" %}
The addresses of the deployed November 2026 release contracts are in the address registry.
{% endhint %}

## Contracts in the November 2026 release

| Contract                                                                                                                     | Change                                   |
| ---------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------- |
| `MapleGlobals` implementation (v5.0.0)                                                                                       | Upgrade of the Globals singleton         |
| `MaplePoolDeployer` (v5.0.0)                                                                                                 | New deployer                             |
| `MaplePoolManager` implementation, initializer and `MaplePoolManagerMigratorV500` (v5.0.0)                                   | Upgrade for existing Pool Managers       |
| `MapleWithdrawalManager` queue implementation and initializer (v2.0.1)                                                       | Upgrade for existing Withdrawal Managers |
| `MapleStrategyManager` factory, implementation and initializer (v1.0.0)                                                      | New                                      |
| `MapleStrategyDeployer` (v1.0.0)                                                                                             | New                                      |
| `MapleLiquidityRouter` (v1.0.0)                                                                                              | New                                      |
| `MapleAaveV3Strategy`, `MapleSkyStrategy` and `MapleAllocationStrategy` factories, implementations and initializers (v1.0.0) | New                                      |
| One Strategy Manager and Underlying Strategy instance per shared strategy                                                    | New                                      |

## Developer reference

Solidity source for the on-chain registries, with addresses embedded as constants:

* Ethereum: <https://github.com/maple-labs/address-registry/blob/main/contracts/MapleAddressRegistryETH.sol>
* Base L2: <https://github.com/maple-labs/address-registry/blob/main/contracts/MapleAddressRegistryBASEL2.sol>


---

# 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.maple.finance/technical-resources/protocol-overview/smart-contract-addresses.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.
