Live on Canton Network · Institutional pilot
CIP-105 requires Super Validators to lock lifetime CC rewards to preserve governance weight — which leaves that capital idle. Helix verifies the locked position, records its provenance and compliance state, and issues pCC: a financing claim against it. It is designed so the lock stays intact and the collateral need not leave its custody posture. pCC is a claim on locked Canton capital, not a transferable, DEX-listed token.
What is live today
These are operating facts about the current pilot that a first diligence call can check in minutes. No audited metrics or partner endorsements are stated, because none are earned yet.
Compliance and SV-locking observation dashboard at vault.helixlabs.org, running against Canton mainnet data. A pilot-stage proof surface — not full production.
Canton Network is Helix's live beachhead — the network where the pCC primitive runs today.
pCC — a financing claim issued against verified locked CC. Recorded and reconcilable on-chain, not a DEX-listed transferable token.
Compliance-aware LTV, on-chain provenance, lock-tier and vesting tracking, and unlock monitoring — built into the vault design.
Institutional pilot. Engagement runs through diligence and scoped pilot access, not open self-serve signup.
The problem
Under the Super Validator Locking and Long-Term Commitment Framework, a validator that wants to keep its governance weight must commit a portion of lifetime earned CC across a tier of thresholds. That capital cannot be financed, collateralized, or routed while it secures the validator's standing — and selling or moving it to free the capital forfeits the weight. The economic value is stranded behind the obligation, with no compliant path to put it to work.
Lifetime Super Validator rewards on Canton.
Governance weight preserved.
No compliant way to finance the locked position.
A share of lifetime earned CC rewards must stay locked to maintain the validator's compliance tier and governance weight. The larger the position, the more capital sits idle.
Falling below a tier threshold opens a 50-minute restore window and, if unrestored, a 30-day cure period — the lock has to be monitored, not just established.
Unlocking to use the capital forfeits governance weight and disturbs vesting and tier state. The economic value of the lock has no native financing path.
The mechanism
pCC is the liquidity layer over a verified locked CC position. Each step is recorded and reconcilable, so the compliance state of the underlying lock remains observable and reconcilable across the financing lifecycle.
Confirm the locked CC against Canton state — amount, lock status, and CIP-105 tier.
Record provenance and compliance state as package-aware, on-chain contract evidence.
Mint a financing claim against the verified position under compliance-aware LTV.
Use pCC as collateral in financing and structured liquidity — the locked CC stays in place.
Burn pCC and reconcile against the recorded position to clear a clean unlock path.
Burn → reconcile → unlock. The claim clears and the locked CC returns to its original compliant state — so liquidity is created without permanently breaking the lock.
pCC is a claim against locked collateral — not a free-transfer, DEX-listed token.
Read the full mechanism in the docsInstitutional controls
Helix is built so a position can be examined, not just trusted. Each control below is concrete, tied to observable state, and inspectable during a pilot — the reasons a custodian, prime broker, or staking desk can keep its existing control posture while a locked position is financed.
Financing is designed so locked CC need not leave the approved custody and control model. Helix accounts for and issues pCC against the in-place verified position rather than taking discretionary custody of the lock or transferring the underlying collateral.
Receipts, vault state, and package-aware contract evidence give every pCC claim a verifiable lineage back to the specific locked position it references — auditable from issuance to reconciliation, not asserted.
Issuance respects CIP-105 tier thresholds, lock status, and the 1/365.25 daily vesting on excess lock. Limits and unwind logic are designed around the compliance window and sized to avoid forcing a breach — design intent, not a guarantee.
The live dashboard surfaces lock state, implied versus on-chain weight, reward context, and risk flags, so positions are monitored continuously rather than assumed at settlement only.
Who it's for
If you operate, custody, finance, or steward locked CC, the verify → account → issue pCC → finance → reconcile pattern maps to a specific need on your desk. Each segment meets the pilot with a different question and finds its own use of the same primitive.
Preserve governance weight under CIP-105 while financing the locked CC that backs it — without breaking the lock or disturbing tier and vesting state.
Offer compliance-aware financing against locked positions that stay inside an approved control model, with on-chain provenance for every claim.
Put idle locked rewards to work through a primitive whose collateral, LTV, and unlock path are observable and reconcilable end to end.
Support a public compliance and locking observation surface that helps CIP-105 enforcement work in practice, not just on paper.
Evaluate a scoped pilot with a live proof surface, real provenance, and a clear risk boundary before any broader commitment.
Live proof surface
The live observation dashboard renders real CIP-105 lock state for SV positions on Canton. It is pilot-stage and not a fully public production application, but it runs against live Canton mainnet data — the proof that the locking model is understood and instrumented.
Per-SV cards: lock percentage, achieved tier, breached thresholds, implied versus on-chain weight, and tranche vesting — the verified locked position with the pCC claim against it. Shown above.
Monitoring of lock thresholds, reward context, vesting, and risk flags across positions under management — the financing side of the same verified lock.
Roadmap — direction, not availability
Live today is Canton and pCC. Everything to the right of it is roadmap — the pattern of verify, account, finance, and reconcile is designed to generalize, stated here as direction only.
Helix is not live on any chain other than Canton, and nothing below implies an existing integration or partnership.
Verified locked CC, provenance, compliance-aware pCC issuance, and the observation dashboard. The shipped, observable wedge — live today.
Designed to extend pCC-style financing toward settlement paths as scoped integrations. Roadmap targets, not live.
The same compliance-aware financing pattern applied to native locked and staked capital across additional proof-of-stake ecosystems, where the need exists. Direction of coverage, not availability.
Diligence & resources
Start with the CIP-105 thesis and the live surface, then go deep in the docs or talk to the team. Helix is at institutional-pilot stage — there is no self-serve signup, and initial access is granted through a scoped pilot conversation.
How Helix turns locked CIP-105 capital into a financeable position — the full lock-to-unlock reasoning behind pCC.
vault.helixlabs.org — the pilot-stage compliance and SV-locking observation surface, running against Canton mainnet data.
docs.helixlabs.org — protocol, contract model, and integration documentation.
How the same financing pattern is framed for native locked capital beyond Canton.
Talk to Helix
Helix is in institutional pilot on Canton. The fastest way to evaluate it is to request pilot access and a walkthrough of the live surface against a real position — for Super Validators, custodians, prime brokers, staking desks, foundations, and allocators.