Cancore
Trust-minimized atomic settlement between Canton and public chains.
Cancore connects Canton and public-chain liquidity through cross-domain settlement. Its documentation also covers wallet-approved agent requests, SDK trading and separate bot accounts with their own keys and balances.
Background
Cancore addresses one of the biggest strategic questions for Canton: how private institutional workflows connect to public-chain liquidity without relying on fragile bridge assumptions. Public chains have liquidity and users. Canton has privacy and settlement discipline. The market needs a safer path between them.
The project focuses on atomic settlement rather than custody. That distinction matters. Cancore is not trying to become a trusted middleman; it is trying to let value move across domains with fewer added trust assumptions.
Key Benefits
- Separate bot accounts and balances
- Funding and fee controls
- Activity inspection and order controls
- Wallet-approved requests or SDK workflows
Why Canton
Canton is built for workflows where privacy, permissioning, and settlement certainty matter. But even the best private network benefits from credible access to broader liquidity. Cancore extends Canton's reach without asking institutions to abandon the properties that made them choose Canton in the first place.
That makes the Canton fit very clear: Cancore is a liquidity bridge for a privacy-first financial network, but with a trust-minimized design philosophy rather than the usual bridge shortcut.
What Makes It Unique
Cancore's uniqueness is the focus on atomicity and minimal trust. Many interoperability products ask users to trust validators, relayers, custodians, wrapped assets, or opaque infrastructure. Cancore's messaging is built around reducing those dependencies.
If it succeeds, it can become a practical settlement path between institution-friendly Canton activity and the open liquidity of public chains.
What's Included
Routing and settlement
Cancore provides infrastructure connecting Canton workflows with supported public-chain routes. Confirm the asset, source network and destination before using a route.
Agent and application integration
Published tooling includes an SDK and bot-account workflows for application and agent integrations. Feature availability and onboarding can differ across routes and account types.
Developer access
Use the current documentation for installation, authentication, signing requirements and supported operations. An SDK integration does not eliminate bridge, contract or operational risks.
Official Resources
Behind the Scenes
Cancore appears to be building in public with a community-heavy rollout. Early access, whitelist activity, bug reports, and audit milestones all point to a project testing both technology and distribution at the same time.
Impact
Interoperability can make Canton more useful. If Cancore provides a reliable path to public-chain liquidity, Canton-native assets and workflows become easier to fund, exit, route, and integrate with the wider crypto economy.
Active Campaigns & Incentives
My bots is being opened in stages. If the section is absent from Wallet settings, it is not yet available for that account.
Looking Ahead
Follow the documentation for current SDK installation instructions and feature availability.
From the Insights Hub
CantonNews Project Spotlight: Cancore
Cancore is a settlement layer built on Canton Network, meaning it’s responsible for finalising transactions between Canton and public blockchains like Ethereum.
$350B Settles Daily on Canton. None of It Reaches Public Chains. Yet.
Right now, two financial systems are running in parallel. They don't talk to each other... Institutional finance is tokenizing at scale. Public chains have deep, permissionless liquidity. But
The Final Piece for Institutional Web3: Canton Network
"Web3 will reinvent finance." That was the pitch sold to us for years. And for years, institutions basically watched from the sidelines. Not because they weren't interested. The infrastructure just