Create Cross-Chain Tokens with CCT Standard
summary
The CCT standard extends ERC20 so a custom token can move across chains via Chainlink CCIP using per-chain token pools that implement either burn/mint or lock/unlock semantics (lock requires prefilled pools). A web UI, the Chainlink Token Manager, deploys pools in a few clicks; the pool contracts are open source for customization (rebasing support requires manual work). Chainlink Local simulates CCIP locally (Foundry/Hardhat/Remix compatible), drops test iteration time to sub‑second, runs offline, and lets the same contracts redeploy to testnet/mainnet without code changes. Bounties and Anvil integration are covered.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 0:37Speaker Introductions & Contacts
- 0:55Key Resources & Hackathon Links
- 1:24Oracles and Chainlink Overview
- 3:03Hackathon Bounties & Sponsor Overview
- 3:31Blockchain Interoperability & CCIP
- 4:52CCT Standard: Cross-Chain Token Creation
- 6:20Token Pools: Burn/Mint vs Lock/Unlock
- 8:14Customization & Advanced Use Cases
- 9:28Documentation & Guides
- 9:49Chainlink Local: Local Simulation Tool
- 11:18Developer Experience & Benefits
- 12:02Bounties Recap & Developer Hub
- 13:03Final Resources & Slides
- 13:32Q&A: Use Cases & Project Integration
- 15:19Q&A: Chainlink Local vs Anvil
- 16:37Final Q&A & Closing Remarks
related talks
21mCreate Cross Chain Tokens with CCT Standard
16mExploring the Cross-Chain Interoperability Protocol (CCIP)
29mCCIP: Connecting The Dots Between Blockchain and The Real World
30mFireside Chat
16mBuild CRE workflows using Chainlink Privacy Capabilities
01h 40mKeynote on the Future of Hybrid Smart Contracts
41mBuild Cross-Chain NFTs
01h 50mBuild Cross-Chain dApps Using CCIP