Nominal Windows
What is nominal is not fixed. It evolves with the load.
As autonomous agents act on-chain at scale, their collective behavior modifies blockchain demand patterns — block saturation, transaction profiles, bridge posting cadence. The infrastructure baseline shifts. What was nominal yesterday may not be nominal today.
Invarians measures these shifts continuously and communicates the current nominal window — not as a static threshold, but as a live reading calibrated against each chain's own evolving distribution. The agent knows when the system is most nominal. The decision is its own.
The Logical Pipeline
1
Finalized on-chain data
Public blockchain data only. No mempool. No price feeds. No prediction.
→
2
Two measurement layers
Structural layer and demand layer — independently measured on each chain and each rollup.
→
3
State classification
L1 chains: four regimes S1D1 · S1D2 · S2D1 · S2D2, calibrated per chain. L2 rollups: execution profile signals.
→
4
Proof of Execution Context
Cross-layer infrastructure context — certified, signed, timestamped.
→
5
Agent Policy
The agent applies its own policy. The Pattern Reference maps each L1 · L2 · bridge combination to documented historical events.
Coverage
Three infrastructure layers. Independently measured.
L1 — Ethereum · Polygon · Solana · Avalanche
Structural regime (τ) and demand pressure (π) — four certified states per chain: S1D1 · S1D2 · S2D1 · S2D2.
L2 — Arbitrum · Base · Optimism
Rollup execution profile — throughput, transaction composition, blob saturation. Distinct framework from L1.
Bridge — L2 to L1 batch posting
Batch posting continuity measured from finalized L1 data. BS1 nominal · BS2 posting gap detected. Invisible to fee monitors post-EIP-4844.
Two Primitives
Two factual outputs. The agent owns the policy.
Since EIP-4844 (March 2024), L2 sequencer incidents and bridge posting gaps produce no economic signature on L1. Fee monitors are structurally blind to what happens below the surface. Invarians measures it directly — from finalized, public on-chain data.
01
Proof of Execution Context
The certified state of the infrastructure at the moment of query — L1 regime, L2 regime, bridge state. Signed HMAC-SHA256. Timestamped. Independently verifiable.
Details →
02
Pattern Reference
The historical record of each execution context — 32 combinations of L1 · L2 · bridge states mapped to documented events and observed frequencies. Not prescriptive.
Details →
// GET /attestation/execution-context — one call, full cross-layer state
proof_of_execution_context {
l1_regime: "S1D1", // structural · demand — both nominal
l2_regime: "S1D2", // demand elevated — throughput above baseline
bridge_state: "BS1", // batch posting nominal
}
signature: "inv_sig_4xKm9zR2pL...", // HMAC-SHA256 — verifiable via /verify
issued_at: "2026-03-28T14:22:01Z",
expires_at: "2026-03-28T15:22:01Z"