Overview
The Gateway contract is deployed on every supported chain. It serves as the entry point for all intents and the trust anchor for the protocol.The Gateway is intentionally non-upgradeable to maintain long-term trust and predictability. Once deployed, the contract logic cannot be changed.
Responsibilities
| Function | Description |
|---|---|
| Intent Validation | Validates chain, asset, expiry, and minimum output parameters |
| Event Emission | Emits canonical OrderCreated events that solvers monitor |
| Fee Application | Applies token-specific fees to each transaction |
| Token Whitelisting | Only allows approved tokens to be bridged |
| Finality Tracking | Marks orders as executed to prevent replay |
| Replay Protection | Ensures each order ID can only be executed once |
Contract Interface
bridgeToken
Create a new bridge intent:bridgeNative
Bridge native token (ETH, BNB, etc.):executeOrder
Execute an intent (solver only):Events
OrderCreated
Emitted when a new intent is submitted:OrderExecuted
Emitted when a solver fulfills an intent:Token-Specific Fees
Fees are configured independently per token:| Token | Default Fee |
|---|---|
| USDC | 0.25% |
| USDT | 0.25% |
| ETH | 0.50% |
| Other | Configurable |
Partner integrations can include additional builder fees. Contact the team for custom fee arrangements.
Security Features
Role-Based Access
Only authorized addresses can execute specific functions
Non-Upgradeable
Contract logic is immutable after deployment
Token Whitelist
Only pre-approved tokens can be bridged
Replay Protection
Each order ID can only be executed once
Design Philosophy
The Gateway is intentionally minimal:- No routing logic — Keeps the contract simple and auditable
- No upgradability — Trust is established at deployment
- No external calls — Reduces attack surface
- Deterministic behavior — Same inputs always produce same outputs
Next: Learn about Routers — how swaps are integrated.

