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.

Mainnet Addresses

syrupUSDC

syrupUSDT

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

Find out more and acquire test tokens by visiting the CCIP Test Tokens pagearrow-up-right.

Pricing

Onchain Oracles

SyrupUSDC/USDC

SyrupUSDT/USDT

Use Chainlink's Data Feeds docsarrow-up-right to consume them.

Data Streams

Low latency streams work on supported chains - full list of available chains herearrow-up-right.

Type
Address

Stream Feed ID

0x000721629eb23678e5c52595523785ae4e0ef470ca8a1cb7e894edcfa03dcfe9

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

  1. User picks source & destination chains in your UI or protocol flow

  2. Approve syrupUSDC / syrupUSDT to the CCIP Router on the source chain (standard ERC-20 approval; Solana uses SPL program approvals)

  3. Initiate CCIP transfer via the Router with destination chain selector, recipient, and amount

  4. 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 directoryarrow-up-right; keep them in config

  • Solana (SVM) specifics: Use the SVM Router program (ccip_send) and follow the SVM API docsarrow-up-right for building send/receive flows

  • Observability: 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]envelope.

Resources & Contact

Last updated

Was this helpful?