Checked October 24, 2026
Evidence you can inspect.
Limits you should know.
The current public release is a testnet candidate. Download integrity, a working dashboard and a security assessment are different kinds of evidence.
Published release material
- v0.9.1718-rc release notesPublished October 24, 2026. Network 20574, node 0.9.1718, commit 83ad3dd9. Includes setup, transition, validation and troubleshooting instructions.
- Published SHA-256 checksumsCompare the binary, configuration and client-tool downloads with the publisher's manifest. Matching a checksum checks integrity against that manifest, not the safety of the software.
- Versioned agent and API guideDocuments signed transactions, discovery, service workflows and governance. The downloaded guide was checked against its published checksum for this website update.
- Python client SDKClient tooling only, not the node or consensus source. Verify before installing and use the testnet chain ID explicitly.
A real testnet interface
The homepage demonstration uses dashboard screenshots and selected public API responses captured from a node running this release on October 24. No wallet/admin access or state-changing requests were used for the capture.
These are recorded snapshots, not a live status feed. Their heights, peer counts and timings describe that capture, not today's network state or future performance.
Current limitations
Source and independent review
The repository states that the node and consensus source are not public yet and will open after mainnet has been live for a while. Prebuilt binaries are the supported distribution today.
This page does not present an independent audit report, a reproducible node-build proof, a verified full-suite test count or a claim of zero unresolved vulnerabilities. Those claims need dated, release-specific supporting reports.
Performance and formal methods
Batch transaction validation is not sustained network throughput. A meaningful TPS result needs a workload, hardware, node count, duration and finality criterion.
No release-specific reproducible benchmark or formal-verification report is linked here. Counts and performance figures in the older whitepaper are design-era references, not a qualification of this candidate.
Implemented signing is not a roadmap promise.
The current client guide specifies ECDSA with secp256k1 for signatures. A SHA3-256 hash function or a possible post-quantum upgrade does not by itself make the current signing system quantum-resistant.
Post-quantum signing is not claimed as active by this site. Judge supported algorithms against the release you actually run.
Readiness remains a test program.
The official candidate describes a 14-day soak. That is a plan to gather operational evidence, not proof that mainnet is ready or that the soak has finished cleanly. The launch page separates the target date from the announcement still to come.
To report a suspected vulnerability, contact Atlas privately. Share only the minimum information needed, and never send wallet passwords or private keys.