A Semantic Execution + Receipt Layer For ERC-8004–Discoverable Services
ERC-8004 discovers services.
x402 moves value.
CommandLayer defines what execution means — and proves it.
Every execution produces a deterministic, hashable, verifiable receipt. CommandLayer is the missing execution + proof layer in the ERC-8004 stack.
The Stack
Discovery
ERC-8004
Payment
x402
Execution Semantics
CommandLayer
Receipts
CommandLayer
ERC-8004 defines who exists.
x402 defines how value moves.
CommandLayer defines what execution means and how completion is proven.This positions CommandLayer as protocol plumbing — not an application layer.
Discovery Is Not Execution
ERC-8004 makes services discoverable. It does not standardize what happens after discovery. CommandLayer fills that gap.
ERC-8004 does not standardize
- Request semantics
- Output structure
- Deterministic completion proof
- Canonical receipt format
- Executor identity anchoring
CommandLayer provides
- Typed verbs
- JSON Schema–validated requests
- Canonical hashing
- Signature verification
- ENS-anchored executor identity
- Deterministic receipts
Receipt Structure
Every verb execution returns a receipt. Below is a minimal analyze receipt
from the CommandLayer runtime.
// analyze.receipt
{
"x402": {
"verb": "analyze",
"version": "1.0.0",
"entry": "x402://runtime.commandlayer.eth/analyze/v1"
},
"trace": {
"trace_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"started_at": "2026-02-17T12:00:00Z",
"completed_at": "2026-02-17T12:00:01Z",
"duration_ms": 1042,
"provider": "runtime.commandlayer.eth"
},
"status": "success",
"result": {
"summary": "Input contains three distinct claims with supporting evidence.",
"insights": ["claim_count: 3", "evidence_ratio: 0.87"],
"score": 0.87
},
"metadata": {
"proof": {
"alg": "ed25519-sha256",
"canonical": "runtime-json-stringify-v1",
"signer_id": "runtime.commandlayer.eth",
"hash_sha256": "b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9",
"signature_b64": "RkFLRV9TSUdOQVRVUkVfRk9SX0RFTU8..."
}
}
}
Canonically serialized
Receipts use a frozen canonical form (
runtime-json-stringify-v1) for deterministic byte representation.
Deterministically hashed
SHA-256 over the canonical bytes. Same input always produces the same hash.
Cryptographically signed
Ed25519 signature over the hash bytes, bound to the executor's ENS identity.
Publicly verifiable
Any third party can verify: resolve the signer's public key via ENS, recompute the hash, check the signature.
Commons vs. Commercial
Execution semantics are universal. Monetization is modular.
Commons
- Public verbs:
analyze,classify,clean,convert,describe,explain,fetch,format,parse,summarize - Free endpoints
- Open schemas (MIT)
- Same receipt format
Commercial
- Economic verbs:
authorize,checkout,purchase,ship,verify - x402 pay-per-call
- Same schema structure
- Same receipt format