Kern protocol · who it's for

Six institutions, six concrete problems Kern solves.

The abstract thesis — "institutional legibility" — becomes concrete when you watch it applied. Each use case below is drawn from the whitepaper, with an animated diagram of the mechanism that makes it work.

all loop automatically · respect reduced-motion
Persona A STO · sto-startup-equity.skald

A Belgian fintech tokenizing private equity

A Brussels B2B fintech (~50 staff) raising a €15M Series B wants to tokenize ~20% of its equity (€3M) so employees and early backers can trade secondary — without an IPO.

Without Kern

Custom Solidity contract for Prospectus Reg. Art. 3 / MiFID II Art. 16(9) / MAR Art. 14. Audit alone €80-150k. FSMA approval unpredictable — no template the regulator has seen before. ~12 months, €150-300k.

With Kern

Deploy the canonical template. Securities-regime articles are Skald invariants the regulator reads directly. Approval compresses to ~3 months. ~€25-40k total.

The regulator reads the invariants — each securities-regime article enforced at runtime
Prospectus Reg. Art. 3
Prospectus registered
MiFID II Art. 16(9)
Custody segregated
MAR Art. 14
Market-abuse controls
● COMPLIANT — verifiable live, no annual report needed
The FSMA opens the explorer and sees the compliance state directly, instead of waiting for an audit report.

Unique to Kern: no other production L1 has runtime-enforced invariants + a regulator-readable contract language + an accumulating library of templates a regulator grows familiar with.

Persona B STO · sto-institutional-fund.skald

An EU institutional fund tokenizing private debt

A Luxembourg AIF (€200M AUM) tokenizing access to a private-debt portfolio. The fund manager (AIFM) is regulated; the depositary is an independent bank — AIFMD requires their separation.

Without Kern

NAV published quarterly via reports, depositary co-signs on paper. Redemptions only in the quarterly window. Heavy operational cycle: calc → depositary validation → distribution doc → regulator notice.

With Kern

NAV posted as a slashable attestation; the depositary co-signs as a second attestation. AIFMD's independence requirement becomes an on-chain invariant: depositary ≠ AIFM.

NAV requires two independent signatures — enforced, not promised
AIFM
posts NAV
+
Depositary (independent)
co-signs NAV

Unique to Kern: the combination of regulator-readable AIFMD invariants, slashable attestations for the depositary co-sign, and on-chain best-execution tracking is not assembled anywhere else.

Persona C STO · sto-real-estate.skald

A French SCPI (real-estate investment vehicle)

A Paris real-estate fund, €80M across 12 properties, 3 000+ retail holders. Secondary trading is a paper-based broker process at quarterly intervals — bad liquidity, slow notary title transfers.

Without Kern

Exit before the quarterly window means a big haircut. Acquisitions slow (notary title transfers take weeks). Tax distributions reconciled manually per investor jurisdiction.

With Kern

Notary-attestation anchors tangible title on-chain. An anti-Ponzi invariant guarantees rental income distributed can never exceed rental income received.

Anti-Ponzi invariant: distributed ≤ received, enforced every block
Rental income received
received
Rental income distributed
distributed
A distribution that would exceed received income is REVERTED ✗ — the contract cannot become a Ponzi.

Unique to Kern: the notary-attestation trust anchor + anti-Ponzi invariant + lock-up and secondary-market staleness gates, pre-assembled as a deployable template for European real-estate tokenization.

Persona D Public goods · quadratic-funding.skald + retroactive-pgf.skald

UNESCO regional office running heritage grants

A UNESCO regional office, €10M/yr for digital heritage preservation. The committee process is slow (6+ months), opaque, and admin overhead is ~15% — heavy for €10-50k grants.

Without Kern

Expert committee decides allocations behind closed doors. No community signal on what matters most. Sybil-prone if opened to public voting. ~15% admin cost.

With Kern

Quarterly Quadratic Funding rounds. Many small community contributions are amplified by a matching pool — breadth beats depth. Sybil resistance from slashable personhood attestations. ~2% admin.

Quadratic funding: many small contributions → amplified match
12 small contributors
─►
matched
quadratically
large match — funding follows the number of backers, not just the sum

Unique to Kern: Gitcoin shows QF works but suffers Sybil attacks; Optimism shows RPGF works but is closed-ecosystem. Kern provides both as native primitives with cryptoeconomic Sybil resistance via slashable personhood attestations.

Persona E Oracle · schema "energy.grid-frequency-hz"

An EU TSO for inter-grid energy settlement

A national grid operator (Elia, RTE, TenneT…) in the EU Central Western Europe market coupling. Settlement needs consensus on grid frequency and clearing prices every 15 minutes across 7 states.

Without Kern

Reconciliation between TSOs takes weeks. Disputes from measurement timing and methodology differences. ~€30-100M/yr per TSO on reconciliation and back-office.

With Kern

Each TSO posts grid-frequency attestations with a bond (~10 000 KRN). Consensus is the aggregate. Equivocation — same TSO, different frequency, same window — is slashable.

TSOs post attestations; a divergent one is detected and slashed
TSO · BE50.01 Hz
TSO · FR50.00 Hz
TSO · NL50.01 Hz
TSO · X (equivocates)49.7 Hz
⚔ equivocation slashed — bond burned, prover rewarded
● consensus = 50.00–50.01 Hz · ENTSO-E runs the schema marketplace

Unique to Kern: no oracle network (Chainlink, Pyth…) is designed for regulated industrial data networks. The slashable attestation + schema marketplace fit ENTSO-E's institutional structure precisely. Directly aligned with the founder's professional context.

Persona F Oracle · schema "telco.roaming-minutes"

An EU telco settling roaming & wholesale traffic

A tier-1 European telco (Deutsche Telekom, Vodafone, Telefónica…) settling roaming with hundreds of counterparts — hundreds of millions of euros per year. GSMA's BCE framework, reconciled monthly/quarterly.

Without Kern

Bilateral reconciliation monthly/quarterly. Disputes resolve over weeks via mutual auditor engagement. Heavy back-office.

With Kern

Operators post subscriber-count and roaming-minute attestations with bonds. Equivocation between settlement windows is slashable. Reconciliation moves from monthly batch to continuous.

Two operators post matching attestations — the cryptographic proof replaces the dispute
Operator A1.2M min
Operator B1.2M min
B (window n+1)0.9M min
⚔ contradiction across windows → slashable evidence
● matched attestations settle continuously · GSMA runs the schema marketplace

Unique to Kern: same argument as energy — no oracle network targets regulated industrial data exchange. The institutional fit + slashing primitive + EU regulatory context together are what Kern provides and competitors do not.

Sourced from docs/whitepaper.md §3 (Use cases envisioned) and docs/use-cases.md.
Personas are illustrative composites of real institutional patterns in the EU regulatory map.