Known limitations

The current release is intended for evaluation, processor development, reproducible backfills, and guarded application integrations with an independent fallback.

• It is not a complete Ethereum archive node and does not maintain EVM state. Arbitrary eth_call, balances, storage, proofs, tracing, and state-diff RPC are not served by the EVM-free core.
• Xatu rows are trusted public dataset input. Sparse EraE material verifies execution commitments but still depends on an external catalog until the planned consensus-root anchoring is complete. Source trust is exposed and must not be described as fully trustless history.
• Raw RPC history is post-merge exact. Ommer-aware pre-merge exactness is deferred.
• Only configured processor material and bounded recent/raw-history profiles are queryable. Pruned material must be reacquired.
• The native browser SDK requires same-origin hosting or an application-owned reverse proxy with an explicit CORS policy, and the page’s origin in api.allowed_origins.
• Mainnet multi-day soak, chaos, abrupt-power-loss, broad cross-source parity, and every advertised host sweep remain release gates for a production claim.
• JSON-RPC has no built-in access control, and the API bearer is the only credential for admin routes. A bind beyond loopback needs the API bearer or an explicit allow_unauthenticated_remote opt-in; such deployments must still use a trusted network or authenticated reverse proxy and must not expose admin/debug endpoints publicly.

Treat this page and the release process as the public scope boundary for the current release.