PRODUCTS
The coverage surface of the three primitives. Every L1, L2, CCIP lane, and CCTP route currently tracked is listed below. Each direction is treated as a distinct signal because source-chain finality drives bridge latency, and CCIP / CCTP topologies are physically asymmetric per direction.
Invarians certifies what the infrastructure is at the moment of query. It does not prescribe execution decisions, recommend strategies, or encode risk tolerance. The three primitives below (Attestation, Regime, Drift Signal) are factual outputs grounded in measurement. The agent owns the execution policy.
Primitive 1 (Attestation) envelopes the entire panel via HMAC-SHA256, regardless of underlying signal type. Applies universally.
Primitive 2 (Regime) classifies state. For L1 and L2 substrates, 12 signed codes (S1+, S2-, D1+, D2+, etc.) capture both structural cadence and demand dimensions. For bridges, a binary state (BS1 nominal, BS2 degraded) reflects pipeline health.
Primitive 3 (Drift Signal) tracks deviation from a 30-day baseline using exponential moving averages. It is a substrate-physics concept: chains evolve under agentic load on the scale of weeks. Bridges are operational pipelines, not substrates; their fitness-for-action is captured directly by current latency P90/P99, success rate, and crypto anchor verifiability, without a drift signal.
Per-chain structural regime (12 signed S/D codes) computed on a rolling 30-day baseline. Each L1 has independent observables (rhythm, beacon participation where applicable, structural cadence) and an independent drift signal.
| Chain | Calibration | Regime signal | Drift signal |
|---|---|---|---|
| Ethereum | Calibrated 2026-04 | Active | Active |
| Polygon | Calibrated 2026-04 | Active | Active |
| Avalanche | Calibrated 2026-04 | Active | Active |
| Solana | Calibration scheduled 2026-Q3 | Planned 2026-Q3 | Planned 2026-Q3 |
Solana sits on a different substrate physics family from EVM chains (slot-based 400ms cadence, leader rotation, vote economics). Calibration on Solana requires its own observable set distinct from EVM chains, programmed for 2026-Q3.
Per-rollup regime tracking sequencer publish latency P97, batch posting cadence, and inclusion behavior. Anchored to Ethereum L1 finality for parent-chain context.
| Chain | Type | Calibration | Signal status |
|---|---|---|---|
| Arbitrum | Optimistic rollup | Calibrated 2026-04 | Active |
| Base | Optimistic rollup | Calibrated 2026-04 | Active |
| Optimism | Optimistic rollup | Calibrated 2026-04 | Active |
Each CCIP lane has its own OnRamp / OffRamp / RMN configuration. ETH→ARB and ARB→ETH are two physically distinct lanes with separate contracts and potentially different DON commit cadences. Each direction is processed as an independent signal.
| Lane | Source events (OnRamp) | Destination events (OffRamp) | RMN check | Status |
|---|---|---|---|---|
| ETH → ARB | Captured | Captured | Both sides | Active |
| ARB → ETH | Captured | Captured | Both sides | Active |
| ETH → BASE | Captured | Captured | Both sides | Active |
| BASE → ETH | Captured | Captured | Both sides | Active |
| ETH → OP | Captured | Captured | Both sides | Active |
| OP → ETH | Captured | Captured | Both sides | Active |
| ETH → POL | Captured | Captured | Both sides | Active |
| POL → ETH | Captured | Captured | Both sides | Active |
| ETH → AVAX | Captured | Captured | Both sides | Active |
| AVAX → ETH | Captured | Captured | Both sides | Active |
| ETH → SOL | Pending | Pending | Pending | Planned 2026-Q3 |
| SOL → ETH | Pending | Pending | Pending | Planned 2026-Q3 |
ETH ↔ SOL CCIP is the only lane in the matrix that crosses substrate physics families (EVM blocks vs Solana slots). It is treated as a primary observability target for 2026-Q3 once the Solana side of the CCIP infrastructure (dual-RPC capture, program log parsing) is integrated.
CCIP capability level: per_message_attested. Source send and destination execute are matched per message via the bytes32 messageId. Latency P90 is computed on captured messages. crypto.anchor is null today (no per-message cryptographic anchor captured yet for CCIP).
CCTP attestation latency is dominated by source-chain finality: the Circle Iris service waits for source confirmation before issuing the attestation. ETH→X and X→ETH therefore have fundamentally different latency distributions because L1 finality (~13 min) is much slower than L2 soft confirmations.
Each attested message is captured with its Circle ECDSA signature (65-byte secp256k1). This signature is independently verifiable against Circle's published attester public key, anchoring CCTP route signals in a cryptographic chain of trust distinct from the Invarians HMAC envelope. Per-message attestations are retrievable via /v2/cctp/attestation/{message_hash}.
| Route | DepositForBurn (source) | Iris attestation latency | MessageReceived (dest) | Status |
|---|---|---|---|---|
| ETH → ARB | Captured | Captured · ECDSA | Captured | Active |
| ETH → BASE | Captured | Captured · ECDSA | Captured | Active |
| ETH → OP | Captured | Captured · ECDSA | Captured | Active |
| ETH → AVAX | Captured | Captured · ECDSA | Captured | Active |
| ARB → ETH | Captured | Captured · ECDSA | Captured | Active |
| ARB → BASE | Captured | Captured · ECDSA | Captured | Active |
| BASE → ETH | Captured | Captured · ECDSA | Captured | Active |
| BASE → ARB | Captured | Captured · ECDSA | Captured | Active |
| OP → ETH | Captured | Captured · ECDSA | Captured | Active |
| AVAX → ETH | Captured | Captured · ECDSA | Captured | Active |
| ETH → SOL | Pending | Pending | Pending | Planned 2026-Q3 |
| SOL → ETH | Pending | Pending | Pending | Planned 2026-Q3 |
ETH ↔ SOL CCTP is the only route where the source event lives in EVM logs on one side and in a Solana program log on the other. The attestation client is chain-agnostic (Iris consumes a message hash regardless of source chain), so the integration cost sits in the source / destination capture path, not in attestation handling. Targeted for 2026-Q3.
/v2/panel. For CCTP routes, this includes per-message ECDSA attestation capture (capability level: per_message_attested). Calibration validated against historical baselines.
Every entry in the four matrices above feeds the same panel response. L1 / L2 entries populate panel.l1[] and panel.l2[] with their structural regime (12 signed S/D codes) and drift signal (Primitive 3, substrate-physics). Each CCIP lane and CCTP route appears as one bridge entry in panel.bridges[] with its unified state (BS1 nominal, BS2 degraded), capability_level: per_message_attested for both protocols, with per-message metrics. crypto.anchor differs by protocol: circle_ecdsa for CCTP, null for CCIP (no per-message cryptographic anchor captured yet). Bridges do not carry a drift signal: as operational pipelines rather than substrates, their fitness-for-action is captured directly by current latency P90/P99, success rate, and crypto anchor verifiability. The signed execution context wraps the full panel; integrity is verifiable via POST /v2/verify.