EVM contract

Four contracts share the EVM side. BlinkEscrow receives every deposit and pays refunds; its funds leave through a release to the solver, a refund that any executor can send to any address for any amount, or an owner withdraw. BlinkSolver holds the operator float and is the contract that pays fulfillments and gas drops; its executors pull deposits out of the escrow with pullFromEscrow, which takes any amount, forwards the referrer share it is given to the fee manager, and does not check that the deposits have settled (the operator and the signer cluster enforce that off chain), and any executor can send any amount of float to any address with payToken. BlinkFeeManager holds referrer fees and pays vouchers out of its own balance only, so the voucher key can never reach the solver float. The executor allowlist includes the router and BlinkBridger (the rebalancing contract, which lets any caller on its own allowlist send any amount of solver float into an allowlisted bridge or swap contract with calldata that caller chooses, including the recipient) as well as the operator wallets. BlinkRouter carries every entry point that swaps or takes a signature (aggregator deposits, permit and permit2 variants, gasless witness deposits, same-chain swaps, partner funding) and forwards the resulting funds into the escrow. The router is UUPS-upgradeable by the owner; the escrow, solver, and fee manager are not upgradeable.

Chain	Escrow	Solver	Router
`arbitrum`	0x612938549C1fb0F6eD69c5Ef15BAC60afB9372b8	0x60331ba0c6Aed38041aFf15e4ccF034fC7c10FD9	0xBEDa5CE14e0FBf3078e66E2d2CF712cb077523e2

Solana is covered separately in SVM program. Prefer the router_address from the quote over these constants. A plain cross-chain deposit binds to the escrow, a swap deposit is sent to the router returned by GetSwapInstructions, and a same-chain swap binds to the router.

Escrow deposit entry points

function depositNative(bytes32 quoteHash) external payable;

function depositToken(bytes32 quoteHash, address token, uint256 amount) external;

Both emit Deposit and leave the funds in the escrow.

Router deposit entry points

function depositTokenWithPermit(
    bytes32 quoteHash,
    address token,
    uint256 amount,
    uint256 permitValue,
    uint256 deadline,
    uint8 v,
    bytes32 r,
    bytes32 s
) external;

function depositTokenWithPermit2(
    bytes32 quoteHash,
    address token,
    uint256 amount,
    uint256 nonce,
    uint256 deadline,
    bytes calldata signature
) external;

function depositWithSwap(
    bytes32 quoteHash,
    address srcToken,
    uint256 amountIn,
    address aggregator,
    bytes calldata swapData,
    address lockToken,
    uint256 minLockAmount
) external payable;

depositWithSwapAndPermit and depositWithSwapAndPermit2 take the same arguments plus the respective signature parameters. Permit variants take the signed permit’s value as permitValue and pass it to the token unchanged, so it must equal the value the user signed; sign for the amount the call pulls, not for an unlimited allowance. They attempt the permit and ignore its failure, so an already-consumed permit does not revert the deposit. Token pulls credit what was actually received, so fee-on-transfer amounts are accounted at the escrow, not assumed. Two witness variants back gasless orders: depositTokenWithPermit2Witness and depositWithSwapAndPermit2Witness take an owner plus a permit2 SignatureTransfer witness signature binding the quote hash (and, for swaps, the bridge token and floor), so an operator wallet can submit the deposit on the signer’s behalf. Only callers on the router’s witness caller allowlist can call them; the owner manages it with setWitnessCaller(address caller, bool allowed), which emits WitnessCallerSet, and any other caller reverts with Unauthorized(). The allowlist holds the operator’s gasless relayer wallets and any integrator relayer wallet we have allowlisted. Their optional permitSignature is an EIP-2612 permit approving permit2 for the maximum uint256 value, signed with the same deadline as the permit2 signature; the router rebuilds the permit from those two values, so a permit signed for anything else is ignored and the deposit then needs a standing permit2 allowance.

Same-chain swap

function swapAndForward(
    bytes32 quoteHash,
    address srcToken,
    uint256 amountIn,
    address aggregator,
    bytes calldata swapData,
    address dstToken,
    uint256 minAmountOut,
    uint256 amountOut,
    uint16 referrerBps,
    address recipient
) external payable;

Swaps and pays the recipient in one transaction, on the router. Delivery is floored at minAmountOut and capped at amountOut; the referrer share is forwarded to the fee manager and any surplus to the solver. swapAndForwardWithPermit adds permitValue, deadline, v, r, s and swapAndForwardWithPermit2 adds nonce, deadline, signature. See Same-chain swaps.

Partner funding

function fundPartner(bytes32 partnerId, address token, uint256 amount) external payable;

Forwards an allowlisted funding token to the solver and emits PartnerFunding tagged with the partner id, the partner’s account id left-padded to 32 bytes as returned by BuildPartnerFunding. The indexer credits the partner’s balance from the event once the transaction is final. See PartnerApi funding.

Voucher redemption

function redeemVoucher(
    bytes32 id,
    address token,
    address referrer,
    uint256 amount,
    bytes calldata signature
) external;

On the fee manager, callable by anyone while the solver is not paused. The EIP-712 signature (domain name BlinkFeeManager, version 1, the fee manager as verifying contract) is verified against the current voucher-signer set, the id is marked used so it cannot be redeemed twice, and the amount is paid to referrer from the fee manager’s balance. Releases and same-chain swaps fill that balance with the referrer share; the solver float is never touched. A voucher’s router_address is the fee manager it redeems against. See Referral program.

Operator functions

Restricted to the owner, registered executors, or BlinkBridger callers, listed for completeness.

Function	Contract	Caller
`fulfillToken`, `payToken`	Solver	Executors. Pay out fulfillments and gas drops; `payToken` sends any amount of float to any address.
`refund`	Escrow	Executors. Sends any amount of the escrow’s balance to any address.
`pullFromEscrow`	Solver	Executors. Moves any amount from the escrow into the solver and forwards `voucherAmount` of it to the fee manager; the contract does not check that the deposits have settled.
`release`	Escrow	The solver contract only, from `pullFromEscrow`.
`fulfillWithSwap`	Router	Executors. Fulfillments that swap into the destination token.
`bridgeOut`	Bridger	Addresses on the bridger’s own caller list. Pulls any amount from the solver and calls an allowlisted target with calldata the caller chooses.
`setCaller`, `setTarget`, `withdraw`, `transferOwnership`	Bridger	The bridger’s own owner. Ownership moves in one step.
`setExecutor`, `setPauser`, `setEscrow`, `setFeeManager`	Solver	Owner. `setEscrow` is one-shot; `setFeeManager` can point the solver at a new fee manager.
`setVoucherSigner`, `revokeVoucherSigners`	Fee manager	Owner.
`setAggregator`, `setFundingToken`	Router	Owner. Allowlist management.
`withdraw`	Escrow, solver, fee manager, router	Owner. Moves any amount to any address.
`pause`, `unpause`	Solver	The pauser pauses, the owner unpauses. While paused, every path that moves funds and is not owner-only reverts: deposits, same-chain swaps, partner funding, fulfillments, payouts, refunds, releases, bridger sends, and voucher redemptions. The escrow, fee manager, router, and bridger read the solver’s pause state. Owner withdrawals keep working.
`transferOwnership`, `acceptOwnership`	Solver	Owner, two-step. The escrow, fee manager, and router read the solver’s owner.

Events

Event	Emitted by
`Deposit(bytes32 quoteHash, address token, uint256 amount, address from)`	Escrow: `depositToken`, `depositNative`, and router deposits forwarding in
`Refunded(bytes32 quoteHash, address token, address recipient, uint256 amount)`	Escrow: `refund`
`Released(address token, uint256 amount)`	Escrow: `release`
`DepositWithSwap(bytes32 quoteHash, address from, address srcToken, uint256 amountIn)`	Router swap deposits
`SameChainSwap(...)`	Router: `swapAndForward`
`Fulfilled(...)`	Solver `fulfillToken`, router `fulfillWithSwap`
`PartnerFunding(bytes32 partnerId, address token, uint256 amount, address from)`	Router: `fundPartner`
`VoucherRedeemed(bytes32 id, address token, address referrer, uint256 amount)`	Fee manager: `redeemVoucher`
`AggregatorSet`, `FundingTokenSet`	Router allowlist changes
`ExecutorSet`, `PauserSet`, `EscrowSet`, `FeeManagerSet`	Solver configuration changes
`VoucherSignerSet`, `VoucherSignersRevoked`	Fee manager voucher-signer changes
`Paused`, `Unpaused`, `OwnershipTransferStarted`, `OwnershipTransferred`	Ownership and pause

The indexer matches Deposit and SameChainSwap against stored quotes by quoteHash.

Reverts

Error	Cause
`InsufficientOutput`	A swap or fulfillment delivered less than the committed minimum.
`AggregatorNotAllowed`	The aggregator is not allowlisted. Refetch swap instructions.
`SwapFailed`	The aggregator call failed, usually stale calldata.
`InvalidMsgValue`	Transaction value does not match the call.
`InvalidReferrerBps`	`referrerBps` above the contract cap.
`FundingTokenNotAllowed`	`fundPartner` with a token outside the allowlist.
`GasDropNotAllowed`	Gas drop requested where it is not permitted.
`EnforcedPause`	The contract is paused.
`VoucherShareExceedsRelease`	A `pullFromEscrow` asked to forward more to the fee manager than it releases.
`VoucherUsed`	Voucher id already redeemed.
`InvalidVoucherSignature`	Signature does not match a registered signer.
`Unauthorized`, `NotOwner`	Caller is not an executor or the owner.
`TransferFailed`, `ApproveFailed`, `NativeForwardFailed`	Underlying token or native transfer failed.

Reference

Blockchain

EVM contract

Escrow deposit entry points

Router deposit entry points

Same-chain swap

Partner funding

Voucher redemption

Operator functions

Events

Reverts

​Escrow deposit entry points

​Router deposit entry points

​Same-chain swap

​Partner funding

​Voucher redemption

​Operator functions

​Events

​Reverts

Escrow deposit entry points

Router deposit entry points

Same-chain swap

Partner funding

Voucher redemption

Operator functions

Events

Reverts