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

# Contract Address

BSC Mainnet contract addresses, approval targets and protocol dependencies.

Use these addresses on **BSC Mainnet (chain ID 56)**. The production API is `https://api.peach.ag`; address entries were checked on October 9, 2026.

### Protocol contracts

<table><thead><tr><th width="211.80078125">Contract</th><th>Address</th><th>Purpose</th></tr></thead><tbody><tr><td>PeachExecutionRouter</td><td><code>0x1F131D5A0f765890693A0E1480f69b2de2c1b568</code></td><td>Swap transaction destination and Direct ERC20 approval spender</td></tr><tr><td>PeachRouter</td><td><code>0xF2B877A2F415efB0Ad5f15d82652564528C1fd2a</code></td><td>Underlying routing contract; used by SDK router configuration reads</td></tr></tbody></table>

For Direct swaps, use `prepared.tx.to` as the transaction destination and `prepared.approvalSpender` as the approval spender. For Delegated swaps, the ERC20 base approval goes to Permit2; the Witness spender and final transaction destination are the Execution Router. Do not approve the underlying PeachRouter or an adapter for these SDK workflows.

### Protocol dependencies

| Contract | Address                                      | Purpose                                            |
| -------- | -------------------------------------------- | -------------------------------------------------- |
| Permit2  | `0x000000000022D473030F116dDEE9F6B43aC78BA3` | ERC20 base-approval target for delegated execution |
| WBNB     | `0xbb4CdB9CBd36B01bD1cBaEBF2De08d9173bc095c` | Wrapped BNB token; 18 decimals                     |

Native BNB uses the SDK placeholder `NATIVE_TOKEN_ADDRESS` (`0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE`). It is not a deployed contract or transaction destination. See [Native BNB](https://docs.peach.ag/documentation/bsc/aggregator/editor/direct-allowance/native-bnb).

### Provider adapters

These contracts execute protocol-specific swap steps. The SDK and service select them through the prepared route; applications do not approve or submit swaps directly to them.

<table><thead><tr><th width="218.84375">Provider</th><th>Adapter address</th></tr></thead><tbody><tr><td><code>PANCAKEV1</code></td><td><code>0x3c1183c10d4d355a137980F1d3b919154471B97D</code></td></tr><tr><td><code>PANCAKEV2</code></td><td><code>0x699B797ea93d49B3409b4940De7375840Feac256</code></td></tr><tr><td><code>PANCAKEV3</code></td><td><code>0x2896fF690132531fE4F16D23Bd35f47c2ea36d34</code></td></tr><tr><td><code>UNISWAPV2</code></td><td><code>0xaDeB10A75F33EB85599C694Fca57B7cc4ee25c9f</code></td></tr><tr><td><code>UNISWAPV3</code></td><td><code>0x1c5AaF294627E1C1B3a4E027E5d3b2435a1330D4</code></td></tr><tr><td><code>DODO</code></td><td><code>0xc80Bd9c80904C535C6596657Ce5bb00DC3762160</code></td></tr><tr><td><code>THENAV3</code></td><td><code>0xdFa368a4E6f1b2D70fBD89cF336dF532bd3A783B</code></td></tr><tr><td><code>NOMISWAP_STABLE</code></td><td><code>0xCD90fb6bF3673E8786318F08B51486Cd3eD9bb05</code></td></tr><tr><td><code>BISWAP</code></td><td><code>0x2d877d7a76AEA06976D1AE38C093Fea8e31061a9</code></td></tr><tr><td><code>PANCAKE_INFINITY_CL</code></td><td><code>0xb433Aa5f3E54c670006FaABc24e40e398e32d8cc</code></td></tr><tr><td><code>UNISWAPV4</code></td><td><code>0x30d87d5DF59f0609088567181B9DBAe66DF32cac</code></td></tr><tr><td><code>APESWAP</code></td><td><code>0x1fb0f4A6C0fF29ABE3DD0c747d613199B6A66eA1</code></td></tr><tr><td><code>BABYDOGESWAP</code></td><td><code>0xDf6C4C2eb6C123A9a1286FC58f3B00407A757cC8</code></td></tr><tr><td><code>BABYSWAP</code></td><td><code>0xD642b01c84F2Ed0aaCFF42eCa24Bfc91E59061c0</code></td></tr><tr><td><code>PANCAKE_STABLE</code></td><td><code>0x675E4E70EE3d5CE9ab6135072738fAFf1FC21De0</code></td></tr><tr><td><code>LISTA_STABLE</code></td><td><code>0x79D163823aE2d3EB1c72A9AeaD1F4fEc36f33327</code></td></tr><tr><td><code>THENA_FUSION</code></td><td><code>0xEA97C93059bef6b4a387b8C07c5d028536A0d5b7</code></td></tr><tr><td><code>SQUADSWAP_V2</code></td><td><code>0x9e51C950ecb4C7F9C6E12542b6Dbc95e5f0b87AC</code></td></tr><tr><td><code>SQUADSWAP_V3</code></td><td><code>0x600D9c389b7e8ECFAab2b13Be787771E800EE666</code></td></tr><tr><td><code>SUSHISWAP_V2</code></td><td><code>0x829795A0E234878Dbb9817ABAD33d1c6e756e2e7</code></td></tr><tr><td><code>SUSHISWAP_V3</code></td><td><code>0x68163f5ab2A849a1252c3847bf0305Bfa093981d</code></td></tr><tr><td><code>WOMBAT</code></td><td><code>0xcE940BF301fE134D9E42a259B1b64Ac4e24b078C</code></td></tr><tr><td><code>PANCAKE_INFINITY_LB</code></td><td><code>0x854504055B5912a8D5cFAc45a1CC41bd9f23bc99</code></td></tr><tr><td><code>BAKERYSWAP</code></td><td><code>0xcc541c732a1dE85f626c340e68E3D25B7E4aA633</code></td></tr></tbody></table>

A deployed adapter does not guarantee that its provider is currently enabled or has liquidity for an order. Use `getAvailableProviders()` and a fresh `swapAllowance()` or `swapPermit2()` result to check availability. Neither requires a prior `find_routes` call.

### Provider pool contracts

These shared protocol contracts are routing dependencies, not user approval targets.

<table><thead><tr><th width="209.796875">Provider</th><th>Pool contract address</th></tr></thead><tbody><tr><td><code>PANCAKE_INFINITY_CL</code></td><td><code>0xa0FfB9c1CE1Fe56963B0321B32E7A0302114058b</code></td></tr><tr><td><code>PANCAKE_INFINITY_LB</code></td><td><code>0xC697d2898e0D09264376196696c51D7aBbbAA4a9</code></td></tr><tr><td><code>UNISWAPV4</code></td><td><code>0x28e2Ea090877bF75740558f6BFB36A5ffeE9e9dF</code></td></tr></tbody></table>

### SDK configuration

The SDK receives execution addresses from the API. To restrict responses to these deployment addresses, set `config.executionRouterAddress` to PeachExecutionRouter and `config.routerAddress` to PeachRouter when creating the client. Address pins are optional; update them deliberately if the production deployment changes.

See [Client Configuration](https://docs.peach.ag/documentation/bsc/aggregator/editor/configuration-and-error-handling) for initialization and [Transaction Safety](https://docs.peach.ag/documentation/bsc/aggregator/editor/validation-approvals-and-expiry) for approval and validation rules.


---

# 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.peach.ag/documentation/bsc/aggregator/contract-address.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.
