Project Research Dossier: Kerne Protocol

1. What Kerne Is Building

Kerne is building a synthetic dollar protocol on Base.

Its core product, kUSD, can be minted 1:1 from USDC and staked as skUSD.

The protocol combines Ethereum staking yield with short ETH perpetual positions designed to reduce directional exposure.

Kerne also emphasizes verifiability through public contracts, reserve data, source code and security information.

Primary source: https://kerne.fi/whitepaper

2. Tokenomics

KERNE has a fixed maximum supply of 1 billion tokens.

Planned allocation:

• Team: 20% • Investors: 15% • Ecosystem: 25% • Treasury: 15% • Community: 5% • Protocol liquidity: 5% • Public sale / TGE: 5% • Catalyst reserve: 10%

KERNE is still pre-TGE with no public circulating supply or market-derived FDV.

Importantly, the full 1B supply is currently held by the governance Safe. The published allocations and vesting schedules are policy commitments and are not yet enforced through deployed vesting contracts.

Primary source: https://kerne.fi/whitepaper

3. Unlock and Dilution Risk

The planned schedule gives the team a 1-year cliff followed by 4-year linear vesting, while investors have a 6-month cliff followed by 2-year linear vesting.

Community tokens are planned to unlock 50% at TGE and 50% over six months. Ecosystem rewards are intended to use a 365-day esKERNE vest.

These schedules could limit early dilution, but they are not yet enforced on-chain.

For me, the key pre-TGE milestone is whether these vesting and allocation controls are actually deployed before token distribution begins.

4. Team and Verification Signals

Kerne provides public contracts, GitHub repositories and an external Hexens audit.

Hexens reported 10 findings across five contracts:

• 0 Critical • 2 High • 2 Medium • 4 Low • 2 Informational

Eight were fixed and two acknowledged.

One limitation is that Kerne states the deployed KerneVault uses earlier bytecode than the commit reviewed by Hexens. Therefore, the audit should not be treated as proof that every live component is identical to the audited version.

Primary sources: https://github.com/kerne-protocol https://kerne.fi/security/audits

5. Key Risks

The main risks include smart contract vulnerabilities, negative funding or hedge failures, oracle risk, USDC dependency and execution risk.

Governance concentration is also important because the governance Safe currently controls the entire KERNE supply while the planned vesting restrictions remain unenforced.

Kerne also states that no company has been incorporated, creating an additional legal and counterparty consideration.

Primary sources: https://kerne.fi/security https://kerne.fi/institutional

6. Conclusion

Kerne shows why pre-TGE research needs to look beyond allocation percentages.

The project already has a live product, public code and external security review. However, its future token structure is not yet enforced on-chain.

The most important question before TGE is therefore simple:

Do the promised tokenomics become enforceable before KERNE becomes transferable?

That matters more than the allocation percentages alone.

Disclosure

I currently hold no KERNE position and received no compensation or token allocation for this research.

This research is for educational purposes and is not financial advice.