Capital already backing Canton's core can secure more of it. Same collateral. Two obligations. Two revenue streams.
Every validator and application provider on Canton already commits capital and infrastructure to back their role. Most of that commitment does one job.
Orbix lets it do more. The same operator, already named on a contract with the Global Synchronizer, signs a second contract: to secure an oracle feed, a bridge, or an app-specific validator set Canton itself does not cover.
Two contracts. Two obligations. Two reward streams, paid in Canton Coin, from two different sources.
Break either obligation, and both contracts can call it a breach.
The existing commitment. Not restaked — the foundation the rest is built on.
Price and data feeds an application depends on. Rewarded in CC by that application.
Dedicated validation for one application, beyond what the Global Synchronizer provides.
Capital backs one role. It earns one reward stream. It carries one set of obligations.
The same capital backs two roles. It earns two reward streams. It carries both sets of obligations, combined.
Three ways to earn, already. Canton Coin rewards split between Super Validators, Validators, and Application Providers, based on measured activity, not passive holding. Orbix is built for operators already in one of those seats.
No restaking primitive exists yet. Canton has nothing like this natively. We're building the layer that lets one operator's existing commitment count twice, using the same bilateral Daml contracts already running the network.
Privacy that protects the strategy. Sub-transaction privacy means what an operator has committed, and to whom, is not visible to competitors watching the same synchronizer.
Source: Canton Network, 2026. This is the capital base Orbix is built to extend — not a claim about Orbix's own activity.
The same capital backs multiple obligations. A fault in one secured service can trigger penalties that hit your standing in the other.
A small set of operators securing many services makes the whole system depend on a few actors performing well.
Restaking has no long track record on Canton. Ours does not either, yet.
Each secured service sets its own penalty conditions. Stack enough of them and the combination is hard to model in advance.
This can cost you the capital you committed. Read both contracts before you sign either.