The settlement route logbook.

Execution context for AI agents on blockchain corridors: the operational state of settlement routes, recorded at the moment and retained. Built for settlement of tokenized real-world assets, not for trading.

Read the September 3rd case
Daily since March 2026
Chains since March, corridors since May
0 missing days
Across the ten CCTP corridors, since capture began
6 chains · 20 corridors
EVM L1 and L2, Circle CCTP, Chainlink CCIP
Every record dated
Timestamped at observation and retained
The question

When your AI agent settles across chains: what independent record of the route's state existed at that moment?

Agents act on context. After the fact, three questions decide whether that context can stand in an audit file.

01
Who produced it?
A party with no stake in the route, the trade, or the agent.
02
Was it available before the agent acted?
Served as signed execution context, consumable by the operator's own policy.
03
Can it be produced when someone asks?
A dated record of the route's state at that moment, kept at the time, not reconstructed after the question.
Method

Recorded at the moment. Kept by no one involved.

Recorded, not reconstructed

On-chain facts can be recomputed forever. Whether attestations were available, whether services answered: that exists only if recorded at the time. Invarians records it as it happens.

Kept by no one involved

Invarians does not operate a rail, does not trade, and does not act for agents. It has no position in the routes it records.

Ready for the question

Each route carries its own measured normal, built day by day. When someone asks what was known at that moment, the answer is a dated page from the record.

Evidence

No incident reported. That day, one route settled three times slower.

Ten CCTP corridors, observed every ten minutes since May 2026. 1,020 route-days carry a qualified 30-day baseline; exactly two show a deviation, both on September 3rd (statistics as of October 2026). One route into Ethereum ran at 3.3 times its measured normal; a second route, from a different chain, deviated the same day. The status pages of the chains involved and of Circle listed no incident for September 3rd.

Daily settlement latency of the Polygon to Ethereum CCTP corridor, July to October 2026, relative to its 30-day baseline, with the September 3rd deviation at 3.3 times baseline marked.

Observed at a 10-minute capture cadence; relative scale, against the route's own 30-day baseline. Every day is on record; a route enters the statistics once it carries 30 days of its own history, and one October instrument window is flagged in the record and kept out of the statistics.

The same record holds the chains themselves: 2,488 stress episodes since March 2026, each measured against that chain's own normal.

Who it serves

Two readers, one record.

Teams deploying agents

Operations and engineering

  • Signed execution context your agents consume before acting, under your own policy.
  • Delay attribution input: a dated record of corridor state that helps distinguish a slow corridor from a slow integration.

Coverage and terms →

The risk function that approves them

Risk, compliance and audit

  • An independent source of operational evidence alongside the operator's own logs.
  • Audit-trail input: route state records, dated at observation, retained.

Obligations, point by point →  ·  Vendor file →