The Sensing Layer

Agentic systems execute. Invarians makes execution observable.

Autonomous agents operating on-chain act on infrastructure that produces no observable signal when it degrades. Structural stress, sequencer degradation and bridge anomalies are all invisible to fee monitors. No blockchain today exposes its own structural state.

No blockchain today can describe its own state.
"Systems that cannot sense themselves cannot scale."

CRE Integration → API Docs

The structural gap

Execution layers no longer reflect their own state.

Since EIP-4844 (Dencun, March 2024), L1 basefee decoupled from L2 activity. Sequencer outages, bridge posting gaps and structural anomalies produce no economic signature on L1. Fee monitors are 100% blind to them. Every cross-chain agent operating today has no native observability of the substrate it executes on.

Arbitrum: June 20, 2024 Documented incident

L1 ETH basefee 7 – 25 gwei: normal

L2 ARB activity Silence

Bridge status No alert

Agent signal Execute

What was actually happening

L1 ETH regime S1D1: nominal

L2 ARB basefee ×1,649 above nominal

Bridge posting gap 37 minutes: BS2

Invarians signal S1D2 × BS2: degraded

A cross-chain agent executing that day operated on completely false premises. The substrate was in stress. The fee monitor said green.

Two distinct layers

Execution and sensing are separate concerns.

Every agentic system has an execution layer that orchestrates, calls and coordinates. No agentic system today has a layer that observes the structural state of the blockchain substrate it acts on.

Concern	Execution layer	Sensing layer: Invarians
Role	Orchestrate, call, coordinate	Observe structural substrate state
What it knows	What to do, when, how	What the infrastructure is doing right now
Blind spot	Sequencer degradation, bridge stress, structural regime shifts	None: that is exactly what it measures
Signal type	Transaction status, gas price, confirmations	Signed regime attestation: L1 × L2 × Bridge
Examples	Chainlink CRE, intent solvers, keepers, RWA automation	Invarians oracle: live, calibrated, signed

Execution tells systems what to do.
Sensing tells them whether it is safe to do it.

SxDx: The regime framework

Four execution contexts. One sensing layer.

Invarians classifies the blockchain infrastructure state across two independent axes: τ (structural rhythm) and π (demand pressure). Each combination maps to an execution context with distinct implications for autonomous agents.

S1D1

Safe

Structural rhythm nominal. Demand within baseline. Infrastructure operating as calibrated.

Agent implication: standard execution conditions. Full throughput available.

S1D2

Congested but stable

Demand above baseline: blocks heavier, more transactions. Infrastructure holds structurally.

Agent implication: elevated costs, no structural risk. Fee-sensitive agents adjust.

S2D1

Hidden stress

Infrastructure slowing: block rhythm deviating from baseline. Demand appears normal. Invisible to fee monitors.

Agent implication: structural degradation in progress. The dangerous regime: nothing shows on gas.

S2D2

Critical

Both axes elevated simultaneously. Structural stress combined with demand surge.

Agent implication: compound stress. High execution risk across both dimensions.

L1 and L2 are measured independently. Bridge state (BS1 nominal / BS2 degraded) adds a third dimension. A complete attestation covers all three layers simultaneously.

What sensing provides

A signed attestation of infrastructure state.

Every call to Invarians returns a cryptographically signed snapshot of the current execution context: regime, freshness, and lineage. The agent applies its own policy. Invarians observes infrastructure state and signs it. Nothing more.

"chain":          "arbitrum",
"oracle_status":  "FRESH",
"l1_regime":      "S1D1",
"l2_regime":      "S1D2",
"bridge_state":   "BS1",
"l2_verified":    true,
"data_age_seconds": 312,
"signature":      "inv_sig_..."

Calibrated per chain

Thresholds derived from 4+ years of BigQuery backtests. ETH: 34,697 windows, FPR 1.23%. Polygon: 25,906 windows. No cross-chain normalization.

Cryptographically signed

HMAC-SHA256 attestation on every response. Ed25519 signatures across the internal collection pipeline. Independently verifiable via /verify.

Agent-owned policy

Invarians publishes infrastructure state. The agent applies its own execution policy. There is no execution window, no recommendation, no prescription embedded in the signal.

Execution layers (e.g. CRE)

Every execution layer benefits from sensing.

Invarians is not built for one platform. Any system that executes autonomously on blockchain infrastructure gains observability by integrating the sensing layer.

Orchestration

Chainlink CRE

Runtime Environment for autonomous on-chain agents. Invarians provides the structural sensing layer missing from the execution stack.

Cross-chain execution

Intent Solvers

Across Protocol, Li.Fi, Uniswap X: routing cross-chain transactions. Bridge state (BS1/BS2) and L2 regime are directly relevant to fill logic.

Institutional automation

RWA & Keepers

Ondo Finance, tokenized asset managers, automated compliance workflows: execution context for audit trails and risk-aware operation.

A Chainlink CRE agent without Invarians orchestrates execution without knowing if the sequencer is in S2D1 or the bridge is in BS2 at execution time. The Arbitrum incident of June 20, 2024 is the documented example of what that costs.

See the complete CRE integration guide →

Agentic sensing: live now

Observe the substrate
your agents execute on.

Invarians is live. L1 + L2 + Bridge. ETH, Polygon, Solana, Avalanche, Arbitrum, Base, Optimism. Signed attestations. Free tier available.

CRE Integration → API Docs Live oracle

invarians.com · Built for autonomous agents