Cordon

Confidential asset servicing for tokenized assets on Robinhood Chain.

$CRDN : 0x97203B7292DAb46C9BFbF12803693126C92f5040

[Cordon @TryCordonRH]

$CRDN Confidential asset servicing for tokenized assets on Robinhood Chain

CA : 0x97203B7292DAb46C9BFbF12803693126C92f5040

Sell the dividends.
Keep the stock.

CORDON splits tokenized assets into confidential claims.

$CRDN on @RobinhoodApp

[Cordon @TryCordonRH]

Tokenized assets can move onchain. Servicing them is the harder problem.

Cordon is building the confidential layer for income, collateral, atomic settlement, corporate actions and provable NAV on @RobinHoodApp

The technical architecture: https://t.co/VRIl0Mhf9n

[Cordon @TryCordonRH]

Cordon gives corporate actions a second check.

The watcher reads the pending multiplier, syncs, then verifies the completed step against Chainlink.

Mismatch Pause INCOME claims for that asset. PRINCIPAL stays unaffected.

Contain the mismatch. Do not freeze the position.

$CRDN 0x496e94fba7669884ae5db215e17246c2884df6a9

Live on @RobinhoodApp

[Cordon @TryCordonRH]

Tokenized assets can move onchain. Servicing them is the harder problem.

Cordon is building the confidential layer for income, collateral, atomic settlement, corporate actions and provable NAV on @RobinHoodApp

The technical architecture: https://t.co/VRIl0Mhf9n

[Cordon @TryCordonRH]

$CRDN Owning the asset and owning its income do not have to be the same thing.

Cordon is designed to let a holder assign income for a defined term while keeping the rest of the bundle intact.

[Cordon @TryCordonRH]

Composability is not “every asset gets every function.”

Cordon’s AssetGate defines which asset classes are claimable, which claim types apply and which encumbrance templates are allowed.

A USDG vault has no VOTE claim.

Useful systems make their boundaries explicit.

[Cordon @TryCordonRH]

16 leg DvP.

All legs settle, or none do.

The world sees the batch.
Not the trade.

[Cordon @TryCordonRH]

Cordon’s 15-minute deposit standby is a boundary, not a trap.

A deposit enters ScreeningGate before it becomes serviceable, allowing association set checks.

But unshield to origin remains available throughout.

Entry can be screened. Exit stays open.

[Cordon @TryCordonRH]

A fixed-term INCOME claim is not a permanent split.

Cordon’s term operation creates:

INCOME(∞) → INCOME(until T) + INCOME_REMAINDER(from T)

At expiry, the remainder resumes accrual at the next valid touch.

The income term ends by proof, not by manual reconciliation.

[Cordon @TryCordonRH]

Start with the distinction:

A PLEDGE or LIEN is not custody transfer.

The holder keeps the claim in Cordon’s ledger.
The counterparty holds an EncumbranceNote that binds the obligation, trigger and enforcement terms.

Collateral is restricted before it is enforced.

[Cordon @TryCordonRH]

Liquidation should not mean send collateral somewhere and hope the rest works.

Cordon’s v1 design treats it as a proven state transition followed by atomic delivery versus payment.

The trigger, waterfall and settlement must agree.

The path🧵👇:

[Cordon @TryCordonRH]

A private ledger can leak through transactions.

Cordon routes servicing actions through relayers, so an EOA is not the servicing identifier.
Mobile proving uses blinded witnesses.
The public API reports aggregates, not positions.

Privacy is the path around the proof, too.

$CRDN on @RobinhoodApp

[Cordon @TryCordonRH]

Cordon’s privacy model has a database rule:

no column may hold an owner, amount and claim-type tuple.

The indexer can track commitments, roots, batch totals and proofs.
It cannot reconstruct a user position.

Privacy starts with what a system refuses to store.

[Cordon @TryCordonRH]

Cordon does not ask a chain to trust a private balance.

It verifies a constrained transition:

valid note → ZK proof → correctly typed notes

The same model governs bundles, encumbrances, DvP and NAV.

Public: proof surface.
Confidential: position.

Built on @RobinhoodApp

[Cordon @TryCordonRH]

Gm to everyone on the green chain

[Robinhood Crypto @RobinhoodCrypto]

gm to everyone building something on Robinhood Chain

[Cordon @TryCordonRH]

What can governance change in Cordon?

Asset classes.
Applicable claim types.
Encumbrance templates.

What cannot be changed by governance?

The immutable pool’s note logic.

Cordon separates the policy surface from the ledger’s core conservation rules.

[Cordon @TryCordonRH]

@RobinhoodApp Tokenization compresses execution, clearing and settlement into software.

That creates speed. It also removes the room where manual reconciliation used to live.

As collateral and redemptions move to shared ledgers, servicing infrastructure becomes the market question.

[Cordon @TryCordonRH]

Cordonv1 Tokenization’s next phase is not more wrappers.

It is what happens after an asset arrives onchain: income, collateral, settlement, corporate actions and NAV.

Cordon is a v1 architecture for that servicing layer on
@RobinhoodApp
Chain.

Why now: 🧵👇

[Cordon @TryCordonRH]

REDEEM_ONLY is Cordon’s answer when an asset leaves the serviceable universe.

If an asset is delisted or removed from the registry, new servicing stops.

The holder can still unbundle and withdraw.

The system narrows to exit.
It does not strand the position.

[Cordon @TryCordonRH]

Cordon is confidential asset servicing for tokenized assets on @Robinhoodapp Chain.

We convert assets into shielded, disclosable claim bundles; manage income and encumbrances; settle up to 16 legs atomically; and attest NAV with zero-knowledge proofs, without exposing holdings.

[Cordon @TryCordonRH]

https://t.co/0NtbEhqTDl

[Cordon @TryCordonRH]

Not every asset should receive every claim type.

Cordon’s AssetGate is designed to define:
which asset classes are claimable;
which claim types apply;
which encumbrance templates are allowed.

A USDG vault, for example, has no VOTE claim.
Composability needs boundaries.