syrupUSDC Crosschain

syrupUSDC uses 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].

Mainnet Supported networks & addresses

Type
Address

Token Address

AvZZF1YaZDziPY2RCK4oJrRVrbN3mTD9NL24hPeaZeUj

Router Address

Ccip842gzYHhvdDkSyi2YVCoAWPbYJoApMFzSxQroE9C

Pool Address

HrTBpF3LqSxXnjnYdR4htnBLyMHNZ6eNaDZGPundvHbm

Testnet Supported 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

Type
Address

Token Address

95Er6pcK2agiTa2Jctp1BBnQtuDfX1d78XSTZKWZyXKk

Router Address

Ccip842gzYHhvdDkSyi2YVCoAWPbYJoApMFzSxQroE9C

Find out more and acquire test tokens by visiting the CCIP Test Tokens page.

High-level flow

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

  2. Approve syrupUSDC 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 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 flows

  • Observability: Track the CCIP message ID from the Router response and correlate with destination events

Market data

If your integration needs market data for pricing or risk checks, you can access it below.

Data Streams (low latency)

Streams work on all supported chains above - full list of available chains here.

Stream feed ID: 0x000721629eb23678e5c52595523785ae4e0ef470ca8a1cb7e894edcfa03dcfe9

Use Chainlink's Data Streams docs to consume them:

Data Feeds (onchain oracles)

SyrupUSDC/USDC data feed addresses exist on Base & Arbitrum.

0x311D3A3faA1d5939c681E33C2CDAc041FF388EB2

Use Chainlink's Data Feeds docs to consume them.

Resources & Contact

PreviousBackend IntegrationsNextIntroduction

Last updated