Docs Sign in Create account

Changelog

Changes a customer would notice, newest first. Internal work is not here — a changelog that lists every commit is a changelog nobody reads.

Free Beta

September 2026

Fixed

  • A native balance can now be asked for. asset is optional on balance.get; omitting it reads the native coin. It used to be required, and no value of it meant the native coin — so the commonest question an access API is asked could not be expressed at all.
  • A refusal the engine made is no longer reported as a source outage. ENGINE_REFUSED is a new code: 422, never retryable, and carrying detail.engine_said, which is the engine’s own sentence about what to change. It used to arrive as UPSTREAM_UNAVAILABLE with advice to back off, while the providers were answering normally.
  • Payment watches work on every followed network. Nine networks were being polled and every watch on them was refused for lacking a capability they do not use. XRPL, Stellar and TON additionally had no way to carry a destination tag, memo or comment, so a watch was accepted and could never match; routing is now a field on the watch.
  • network.status now describes the engine that is running. It reported a stand-in built at start-up, which said UNINITIALIZED for ever on every network.
  • Usage counts are no longer always zero. The dashboard read a field that does not exist on a usage summary and rendered its fallback.

Added

  • A public status page, with per-component state and published incidents. No uptime figure: nothing here measures availability.
  • A support surface that attaches your account, organization, project and a request id, and never an API key or a request body.
  • A request log on your usage page: every call with its id, network, method, outcome and latency.
  • Beta limits, published with the measurement each number came from, enforced at seven scopes.
  • Per-network pages, generated from the deployment.
  • /.well-known/security.txt and /llms.txt.

Changed

  • Per-project defaults are lower. They used to exceed the deployment’s own measured safe capacity: four projects at their documented defaults saturated it. See Limits for the new numbers and the measurement behind each.
  • Sign-up and sign-in now carry a CSRF token. A cross-site POST could previously create an account or sign somebody in.

Known and unfixed

  • Email verification is unavailable. No mail provider is configured, so no address can be proved and PRODUCTION authority stays shut. TEST projects carry the same read capabilities.
  • Four payment networks are not served here. Ethereum, Tron, Solana and Bitcoin need a Data plane this deployment does not run.
  • No periodic availability probe. /v1/status reports UNKNOWN for every network’s availability because nothing checks on a schedule. The status page says so rather than borrowing another number.
  • No client libraries. See SDKs.

A dated entry appears here when something a customer would notice changes. Live component state is on the status page; incidents are published there rather than here.