Skip to content

Roadmap & Tracks ​

The roadmap runs along a few parallel execution streams. Each track moves at its own pace; together they turn the vision into something shippable. Concrete dates live on the timeline and the launch week page — the board below uses Now / Next / Later horizons instead.

Phase 3 is in build-to-launch: the MCP engine and catalogue exist; the public hosted endpoint is what we're shipping next. Payment rails follow once that endpoint has been used. Fast-moving sections — this page, the Agent API concept, and pricing — each have a micro-changelog at the bottom.

The board is data-driven — edit roadmap/data/roadmap.ts to add or reorder tracks (rows), horizons (columns), and items. Built to stay readable with 2–5 tracks.

Now
Next
Later
Engine & API
MCP tools implemented
describe_capabilities + run_bytecode + run_transaction; generic verbs, not per-EIP tools.
Done
Glamsterdam EIP catalogue
Canonical id is the combined name (glamsterdam); amsterdam remains the EthereumJS / EL alias. Round-trip pipeline filling runnable modules.
In progress
Public hosted MCP
HTTP at mcp.feelyourprotocol.org — launch week 5–9 Oct 2026.
In progress
EIP-7928 BAL generate
Generate shape for block-level access lists.
Planned
Hegota scope (EL EIPs)
Frame txs and other Hegota EL work start on the paid tier, then move to free as that hardfork approaches.
Planned
Website & Education
Explorations & education
~2 Amsterdam explorations per week; video pipeline for social.
In progress
MCP twin links per exploration
Each live exploration maps to mcp-docs/use/eips/.
In progress
Without vs with MCP proof
Documented agent comparisons — oracle vs LLM-only answers.
Planned
Infrastructure
Website on Strato
Done
AWS EC2 MCP host
Compute-optimized Graviton; nginx + TLS for public HTTP.
In progress
Scale & observability
Planned
Business & Community
x402 paid tier
Weeks after the open launch. USDC on Base for new EIPs; EIP-8141 first. See /monetization/pricing.
Planned
Agent-readable onboarding
Capability, price, and payment without a human who read the website. See /vision/two-audiences.
Planned
Tiered token discounts
Holder discount lane — never a gate for newcomers.
Planned
MCP registry listings
Machine-readable listings so agents can find the lab.
Planned
Enterprise annual tier / buyback
Introduce "when they come".
Planned

The tracks ​

  • Engine & API — the MCP server on EthereumJS: generic tools shipped, Glamsterdam catalogue filling, open public launch in launch week, then a paid cadence for new EIPs and Hegota scope.
  • Website & Education — explorations (~2/week), MCP twin links on mcp-docs, and documented without vs with MCP proofs for the oracle thesis.
  • Infrastructure — website on Strato; AWS EC2 for the headless MCP host. x402 plumbing lands with the paid tier.
  • Business & Community — access cycle and x402 pricing, token discounts, distribution, agent-readable onboarding and registry discovery. (Granular as separate doc pages; grouped here for board readability.)

Phasing ​

Within Phase 3, the sequence we're in: catalogue + pipeline done → open public MCP (launch week, full Glamsterdam) → harden and watch usage → x402 paid tier for new EIPs (EIP-8141 first) → those EIPs graduate to free when Hegota / Bogota is in view → registry + enterprise tier when demand appears. See the timeline. Order and dates are targets under discussion, not commitments.

Changelog ​

Roadmap Changelog
  1. v0.62026-10-01Open Glamsterdam launch in Now; x402 paid tier moved to Next (EIP-8141 first, then graduation).
  2. v0.52026-09-24Agent-readable onboarding and registry listings on the board.
  3. v0.42026-09-02Board refreshed — PoC done, launch week in Now column; Amsterdam vs Glamsterdam naming clarified in notes.
  4. v0.32026-06-30Reframed roadmap as conceptualization workspace — tracks describe planned work, not shipped product.
  5. v0.22026-06-30Reworked tracks to four execution streams (Engine & API, Website, Infrastructure, Business & Community) and Phase-3 build sequence, based on the strategy session.
  6. v0.12026-06-30Initial roadmap scaffold — placeholder tracks and Now/Next/Later horizons.

Add a one-line entry here every time the roadmap board changes.

A living conceptualization workspace — each section carries its own micro-changelog. Latest thinking always applies.