LIQUID VALIDATOR CLAIMS — CANTON NETWORK

Committed capital.
Still in motion.

Capital locked with a Canton validator returns a receipt.

The receipt moves. The underlying keeps working.

VALIDATOR nvCC RECEIPT

Capital that works once.

Commit capital to a validator today and it does one job.

It sits behind that validator's operations until you withdraw it. Nothing else can use it while you wait.

One contract. Two claims.

Nevos is a bilateral Daml contract between you and a validator operator.

You commit capital. The operator names you as a party to a defined share of what that capital earns.

INPUT
Capital committed to a named validator operator
CONTRACT
Bilateral Daml agreement, signed by both parties
OUTPUT
nvCC — a liquid receipt representing your claim
CLAIM
A defined share of the operator's Canton Coin rewards
RECEIPT USE
Collateral. A swap leg. The base asset for a structured product.

The receipt is not the capital. It is a claim on what the capital produces.

Every Daml contract has a signatory. Every one has a named owner. Nevos gives that ownership a second life as a tradable instrument.

Before and after.

COMMITTED, ILLIQUID
Liquidity
None until you exit the commitment.
Use elsewhere
Not possible.
Validator's work
Continues as normal.
Exit path
Wait for unbonding.
COMMITTED, LIQUID
Liquidity
Immediate, through the receipt.
Use elsewhere
Collateral, a swap leg, or a structured product base.
Validator's work
Continues, unaffected.
Exit path
Sell the receipt, or wait for unbonding.

What the receipt is actually worth.

Canton has no delegation mechanism today, and no protocol-level staking yield. There is no APY to quote you here.

What exists is validator revenue: Canton Coin earned for operating infrastructure, and for measurable application usage, under a burn-and-mint model that mints rewards from real activity rather than inflation alone.

Nevos lets an operator share a defined slice of that revenue with the capital behind them, in a contract you can read before you sign it.

That share is set bilaterally, operator by operator. It is not a network-wide rate. It moves with the operator's performance, and it can be zero.

[FORWARD-LOOKING] This structure has no long operating history on Canton mainnet. Read every claim on this page as a design, not a track record.

Why this only works here.

BILATERAL BY DEFAULT

Every Daml contract names its signatories. A revenue-share agreement is not a workaround here. It is the native shape of the ledger.

ORDERED, NOT READ

The Global Synchronizer sequences transactions without decrypting them. Your revenue-share terms stay between you and your operator.

SETTLED ATOMICALLY

Two-phase commit means the receipt and the underlying claim move together, or not at all.

REAL INSTITUTIONS ALREADY HERE

DTCC is tokenizing Treasuries on Canton. Broadridge runs repo on it. Nevos is built for validators operating in that environment, not a future one.

What can go wrong.

Operator risk

Your return depends on one validator's performance. Validators underperform. Some will fail outright.

No protocol guarantee

The revenue share is a private contract, not a network-wide yield. It can be renegotiated, reduced, or wound down on the terms the contract sets.

Receipt liquidity risk

The receipt trades on secondary markets Nevos does not control. It can trade below the value of the claim it represents.

Early mechanism

This structure has no long operating history on Canton. Treat it accordingly.

Contract risk

Daml templates can contain errors. Audits reduce this risk. They do not remove it.

No principal protection

Capital committed to a validator is not insured. It can be lost.

Start with the contract, not the promise.

Read the protocol spec Apply as a validator partner →