Migrating to the BebopRouter contract

Bebop has introduced the BebopRouter 0xBeb0009ACa35087ce7cCF11637E24dd1Aad3bf2A contract, which now wraps BebopSettlement extending its functionality.

Do you need to migrate?

With Standard approvals, no changes are required if your integration already reads these fields from the quote response. Confirm both:

Approvals. You approve the approvalTarget from the quote response, not a hardcoded address. See Token approvals.
Broadcast. You send the returned tx object as-is; tx.to already targets the correct contract.

If you hardcoded the BebopSettlement address anywhere (for approvals or as the transaction target), switch to reading approvalTarget and tx from the quote response.

Reading the calldata

With Standard approvals, Bebop returns calldata ready to broadcast in tx.data. It calls the router’s swap function:

function swap(
    int256 exactAmount,
    BebopRouterOrder calldata order,
    bytes calldata extraInfo,
    bytes calldata routerSignature,
    bytes calldata bebopPmmCalldata,
    Hook[] calldata hooks
)

Parameter	Description
`exactAmount`	Fill mode. `> 0`: exactIn, you send exactly this amount of `fromToken`. `< 0`: exactOut, you want exactly `\|exactAmount\|` of `toToken` after fees. `== 0`: use whatever `fromToken` balance the router holds.
`order`	The signed order struct. `fromAmount` / `toAmount` define the quote ratio used for scaling.
`routerSignature`	The router signer’s EIP-712 signature over the order.
`bebopPmmCalldata`	The raw `BebopSettlement.swapSingle` / `swapAggregate` calldata the router wraps.

For a concrete reference, see this example transaction.

Permit2 self-execution

BebopRouter supports Permit2 self-execution for ERC-20 sell tokens.

Request a quote

Add gasless=false&approval_type=Permit2 to your quote request. Set taker_address to the user who owns the tokens, not your wrapper contract.

Approve Permit2

If needed, approve quote.approvalTarget on the sell token for at least quote.toSign.permitted.amount. For this flow, approvalTarget is the Permit2 contract.

Sign the permit

Have the taker sign quote.toSign as the EIP-712 message using the Permit2 witness types. Use the domain { name: "Permit2", chainId: quote.chainId, verifyingContract: quote.approvalTarget } without a version. Keep spender as returned: it is BebopRouter, not your wrapper.

Add the signature and submit

The returned tx.data calls settle with an empty userSignature. With an ethers v6 Interface for BebopRouter, replace that final argument:

const args = routerInterface
  .decodeFunctionData("settle", quote.tx.data)
  .toArray(true)

args[6] = userSignature
quote.tx.data = routerInterface.encodeFunctionData("settle", args)

Simulate the completed transaction before submission. Then broadcast the updated quote.tx, or call quote.tx.to from your wrapper with the updated calldata.

Introduction

Core Concepts

RFQ API

BopAMM

Aggregation API

Price API

Trade History API

Migrating to the BebopRouter contract

Do you need to migrate?

Reading the calldata

Permit2 self-execution

​Do you need to migrate?

​Reading the calldata

​Permit2 self-execution

Do you need to migrate?

Reading the calldata

Permit2 self-execution