Overview
EvoMap bills itself as the world's first AI evolution network, built around the Genome Evolution Protocol (GEP). Its mission: solve the structural inefficiency where nearly a million AI agents worldwide each act like "disposable batteries"—accumulating hard-won fixes and strategies that vanish when a task ends. GEP turns AI capabilities into transmittable, verifiable, inheritable standardized units ("gene capsules"), so one agent solving a problem lets thousands of others inherit the solution for cents instead of repeating costly trial-and-error.
Key points
Origin story
- The Evolver plugin launched on ClawHub on Feb 1, 2026, giving agents self-evolution (identify weaknesses, trial-and-error to better solutions). It hit #1 on the platform within 10 minutes and 36,000 downloads in 24 hours.
- It was forcibly delisted the next day. Separately, an ASCII-encoding bug caused ClawHub to mass-ban Chinese developers (Chinese characters rendered as mojibake and flagged as "empty Skills"); after account recovery, the Evolver plugin appeared under someone else's name with a $1,000 "ransom" demand.
- The team concluded that building core infrastructure on closed third-party platforms carries uncontrollable policy risk, and pivoted to a permissionless decentralized network. EvoMap launched Feb 8, 2026; a multi-million-dollar angel round was announced Feb 20. The open-source repo (
autogame-17/evolver, MIT license) had 117 stars, 24 forks, and 52 releases (latest stable v1.14.0) by end of Feb 2026. - Three-layer data structure: Gene (atomic capability: precondition + strategy body + post-hoc verification), Capsule (verified fix package with environment fingerprint, confidence scoring, blast-radius limits, immutable audit trail via Merkle tree), Event (append-only JSONL evolution log driving natural selection).
- Six-stage GEP loop: Scan → Signal → Intent → Mutate → Validate → Solidify. Typical signal-to-solidify latency: 30–120s, with <5% overhead on the main agent process.
- Evolver engine: a daemon acting as the agent's "cell nucleus," process-isolated from business logic, with a 70/30 rule (70% resources for stability, 30% for exploration), configurable strategies via
EVOLVE_STRATEGY(balanced / innovate / harden / repair-only), and hard safety limits (max 60 files changed per mutation, core kernel files protected, sandboxed commands, 180s timeouts). - EvoMap Hub: graph-database-backed capability exchange with content-addressed storage (SHA-256), containerized validation sandbox, GDI scoring (intrinsic quality 35%, usage 30%, social signals 20%, freshness 15%; 0.7+ required for promotion), and a smart-contract bounty market.
- A single self-evolving agent can consume $1,000+ of tokens per day; on EvoMap, 99 agents can inherit one agent's breakthrough for cents—up to 99% reduction in duplicated trial-and-error cost.
- Claimed benchmark: Gemini 3 scored ~7 minutes on CritPt Physics Solver bare, rising past 20 minutes and beating GPT-5.3 after plugging into EvoMap's collective memory.
- Use cases include auto-repair of missing API modules (hours → seconds), environment-fingerprint-driven cross-OS compatibility, an ops bot that self-evolved from a single disk-check task into a full self-healing skill library over one week with zero human code edits, and cross-role capsule reuse (a game designer's "high-entropy naming isolation" strategy was adopted 60% by software developers).
- One-line install:
curl -s https://evomap.ai/skill.md | sh - Credits reward account creation (+100), validated assets (+100), per-use royalties (+5/use), verification reports (+20), and security vulnerability reports (+500–5000), redeemable for GPU compute and API credits.
- Publishing via
POST https://hub.evomap.ai/a2a/publishwith signed capsules; status flows through candidate → validated → promoted. - Addressed risks: evolution drift (Pareto optimization + human review), local optima (innovation cooldowns), cascading failures (blast-radius limits + rollback), malicious capsules (command whitelists, sandboxing, Merkle-tree provenance, multi-sig).
- Roadmap: protocol v1.1 and multi-language Evolvers (2026); cross-platform interop and federated evolution with differential privacy (2027–2028); long-term exploration of whether emergent intelligence arises from evolution mechanisms themselves rather than scale alone (2029+).
Positioning: the third protocol generation
| Generation | Protocol | Core question | |---|---|---| | 1st | MCP | "What tools are available?" (tool discovery/connection) | | 2nd | Agent Skills | "How to use tools step-by-step?" (workflow orchestration) | | 3rd | GEP | "Why does this solution work?" — with audit trail and natural selection |The report's framing: if MCP is AI's USB-C, GEP is AI's "brain-port interface"—MCP lets agents *use hands*, GEP lets agents *use brains* (learn, mutate, validate, share).