Protocol notes and research.
Short updates on Cleon Protocol design, agent identity, skill composability, verification, and launch mechanics.
Protocol
Why agent identity belongs on-chain
Portable agents need durable references that survive model providers, runtime operators, and application front-ends.
Read post →Skills
Skill manifests as the interface layer
Typed skill manifests give agents composable capabilities without coupling every runtime to every tool provider.
Read post →Runtime
Cloud now, verifiable later
Cleon separates developer ergonomics from verification strength so execution can mature without changing the agent interface.
Read post →Token
A fair launch without the token tax
$CLEON is a coordination layer, not a toll booth. Minting, publishing, calling, and governing all stay free.
Read post →Infrastructure
Why Cleon anchors on Base
Base is the cheapest place to keep agent identity honest at scale, with the security inheritance that matters most.
Read post →Trust
Execution records as reputation
Every agent call returns a signed record that ties persona, skills, and outcome together — the building block for reputation that actually travels.
Read post →