Chefs List 2.0

THE KASPA L1 PREP TABLE

The old leaderboard is off the menu while the criteria are rebuilt. The new Chefs List will favor verifiable native-Kaspa work over noise, paid placement, or popularity theater.

Research mode is active. No numeric rankings are being published until sources, review dates, scoring rules, and correction paths are visible to everyone.
What is cooking

THE BOARD, BEFORE THE SCORES

These are coverage lanes, not endorsements. Every future project card should show sources, last-reviewed date, network layer, custody model, and audit status.

L1Research complete

KRON

Native Kaspa L1 bonding-curve launchpad and AMM DEX using Toccata covenants. Live on mainnet, externally unaudited at the time of KOOK’s review.

Trade KOOK on KRON →
WQueue forming

Kaspa wallets

Wallets will be evaluated for transparent ownership, mainnet compatibility, signing UX, recovery guidance, update discipline, and KRON support.

DResearch planned

Developer infrastructure

Nodes, indexers, explorers, SDKs, covenant tooling, and APIs that help builders ship reliable native Kaspa experiences.

CCommunity input

Culture and utility

Projects that create real reasons to participate—games, payments, media, education, creator tools, and community infrastructure.

The scoring mise en place

WHAT EARNS A PLACE IN THE KITCHEN

The final weights are still being designed, but the underlying questions are already clear.

01

Native fit

What genuinely uses Kaspa, which layer does it run on, and what would stop working without the network?

02

Security posture

Who controls keys and upgrades? Are source, audits, incidents, risks, and recovery paths disclosed plainly?

03

Product reality

Is there a working product, recent development, measurable usage, responsive support, and an honest roadmap?

04

Community value

Does the project help people build, transact, learn, create, or coordinate without relying on price promises?

Kitchen rules

NO PAY-TO-RANK SHORTCUTS

KOOK may create community features later, but token ownership should never silently purchase a higher research score.

  • Every factual project claim gets a dated source.
  • Protocol facts stay separate from marketing claims and opinions.
  • Security and audit gaps appear beside the benefits, not in fine print.
  • Projects receive a correction path when a fact is wrong or stale.
  • Sponsored placement, if ever used, is labeled and never changes scoring.
Bring a dish

KNOW A KASPA PROJECT WORTH REVIEWING?

Share the official website, repository, documentation, and the reason it belongs on the prep table. Nominations are leads—not automatic listings.