Invarians
GOVERNANCE / HOW IT WORKS /
Centralized · Available Developers API · SDK docs Fundamentals How it works Products What you get Test Test the API
CRE Integration Hybrid · Chainlink DON Preview · Late 2026-2027
Decentralized · INVAR Network 2028
/
ANS-Vx Methodology, backtests, registry Evidence 30-day reproducible regimes Labs Pattern observatory, agentic baseline Agentic Agent-facing surfaces (A2A, MCP)
BLOG ROADMAP FAQ LOGIN GET API ACCESS ADMIN

For banks, RWA issuers, treasuries, and the agents acting on their behalf.

Give your agents auditability inputs on the state of chains, bridges and settlement routes, signed by a party with no stake in the transaction.

Invarians builds a decentralized layer exposing

CROSS-CHAIN EXECUTION CONTEXT FOR AGENTS

Centralized alpha now, building toward a Chainlink CRE-DON, then an independent network.

Four things the signed context lets an institution demonstrate: the conditions its systems consumed when an operation executed, the state of the observed settlement route, what was exposed during an incident, and all of it verifiable by a third party. Three primitives in one signed payload: Attestation, Regime + Bridge State, Delta. Alpha SDK live.

Sequencer slowdowns, validator pressure, agentic load and protocol upgrades shift the substrate beyond fee-monitor visibility. From finalized public data, Invarians separates routine substrate noise from persistent structural change, and attests the context a client system consumed when it acted.

In use for DeFi risk, DAO treasury, intent-solver and Chainlink CRE workflows, open to early integrators.

GET AN API KEY →

Early access·Open methodology·Reproducibility kit on public BigQuery

What institutions must be able to demonstrate

Four auditability outcomes, derived from documented requirements.

01 · EXECUTION EVIDENCE
How is exposure to blockchain infrastructure monitored, and with what evidence?
Ad hoc captures and vendor dashboards do not constitute reviewable evidence. Invarians provides a signed record of the observable conditions the client system consumed when an operation was authorized and executed.
Relevant documented requirements: Basel SCO60, DORA, SEC 17a-4.
02 · SETTLEMENT-ROUTE EVIDENCE
How is the state of a settlement route established across its components?
Each component can appear nominal in isolation while the route degrades. Invarians composes the state and progression of the complete observed settlement route into one signed tuple, within declared coverage.
Relevant documented requirements: PFMI finality, Basel settlement-finality documentation duties.
03 · INCIDENT RECONSTRUCTION
How are operations exposed to an infrastructure degradation identified after the fact?
Invarians establishes the degradation window and conditions, exportable, against which the institution identifies its exposed operations from its own order log, and documents the established return to nominal.
Relevant documented requirements: DORA Articles 11 and 17.
04 · INDEPENDENT VERIFICATION
How is operational evidence made independently reviewable?
Internal logs are simultaneously the data, the interpretation and the proof. Invarians produces evidence a third party can verify without depending on the institution's logs, or on trust in Invarians.
Design principle: independent third-party verification (a Basel requirement in the reserve-disclosure context).
The requirements registry

Built on the regulation, not around it.

Invarians is built on a frozen corpus of 91 regulatory, institutional and technical sources, Basel, DORA, MiCA, MiFID, the SEC and CFTC record rules among them. From that corpus, 144 requirements are extracted, each carrying its verbatim quote and the hash of its source text, and each mapped to the metric that serves it. The four outcomes above, and the layer that produces them, rest on this documented basis: network-risk monitoring, settlement finality, incident management, record retention, independent verification.

The corpus and the mapping are public and versioned, so any requirement we act on can be traced back to the exact text it comes from.

Have a regulatory text we should read?

Institutions, counsel, researchers and builders can propose a regulatory or institutional text material to the layer, and attach the document. Each submission follows a public lifecycle: capture, freeze with hash, extraction, verification against the source, registry entry. Published inclusion criteria; submission does not guarantee inclusion; nothing here is legal advice.

Submit & attach a text →
Coverage

What agents read before they act.

Every signed context comes from continuous coverage of the chains your agents operate on: a smoothed hourly reading, bridge observations on 10 to 15 minute windows, freshness and windows declared, no real-time claim. Live scope today:

Full topology, lanes and routes →
Live stress events · last 30d
—
structural deviation episodes: moments the substrate left its own nominal, live proof that it does
By chain
ETH
—
POL
—
ARB
—
BASE
—
OP
—
—last 24h
—last 7d
—ongoing
View full archive →
Who is Invarians for today?

Substrate context for agents protecting protocols and executing institutional flows.

Who Invarians is for today and the north-star scope A layered diagram showing the Invarians substrate observability layer measuring underlying rails (Ethereum L1, rollups, bridges) and exposing primitives consumed by two families of agents, surveillance and execution, which serve protocols and institutions. Out of scope and Phase 02-03 north star are shown below. Underlying rails Ethereum L1, rollups L2, bridges (CCTP, CCIP) Invarians substrate observability layer Signed regimes, drift, polarisation, dispersion, On-Chain Execution Context Surveillance agents Observe · detect · protect DeFi risk modelers CRE structural gates ref: Chainlink RMN, XChainWatcher Execution agents Route · time · settle DAO treasury rebalancing Intent solvers, keepers ref: Chaos Labs Horizon, ISDA Guardian Protocols and institutions Chainlink, Circle, foundations, RWA issuers, treasury, banks OUT OF SCOPE Retail daily trading, HFT, MEV extraction, micro-transfers NORTH STAR · PHASE 02-03 Institutional RWA settlement at production scale Hybrid Chainlink DON Late 2026-2027 Decentralised network 2028

Institutional RWA settlement at production scale requires multi-party attestation and decentralized verification. That trust model arrives with the hybrid Chainlink Functions DON deployment (late 2026 to 2027) and the decentralized network (2028). Until then, the Phase 01 centralized pipeline is appropriate as a complementary structural signal in risk dashboards, not as a settlement gate.

Current and target trust models

One payload, three levels of trust: available today, and on the way.

Available · Centralized alpha
Centralised
API · SDK · single RPC
Signed execution context
HMAC-SHA256 signed (single-operator trust)
API + SDK · early access (Alpha, breaking changes expected)
L1 × L2 · 7 chains · 20 variable-latency bridges (CCTP V2 live BS1/BS2 under v1.2, CCIP V1.5 / V1.6 hybrid per-message captured)
Trust model : Invarians server
Signing : single node
Not a decentralized proof
Quick Start →
Late 2026-2027
Hybrid
Chainlink Functions · DON · Multi-RPC
DON threshold signature
Multi-RPC · independent nodes
Cryptographically verifiable
CRE · Chainlink Functions
Requires Chainlink CRE
Algorithm authored by Invarians
Not yet in production
Preview →
2028
Decentralised
INVAR Network · Node · Stake
Independent node network
Stake to compute · node rewards
On-chain baselines · open methodology
Ed25519 per-node signing
Not yet available
Coming 2028
A2A · Agent-to-Agent Signed context shared between agents before a cross-chain action. Each agent references and verifies the same record instead of relying on the other's internal logs. A2A diagram →
Developers
API · SDK · Quick Start
DEVELOPERS →
Agentic
MCP · CRE · A2A
AGENTIC ↗
Labs
Live data · Calibration · Patterns
LABS ↗