Asset Integration
Access syrupUSDC & syrupUSDT across multiple blockchains using CCIP. Find contract addresses, oracles, and bridge contracts for Solana, Arbitrum, Base, Plasma etc.
syrupUSDC & syrupUSDT use Chainlink Crosschain Interoperability Protocol (CCIP) to facilitate bridging and holding 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.
Both tokens have 6 decimals across all chains.
Mainnet Addresses
syrupUSDC
CCIP Router
Receiver (Mint/Redeem)
CCIP Router
Receiver (Mint/Redeem)
syrupUSDT
CCIP Router
Token Admin (Timelock)
CCIP Router
[To be added]
Token Admin (Timelock)
CCIP Router
[To be added]
Testnet 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
syrupUSDC
CCIP Router
Receiver (Mint/Redeem)
CCIP Router
Receiver (Mint/Redeem)
Find out more and acquire test tokens by visiting the CCIP Test Tokens page.
Pricing
Onchain Oracles
SyrupUSDC/USDC
Chainlink Price Oracle
Chainlink Price Oracle
Chainlink Price Oracle
SyrupUSDT/USDT
Chainlink Price Oracle
Chainlink Price Oracle
Chainlink Price Oracle
Use Chainlink's Data Feeds docs to consume them.
Data Streams
Low latency streams work on supported chains - full list of available chains here.
Stream Feed ID
0x000721629eb23678e5c52595523785ae4e0ef470ca8a1cb7e894edcfa03dcfe9
Stream feed ID
0x0003e2c8ee282f518aee9efd1e14a5fd51da7a0e3207041f5db1785d0729cd1d
Use Chainlink's Data Streams docs to consume them:
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.
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 CCIP 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
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].
Resources & Contact
Partnerships & queries: [email protected]
Last updated
Was this helpful?