Not a binary signal. A structural regime, rhythm, demand, divergence from nominal, across L1, L2, and bridge.
Most on-chain agent infrastructure answers one question: what is the price?
Invarians answers a different one: is the infrastructure ready to execute?
Block rhythm, sequencer health, bridge liveness, these are structural signals that determine whether an agent's decision will land cleanly or into a degraded environment. Price feeds don't carry that information. The RPC doesn't either.
What Invarians actually returns
Invarians classifies each chain into a regime across two axes, structural (τ) and demand (π), producing a signed attestation an agent can consume before acting:
{
"chain": "ethereum",
"regime": "S1D1",
"divergence_index": 0.08,
"oracle_status": "OK",
"bridge_state": "BS1",
"signature": "inv_sig_..."
}
The agent reads the structural regime across L1, L2, and bridge, then routes execution to the layer that best matches its risk parameters. L1 stressed, L2 nominal → prefer L2. Bridge degraded → defer cross-chain.
The Chainlink path
The schema below illustrates a future integration inscribed in Invarians' public roadmap: Chainlink Functions embedding the Invarians algorithm directly inside the DON. Each node computes the regime independently on its own RPC, consensus is reached, and a DON-signed attestation is delivered to the agent inside the CRE.
A context layer agents can query. A methodology the DON can run. A proof the chain can hold.
Top comments (0)