Tokenized securities · Use cases
Composable securities. No bridge to hack.
A tokenized security shouldn't have to route through the most-attacked component in crypto. Ours verifies its own backing at the source — no bridge, no pooled honeypot — and composes into baskets and structured products without the shared-contract risk that usually comes with them.
Why bearer wins
Compose value without pooling risk.
DeFi's bargain is to put everything in shared contracts. That's what gives you composability — and it's exactly why bridges are the biggest hacks in crypto: pool value and trust in one place and you get both at once. A bearer security is a self-contained object. You keep the composability and lose the blast radius.
No pooled honeypot
Value and trust don't sit in one shared contract, so there's nothing to drain. Bridge risk simply isn't in the model.
Verifies at the source
A token proves its own backing directly against the issuer's contract — no bridge holding locked value, no validator set to compromise.
Composes inside the object
Baskets, tranches and structured products live in one verifiable token — not a web of shared contracts each carrying its own cascade risk.
No central registry
The cap table is the set of outstanding tokens, reconstructible from the tokens themselves. There's no authoritative database to trust or breach.
The architecture
Settlement, with the separation of duties intact.
In TradFi, three institutions keep securities settlement safe — and DeFi collapsed all three into one contract, which is exactly why bridge and synthetic-asset failures are catastrophic rather than contained. Unicity keeps the three duties separate, but makes the reconciliation cryptographic instead of organisational.
Settlement
TradFi
DTCC guarantees no double-ownership.
Unicity
The uniqueness oracle — no double-spend, no shared ledger.
Transfer agent
TradFi
Transfer agents confirm ownership.
Unicity
Possession of the bearer token — ownership proven by holding the self-certifying asset.
Custodian
TradFi
Custodians handle KYC, eligibility and credit.
Unicity
The predicate — KYC, eligibility and transfer restrictions enforced at the point of transfer.
DTCC-grade failure containment with sub-second settlement at near-zero marginal cost — TradFi's security architecture without the T+1 reconciliation tax, and without the single point of failure that makes DeFi settlement uninsurable.
Use case 01· custody & risk
Nothing pooled. Nothing to drain.
Cross-chain bridges are the biggest hacks in crypto because they pool everyone's locked value and all the trust logic into a single contract — one honeypot to attack. A bearer security carries no such thing: it verifies its backing directly against the source, with no bridge contract holding pooled value and no validator set to compromise. For a tokenized bond or fund moving between issuance, trading and custody, that's the difference between a loss and a fiduciary catastrophe. And because the cap table is just the set of outstanding tokens — reconstructible from the tokens themselves — there's no central registry to breach either.
For — asset managers, custodians, issuers
Bridges & shared state
Value and trust pooled in one contract — the single most-attacked component in crypto. Billions lost, repeatedly.
With Unicity
The token verifies its own backing at the source. No pooled value, no bridge, no validator set — nothing to drain.
Use case 02· structured products
One token, many securities.
Because a bearer security is self-contained, you can compose inside the object: one token that represents a basket of bonds, a structured product with tranches, or a fund share that itself holds underlying securities. In DeFi you'd assemble that by wiring together shared contracts — and inherit every one of their cascade risks. Here the composition lives in a single, independently-verifiable object. Coupons, dividends and splits are distributed by the issuer re-minting with the entitlement attached — the same checkpoint that anchors compliance.
For — structured products, funds, index & basket issuers
Composability today
Wire shared contracts together — each one a dependency, each one a cascade path when something upstream breaks.
With Unicity
Composition inside one verifiable object. A basket or a tranche is a token — not a web of contracts to audit and defend.
Use case 03· private & restricted securities
Eligibility enforced by the asset.
A restricted share, a Reg D placement or a private-fund interest can only legally move to eligible holders — accredited, whitelisted, in the right jurisdiction, past a lockup. Today a transfer agent, registry or issuer allowlist enforces that after the fact. In a bearer security the eligibility rule is a predicate in the token: a transfer to an ineligible party can't be constructed, and every holder in the token's history can be verified eligible.
For — private placements, restricted & Reg D securities
Transfer agent / allowlist
Eligibility is checked after the fact by an intermediary — and can be bypassed, lagged, or mis-set.
With Unicity
The rule lives in the token. An ineligible transfer can't be formed — prevention, not correction.
Use case 04· settlement & market infrastructure
Atomic DvP, no depository.
Delivery-versus-payment is the core operation in securities settlement, and today it needs a central securities depository and a settlement window — T+1, with the whole industry straining toward T+0. A predicate swap settles both legs or neither, atomically, with no shared ledger and no depository in the middle. Settlement stops being a window and becomes an event.
For — exchanges, settlement venues, tokenization platforms
CSD & the T+1 window
A central depository nets and settles inside a settlement window — counterparty and settlement risk carried in between.
With Unicity
Both legs or neither, instantly. No depository, no window, no settlement risk to carry.
Use case 05· institutional privacy
Private positions, disclosed on demand.
Institutions don't want their positions, trades and sizes public — a real objection to tokenizing on transparent chains. A bearer security is confidential by default: the network sees nothing. When a regulator needs beneficial ownership or a large-holder threshold, the token's provenance discloses the chain of accountable, credentialed holders on demand — without a public ledger exposing everything to everyone.
For — institutional holders, funds, regulated issuers
Transparent chains
Positions exposed to competitors and counterparties; add privacy tech to fix it and throughput collapses.
With Unicity
Private by default, disclosed to the regulator on demand. Confidentiality and oversight at once — not one traded for the other.
Five use cases. One object.
They all come from one move: a security that's a self-contained bearer object, not an entry in a shared contract. The mechanics — the uniqueness oracle, predicates, atomic swaps — are proven in three formal papers and running code.