Project: Kerne Protocol
Status: Pre-TGE / no active public sale
Research focus: tokenomics, unlock risk, team verification, and smart-contract risk

1) What Kerne is building

Kerne Protocol is building kUSD, a synthetic dollar system on Base.

The basic model is:
• Users mint/redeem kUSD against USDC.
• kUSD can be staked into skUSD.
• The protocol aims to generate yield through a delta-neutral strategy combining ETH staking yield and perpetual funding.

The goal is to create a dollar-denominated asset that can earn onchain yield without requiring users to directly manage the underlying hedging strategy.

2) Tokenomics

KERNE has a fixed total supply of 1 billion tokens.

Published allocation:
• Team — 20%
• Investors — 15%
• Ecosystem — 25%
• Treasury — 15%
• Community / Opal — 5%
• Protocol-Owned Liquidity — 5%
• Public Sale / TGE — 5%
• Catalyst / Liquidity Reserve — 10%

The published vesting plan includes:
• Team: 1-year cliff + 4-year linear vesting
• Investors: 6-month cliff + 2-year linear vesting

However, there is an important distinction between the published schedule and what is currently enforced onchain.

At the time of this research, the full 1B KERNE supply remains controlled by a 2-of-3 governance Safe. The project states that dedicated vesting contracts have not yet been deployed and the allocations have not yet been separated into individual vesting wallets/contracts.

That means the published vesting schedule should currently be treated as policy intent rather than fully enforceable onchain vesting.

3) FDV, circulation, and dilution

KERNE is still pre-TGE, so there is no meaningful market price or circulating market cap yet.

Because there is no public trading price, an FDV cannot be responsibly calculated today.

Once a TGE price exists:

FDV = token price × 1B total supply

The main dilution risk is therefore not a current market-cap mismatch, but how much supply enters circulation at TGE and whether the published vesting schedule is implemented before major allocations become transferable.

I would want to verify:
• Exact initial circulating supply
• TGE allocation breakdown
• Whether team/investor vesting contracts are deployed before TGE
• Treasury and ecosystem spending controls

4) Security / technical risk

Kerne has published an external Hexens audit.

The audit reported:
• 0 Critical
• 2 High
• 2 Medium
• 4 Low
• 2 Informational findings

The project states that 8 findings were fixed and 2 were acknowledged.

One issue worth monitoring is that the live KerneVault bytecode was reported as being based on a version older than the audited commit.

The team has also stated that vault deposits are currently disabled and no user funds are exposed there.

For me, that lowers immediate user-fund risk but does not remove the need to verify that the final production contracts match the audited code before wider deployment.

5) Team verification

Kerne states that it has three co-founders.

One founder, Liam Lakevold, is publicly identified. The other two founders remain publicly anonymous.

The project also states that it currently has no institutional backers.

This is not automatically disqualifying, but it increases the importance of:
• multisig transparency
• auditable treasury movements
• public development history
• strong vesting enforcement
• independent security reviews

6) Main risks

My main concerns are:

1. Vesting enforcement
The published vesting schedule is not yet fully enforced through dedicated contracts.

2. Supply concentration
The full token supply currently sits under one governance Safe structure before allocation separation.

3. Smart-contract versioning
The production vault must ultimately match audited code before deposits reopen.

4. Team transparency
Two of three co-founders are not publicly identified.

5. Execution risk
The protocol depends on successfully operating delta-neutral strategies, managing hedges, and maintaining kUSD liquidity and redemption reliability.

Conclusion

Kerne has a relatively strong transparency surface for a pre-TGE project: public tokenomics, contract information, GitHub activity, and an external audit.

The main question is not whether the allocation table looks reasonable on paper.

The key question is whether the project converts those published commitments into enforceable onchain controls before TGE.

For me, the most important checkpoints are:
• vesting contracts deployed
• allocation wallets separated
• final audited contracts matched to production
• initial circulating supply disclosed
• treasury controls clarified

Until those are confirmed, I would treat the tokenomics as promising but not yet fully enforced.

Disclosure: No position in KERNE. This research was prepared for educational due diligence and is not financial advice.

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