Layer-1 · v1.1 release candidate · Audit-ready
Kern is a Layer-1 blockchain combining EVM-compatible tooling with native on-chain governance — designed so the rules of an STO, a public goods fund, or an oracle network are visible at the source, not buried in a 200-page audit report.
Built in the open by Nicolas Van Eeckhout — follow along on LinkedIn for protocol milestones, audit results, and testnet launches. No list, no inbox.
If you remember nothing else about Kern, remember these.
Three-phase BFT consensus. One-second block time, two-second finality. No probabilistic reorganizations. Validators stake KRN; rewards adapt to participation.
Smart contracts are written in Skald, a small statically-typed language. Declared invariants are checked on every state transition. A lending market literally cannot enter an insolvent state.
Protocol amendments — consensus parameters, gas pricing, even Skald itself — go through an on-chain governance cycle. Dual-track: protocol upgrades and treasury allocations, with slashing for equivocation.
What's distinctive about Kern is not what it can do generically — it's what it makes legible at the protocol layer.
Signed claims about the world — KYC verifications, oracle prices, NAV figures, ESG data — with cryptoeconomic slashing on equivocation. Whistleblowers earn 10% of the bond. The accountability primitive at the L1.
Three audit-ready Skald templates: startup equity, institutional fund (AIFMD-compliant depositary independence), real estate (anti-Ponzi distribution invariants). The regulator reads the source.
Two grant-making primitives at the protocol layer. Quadratic funding rounds with on-chain matching math; retroactive funding with explicit scoring. Replace committee opacity with explicit formula.
Generic data + DeFi price oracles backed by the attestation primitive: feeders post slashable claims, circuit breakers trip on divergence. ZK-claims via BN254 for privacy-preserving attestations.
Other L1s compete on throughput. Kern competes on legibility — the dimension that decides whether a regulator, a foundation, or an institutional fund can use the protocol at all.
| Property | Ethereum L1 | Tezos | Solana | Kern |
|---|---|---|---|---|
| Finality | Probabilistic (~12 min) | Deterministic (~30 s) | Deterministic (~12 s) | Deterministic (~2 s) |
| Staking model | 32 ETH locked or LST | Liquid PoS, custody preserved | Delegated PoS | Liquid PoS, no LST |
| Contract language | Solidity (no native invariants) | Michelson + LIGO | Rust (Anchor framework) | Skald with runtime-enforced invariants |
| Governance | Off-chain, hard forks | On-chain, self-amending | Off-chain | On-chain, dual-track + slashable |
| Attestation primitive | — | — | — | Slashable, generic, schema-indexed |
| STO templates | Community ERC-1400 | — | — | MiFID II + AIFMD aligned |
| EVM compatibility | Native L1 | — | — | Via optimistic rollups |
The contract language is where institutional legibility is won or lost. Skald trades raw power for a property no mainstream contract language offers: invariants as a first-class construct the runtime enforces unconditionally.
| Dimension | Solidity | Move | Clarity | Skald |
|---|---|---|---|---|
| Invariants | Manual / external tools | Prover (compile-time, opt-in) | Asserts + decidability | First-class, runtime-enforced |
| Reentrancy | Famous footgun | Hard by design | Impossible by design | Impossible — atomic entry, no mid-call external calls |
| Surface area | Large (inheritance, dispatch) | Medium (modules, generics) | Small (no recursion) | Tiny — grammar fits one page |
| Turing-complete | Yes | Yes | No (decidable) | No (bounded) |
| Legibility for non-engineers | Low | Medium | Medium-high | High — the invariant block is the compliance statement |
| Ecosystem maturity | Largest by far | Growing | Small | Reference impl only — honest about this |
Skald borrows decidability and no-reentrancy from Clarity, the make-bugs-unrepresentable philosophy from Move, and the small-surface discipline from Vyper. Full comparison and honest limitations in the whitepaper.
From the reference implementation to Midgard mainnet. Network names follow Norse cosmology — devnet to Yggdrasil testnet to Midgard mainnet.
v1.1-rc shipped: 4 verticals, 692 tests, Heimdall explorer.
Foundation establishment. Multisig, treasury, validator registry.
Independent security audit — Trail of Bits / OtterSec / Hashlock tier.
Public testnet. Foundation-operated Heimdall. Feedback cycle.
Re-audit on post-testnet fixes. 70% public KRN allocation.
Genesis ceremony. Public RPC. Production explorer. Live.
Heimdall — the Norse god who watches the nine worlds from Bifröst and sounds the Gjallarhorn when something goes wrong — is Kern's official block explorer and monitoring stack. It surfaces what generic block explorers cannot: the live securities-compliance state of each STO, oracle health per feed, the active attestation registry, the slashing economy.
Ships with the v1.1-rc reference implementation. FastAPI + SQLite indexer + Jinja2 + Tailwind, 19 HTML pages, 12 JSON API endpoints, 7 Grafana dashboards, 10 Prometheus alerting rules.
Kern is a personal long-running project by Nicolas Van Eeckhout: founder of Cogarius, contributor to the Tezos ecosystem, and co-founder of the Meetup Blockchain-Ethereum group in Brussels. The protocol rests on two convictions.
First: that the EU's regulatory frameworks — MiCA, AIFMD, MiFID II, DORA — are not obstacles to L1 adoption, but specifications that a well-designed L1 should make trivial to satisfy. Second: that the right place to encode this is the contract language and the protocol primitives, not a downstream compliance overlay.
The validator set, the contributor program, the audit firms, and the public sale mechanism are all designed for European institutional adoption first, US-style retail second.
EU regulation is the spec sheet. Kern is the implementation.
⚠ Notice — pre-audit software
The Kern reference implementation is provided "as is," without warranty of any kind. The author accepts no liability for any deployment, financial loss, or regulatory consequence arising from its use. Discussion of EU regulation (MiCA, AIFMD, MiFID II, DORA) is informational and not a compliance assurance; no regulator has approved or endorsed this work. Independent professional security audits are planned before the Yggdrasil testnet and are a gating item for the Midgard mainnet. Read the full disclaimer.
Kern is built in the open, on evenings and weekends, by Nicolas Van Eeckhout. Follow the work on LinkedIn — protocol milestones, audit results, Foundation establishment, testnet launches.