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 →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.
These are coverage lanes, not endorsements. Every future project card should show sources, last-reviewed date, network layer, custody model, and audit status.
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 →Wallets will be evaluated for transparent ownership, mainnet compatibility, signing UX, recovery guidance, update discipline, and KRON support.
Nodes, indexers, explorers, SDKs, covenant tooling, and APIs that help builders ship reliable native Kaspa experiences.
Projects that create real reasons to participate—games, payments, media, education, creator tools, and community infrastructure.
The final weights are still being designed, but the underlying questions are already clear.
What genuinely uses Kaspa, which layer does it run on, and what would stop working without the network?
Who controls keys and upgrades? Are source, audits, incidents, risks, and recovery paths disclosed plainly?
Is there a working product, recent development, measurable usage, responsive support, and an honest roadmap?
Does the project help people build, transact, learn, create, or coordinate without relying on price promises?
KOOK may create community features later, but token ownership should never silently purchase a higher research score.
Share the official website, repository, documentation, and the reason it belongs on the prep table. Nominations are leads—not automatic listings.