Releases
Find the current release evidence and adoption checks without mistaking a release candidate for stable production software.
Trust, applicability, and sourcesCurrent public project policy or service surface
Current release candidate
v0.3 is intended for evaluation and testnet use. Stable binaries and signed release artifacts have not been published yet. The first release enables BTC, BCH, and LTC by default, subject to the full effective-capability intersection and seller configuration.
Before adopting a release
- Confirm the repository, version, publication date, and artifact integrity.
- Read breaking changes, migrations, capability changes, and known issues.
- Test backup and rollback procedures in an environment representative of production.
Documentation release gate
Node and Unified tag workflows verify that a versioned release note exists, required public guidance is reachable, and the documentation source manifest reviews the exact commit being tagged. A tag must not create a release while its public instructions still describe a different source revision.
This gate establishes documentation readiness; it does not replace tests, artifact provenance, signatures, SBOM review, migration validation, or runtime capability checks.