syrupUSD Crosschain
syrupUSDC & syrupUSDT use Chainlink Crosschain Interoperability Protocol (CCIP) to facilitate minting, holding & redeeming on chains other than Ethereum mainnet. CCIP handles secure crosschain token movement and message delivery, so you don’t need to build a custom bridge.
Integration paths
1) Offchain integrators (bridge, wallets & aggregator UIs)
If you run a bridge, wallet, or aggregator UI, use the token and router addresses per chain (below) to configure your routes and call patterns. Typically, you won’t deploy onchain contracts - your UI directs users to call the CCIP Router with the correct params.
2) Onchain integrators (protocols)
If your protocol needs to bake in crosschain syrupUSDC transfers, implement CCIP send/receive flows in your smart contracts and interact with the Router on the source chain, please contact us at [email protected].
syrupUSDC Mainnet: networks & addresses
Token Address
AvZZF1YaZDziPY2RCK4oJrRVrbN3mTD9NL24hPeaZeUj
Router Address
Ccip842gzYHhvdDkSyi2YVCoAWPbYJoApMFzSxQroE9C
Pool Address
HrTBpF3LqSxXnjnYdR4htnBLyMHNZ6eNaDZGPundvHbm
syrupUSDC Testnet: networks & addresses
CCIP provides two ERC-20 test tokens, so you don’t depend on third-party liquidity while testing:
CCIP-BnM (Burn & Mint): deployed on each testnet; transfers are burn → mint
CCIP-LnM (Lock & Mint): minted only on Ethereum Sepolia
Token Address
95Er6pcK2agiTa2Jctp1BBnQtuDfX1d78XSTZKWZyXKk
Router Address
Ccip842gzYHhvdDkSyi2YVCoAWPbYJoApMFzSxQroE9C
Find out more and acquire test tokens by visiting the CCIP Test Tokens page.
syrupUSDT Mainnet: networks & addresses
Token Address
0xC4374775489CB9C56003BF2C9b12495fC64F0771
Router Address
0xcDca5D374e46A6DDDab50bD2D9acB8c796eC35C3
Pool Address
0x1d952d2f6eE86Ef4940Fa648aA7477c8fF175F09
High-level flow
User picks source & destination chains in your UI or protocol flow
Approve syrupUSDC / syrupUSDT to the CCIP Router on the source chain (standard ERC-20 approval; Solana uses SPL program approvals)
Initiate CCIP transfer via the Router with destination chain selector, recipient, and amount
CCIP finalizes on destination chain and releases/mints syrupUSDC / syrupUSDT to the recipient
Implementation notes
Always call the Router listed for the source chain; don’t hit low-level endpoints directly
Chain selectors & fees: Pull chain selectors and fee token options from the CCIP directory; keep them in config
Solana (SVM) specifics: Use the SVM Router program (
ccip_send
) and follow the SVM API docs for building send/receive flowsObservability: Track the CCIP message ID from the Router response and correlate with destination events
If you require market data streams or feeds, please see Data Streams & Oracles
Resources & Contact
Partnerships & queries: [email protected]
Last updated