Changelog

Release status and where the release record lives

Changelog

QTG is pre-1.0. Tagged releases (v0.1.0, plus v0.1.0-alpha.N prereleases) go to the OSS repo; CHANGELOG.md in that repository is the release record, structured per release as security-relevant changes, runtime safety, provider/adapter work, breaking config or migration steps, evidence, and known limitations.

This documentation describes the current state of the development line rather than a version you can pin. Nothing here carries a compatibility promise yet.

Pre-1.0 means interfaces move without deprecation cycles — the HMAC canonical string, the template schema, and the executor protocol have all changed within a single month. Read Security Tradeoffs before pointing this at real funds.

Boundary changes worth knowing

Signer lifecycle administration moved to Pro. Shared schema, signer adapters, and movement-time safety remain Free — an OSS deployment still signs, still enforces the address allowlist, still re-derives the recipient from the signed artifact. What moved is the administrative surface: generic signer reads and the shared dashboard no longer expose lifecycle history.

The HMAC middleware refuses requests served under an ASGI path prefix. The signature covers scope["path"], which excludes the prefix, so a prefixed deployment would have accepted unsigned requests. It now returns 503 instead. Put QTG behind a proxy that forwards the original path.

CEX internal capital transfers and privileged Binance sub-account balance reads moved to Pro. New POST /v3/capital-transfers submission is disabled by default; install Pro and explicitly set MG_CAPITAL_TRANSFER_MUTATIONS_ENABLED=true before enabling it. Pending rows remain observable while new submissions stay disabled.

CCIP advisory readiness/quote and the governed route catalog are Pro. The governed CCIP route catalog, readiness projection, and quote surface (MG_CCIP_ENABLED, default false) ship only in the Pro package; the OSS build exposes the CCIP concept pages but no executable CCIP lane.

USDT0 (LayerZero native-OFT) lane is Pro. Registered under MG_USDT0_ENABLED (default false) with its own pre-broadcast intent ledger and governed templates; no executable LayerZero lane ships in OSS.

Circle credential-authority foundation landed (JEP-740 line). Credential authority services (provisioning, readiness, cutover, settlement, attestation, usage) plus protected credential material primitives and live admin bearer eligibility enforcement; credential containment and the qtg auth revoke-credential governed lifecycle are current behavior.