Skip to content

Problem & Vision ​

Ethereum changes faster than people can learn it, and faster than an AI can safely guess it.

Protocol updates — EIPs, hard forks, research — are hard to follow, hard to explain, and hard to build against. Feel Your Protocol started as a hands-on way through that: read the change, run it, see what it does.

Agents now take on the same work. Auditing a contract, searching for MEV, testing an upgrade before it lands. They hit a wall:

LLMs are probabilistic. The Ethereum protocol is strictly deterministic.

A model guesses

Gas, a cascade of state, a deep stack trace. The answer sounds sure and can still be wrong.

The protocol does not

The same inputs have one result. An oracle is the call that returns it.

The oracle ​

Feel Your Protocol is that oracle for the future protocol — the rules that are not on mainnet yet.

A hosted MCP server wraps the modular EthereumJS stack. An agent sends bytecode, a transaction, or a small block, and gets an exact simulation under an upcoming fork.

Deterministic truth for probabilistic machines.

Textbook and server ​

One engine underneath both. Two legs, one engine.

People and agents ​

People

Researchers, educators, integrators, and the token community.

Agents

They can arrive alone, with nobody who has already allowlisted the tool.

Two audiences.

What opens ​

The public server is live.

Open

Free. No API key, no payment.

Glamsterdam

The full upcoming hardfork, open since 6 October 2026.

Later

A paid tier for EIPs still ahead of that fork.

Schemas and limits live on mcp-docs. The paid cycle is on Pricing.

Why us ​

The work is already here

Years of EIP prototypes, and of maintaining infrastructure inside Ethereum. A model cannot invent that context.

A stack you can take apart

EthereumJS is TypeScript libraries, not one node. Forks switch, state arrives per call, and every step can be traced. Cryptography sits on Noble. A monolithic Rust node is a poor fit.

A name people trust

An education-first brand and an open-source record make it easier to allowlist the server.

Checked, not claimed

The same question, on the same model, once without the server and once with it. The difference is published.

The shape of it ​

You bring

Accounts, code, and transactions. A fresh lab world each call.

You receive

Gas, logs, and a step-by-step trace.

Outside

Chain RPC, an archive of mainnet history, an indexer, long replays of past blocks.

Where to go next ​

Changelog ​

Problem & Vision Changelog
  1. v0.92026-10-06The public server is open. The launch card points at what landed.
  2. v0.82026-10-05Icon groups for the wall, the two legs, the two audiences, the moat, and the lab boundary.
  3. v0.72026-10-05Shorter public page. Dropped the Phase 3 frame from this essay.
  4. v0.62026-10-01Next ship is the open Glamsterdam MCP. Paid x402 tier follows for EIPs ahead of that hardfork.
  5. v0.52026-09-24Humans and agents as equal customers; payment, onboarding, and discovery follow from that.
  6. v0.42026-09-02Lab equipment built — public hosted launch is the next milestone; mcp-docs and generic MCP tools acknowledged.
  7. v0.32026-07-15MCP docs site live — strategic sketch stays here; concrete docs on mcp-docs.
  8. v0.22026-06-30Reframed as conceptualization workspace — conditional language for unshipped API.
  9. v0.12026-06-30Initial problem & vision outline.

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