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 — the board below uses Now / Next / Later horizons instead.

Most of Phase 3 is still conceptualization and early build-out — the board reflects what we're working on or planning toward, not a finished product map. Fast-moving sections — this page, the Agent API concept, and pricing — each have a micro-changelog at the bottom; check there to see what changed.

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

Local zero-crypto MCP PoC

Wrap one EthereumJS function as an MCP tool; prove the LLM round-trip.

In progress

Amsterdam EIP pipeline

First full pipeline on already-implemented Amsterdam EIPs.

In progress

Glamsterdam scope (BAL, pricing)

Planned

Hegota scope (FOCIL, frame txs, EL)

Planned

Website & Education

Explorations & education

In progress

API showcase links per exploration

Visual funnel from each exploration to its API capability.

Planned

Infrastructure

Stays on Strato (website)

In progress

AWS EC2 (c7g) for API

Compute-optimized Graviton + worker pool for isolated sims.

Planned

Scale & observability

Planned

Business & Community

x402 linear pricing (per-gas)

USDC on Base, from request #1, no free tier.

Planned

Tiered token discounts

Planned

Registry presence + outreach

Planned

Enterprise annual tier / buyback

Introduce "when they come".

Planned

The tracks

• Engine & API — the EthereumJS pipeline and the planned MCP server: local PoC first, then the Amsterdam EIP pipeline, then expanding fork coverage (Glamsterdam → Hegota: FOCIL, frame txs, EL EIPs per EIP-8081).
• Website & Education — explorations and the visual funnel that will eventually link each exploration to its API capability.
• Infrastructure — keeping the website on Strato while planning to move the headless API to AWS, plus the payments plumbing.
• Business & Community — pricing, token utility, distribution, and community alignment. (Granular as separate doc pages; grouped here for board readability.)

Phasing

Within Phase 3, the build sequence we're targeting roughly as: prove the local PoC → ship the Amsterdam pipeline (~Sep 1 target) → layer on x402 + token discounts → introduce an enterprise tier when demand appears. See the timeline for the dated view. Order and dates are targets under discussion, not commitments.

Changelog

Roadmap Changelog

1. v0.32026-06-30Reframed roadmap as conceptualization workspace — tracks describe planned work, not shipped product.
2. 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.
3. 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.