Every system, with its real status

This page is generated from the chain registry — the same flags the SDK and the anchoring API enforce. A network is never described beyond its integration status, and planned integrations are labeled planned.

Storage systems

Networks whose transactions can carry chunk bytes — where an artifact's content can optionally live on-chain. Storage is always an explicit opt-in; hash-only evidence is the default.

Showing 52 of 52 networks


Ethereum	EVM-compatible	Roadmap adapter	Implemented
Base	EVM-compatible	Roadmap adapter	Implemented
Auto EVM	EVM-compatible	Roadmap adapter	Testnet deployed
Optimism	EVM-compatible	Roadmap adapter	Implemented
Arbitrum One	EVM-compatible	Roadmap adapter	Implemented
Polygon	EVM-compatible	Roadmap adapter	Implemented
BNB Smart Chain	EVM-compatible	Roadmap adapter	Implemented
Avalanche C-Chain	EVM-compatible	Roadmap adapter	Implemented
zkSync Era	EVM-compatible	Roadmap adapter	Implemented
Scroll	EVM-compatible	Roadmap adapter	Implemented
Linea	EVM-compatible	Roadmap adapter	Implemented
Mantle	EVM-compatible	Roadmap adapter	Implemented
Blast	EVM-compatible	Roadmap adapter	Implemented
Celo	EVM-compatible	Roadmap adapter	Implemented
Ethereum Sepoliatestnet	EVM-compatible	Active	Testnet deployed
Base Sepoliatestnet	EVM-compatible	Roadmap adapter	Implemented
Auto EVM Chronostestnet	EVM-compatible	Active	Testnet deployed
OP Sepoliatestnet	EVM-compatible	Roadmap adapter	Implemented
Arbitrum Sepoliatestnet	EVM-compatible	Roadmap adapter	Implemented
Polygon Amoytestnet	EVM-compatible	Roadmap adapter	Implemented
BNB Smart Chain Testnettestnet	EVM-compatible	Roadmap adapter	Implemented
Avalanche Fujitestnet	EVM-compatible	Roadmap adapter	Implemented
zkSync Sepoliatestnet	EVM-compatible	Roadmap adapter	Implemented
Scroll Sepoliatestnet	EVM-compatible	Roadmap adapter	Implemented
Linea Sepoliatestnet	EVM-compatible	Roadmap adapter	Implemented
Mantle Sepoliatestnet	EVM-compatible	Roadmap adapter	Implemented
Blast Sepoliatestnet	EVM-compatible	Roadmap adapter	Implemented
Celo Alfajorestestnet	EVM-compatible	Roadmap adapter	Implemented
Autonomys Mainnet	Substrate-based	Active	Integrated into the webapp
Autonomys Taurustestnet	Substrate-based	Active	Integrated into the webapp
Polkadot Asset Hub	Substrate-based	Roadmap adapter	Implemented
Kusama Asset Hub	Substrate-based	Roadmap adapter	Implemented
Westend Asset Hubtestnet	Substrate-based	Roadmap adapter	Implemented
Paseo Asset Hubtestnet	Substrate-based	Roadmap adapter	Implemented
Solana	Solana	Active	Integrated into the webapp
Solana Devnettestnet	Solana	Active	Integrated into the webapp
Aptos	Aptos	Roadmap adapter	Implemented
Aptos Testnettestnet	Aptos	Roadmap adapter	Implemented
Sui	Sui	Roadmap adapter	Implemented
Sui Testnettestnet	Sui	Roadmap adapter	Implemented
Starknet	Starknet	Roadmap adapter	Implemented
Starknet Sepoliatestnet	Starknet	Roadmap adapter	Implemented
NEAR	NEAR	Roadmap adapter	Implemented
NEAR Testnettestnet	NEAR	Roadmap adapter	Implemented
TRON	TRON	Roadmap adapter	Implemented
TRON Niletestnet	TRON	Roadmap adapter	Tested locally
Cardano	Cardano	Roadmap adapter	Implemented
Cardano Preprodtestnet	Cardano	Roadmap adapter	Tested locally
TON	TON	Roadmap adapter	Implemented
TON Testnettestnet	TON	Roadmap adapter	Tested locally
Hedera	Hedera	Roadmap adapter	Implemented
Hedera Testnettestnet	Hedera	Roadmap adapter	Implemented

Settlement systems

Networks where a hash or Merkle root is fixed in time for the system's ordinary transaction fee. Each settlement receipt is an independent, system-native attestation — several of them make the evidence portable, not “more proven.”

Showing 2 of 2 networks


Cosmos Hub	Cosmos	Roadmap adapter	Implemented
Cosmos Hub Testnettestnet	Cosmos	Roadmap adapter	Tested locally

Agent frameworks

Planned integrations that seal evidence from inside agent runtimes, per the Agent Evidence Profile.

OpenAI Agents

Planned

Seal run outputs and tool-call digests straight from an agent-framework hook.

MCP

Planned

The FileOnChain MCP server already anchors via the hosted API; profile-aware sealing of MCP tool activity is next.

Developer tooling

Surfaces that carry an envelope's verifier result somewhere else — a README, a release note, a timeline. Each one repeats the local verifier's status word for word.

Share links & status badge

Available

A /verify?url= link reproduces the report in the reader's browser and carries a social card painted from the verifier's result; /api/badge?url= is an SVG whose text is the offline verifier's status for the envelope at that URL. Never a single green “verified”.

MCP server

Available

A stdio MCP server for Claude Code, Cursor, and other MCP clients. A Cloud + SDK integration, not part of the protocol: verify_evidence runs the local verifier in-process with no key; the anchoring tools spend account credits through the hosted API.

GitHub Action: seal a release

Starter

Hashes release artifacts into a manifest, seals it with the reference SDK, attaches the envelope to the GitHub Release, and appends the badge to the notes. Runs on this repository's own releases; not on the Marketplace, and it installs the SDK from the monorepo because the packages are not on npm yet.

Add the MCP server to Claude Code in one line (Cursor and other clients take the same command as an mcpServers entry):

terminal

claude mcp add fileonchain -- npx -y @fileonchain/mcp

Observability platforms

FileOnChain complements tracing systems rather than replacing them: traces are imported by reference and digest — the observability platform stays the system of record.

OpenTelemetry

Planned

Reference and hash exported spans as trace claims — the trace stays in your collector; its digest travels in the envelope.

Langfuse

Planned

Import a trace by reference and digest, per the Agent Evidence Profile's traceRefs.

LangSmith

Planned

Same referenced/hashed trace import — evidence about the run, never a copy of it.