Router contract
The router contract 0xBeb0009ACa35087ce7cCF11637E24dd1Aad3bf2A wraps the settlement contract to add on-chain toxic-flow protection and maker hooks. Learn more on the product page.
Settlement contract
The contract 0xbbbbbBB520d69a9775E85b458C58c648259FAD5F is live on:
| Chain | Chain ID |
|---|
| Arbitrum | 42161 |
| Avalanche | 43114 |
| BNB Chain | 56 |
| Base | 8453 |
| Ethereum | 1 |
| HyperEVM | 999 |
| Optimism | 10 |
| Polygon | 137 |
Missing a chain? Bebop will deploy on any chain a market maker wants to provide liquidity on.
Supported tokens
If you want to provide liquidity on a token, Bebop can add it. Stream it on the Pricing WebSocket and Bebop will review and onboard it to the supported list.
For the tokens currently supported, see RFQ API Quickstart › Get Tokens for a Chain.
Cross-maker swaps
Bebop supports swaps between tokens from different makers. An AAA -> BBB swap in that case happens in two hops: AAA -> USDC and USDC -> BBB. Example transaction.
Approvals
Bebop transfers assets using allowances from users and market makers. As a result, approve the settlement contract for the size of levels you stream and the quotes you provide.
Quote requests are not sent to makers with insufficient approvals.
