Transparency
What a2ally is running
Last updated
TL;DR: Shows the exact commit and build a2ally is running, its signing keys and its deploy history; every deploy and rule change is sealed on the ledger.
Running now
- Version: 0.5.2
- Git commit: 2be7a86
- Build hash: b6bd74504de6ac3870c3e95f0c65c0acd2946257062d57294b7d8ce4db69852c (351 files)
- Witness kit SHA-256: 5ef2c53e30c927a3d7ef034375aedab7b989eace613a475fd0b943624c7682c5
- Mirror kit SHA-256: 6873528778d48edfa38f94126156d218d89746cbacfc6026018ca8657a28f955
- Offline drill script SHA-256: b1ce62e6a331f0f969cbea1c1afe74d38a33fc850a2384040c863b0aae0b856f
- Signing keys: https://www.a2ally.com/.well-known/a2ally-keys.json
Deploy history
- 2026-11-06T23:58:43.424Z · commit 2be7a86 · build b6bd74504de6ac38
- 2026-11-06T22:14:47.895Z · commit a26174a · build bf91846d204a44b9
How to check
Machine-readable: https://www.a2ally.com/v1/transparency/build. Rule changes and the 7-day waiting period: https://www.a2ally.com/transparency/changes. Verify signatures, receipts and ledger anchors offline: https://www.a2ally.com/witness/verify.
What this does not prove yet
These values are reported by the running service itself. Until builds are reproducible from a public source and attested by hardware (roadmap), a reader can check consistency over time — keys, commit and build history — but cannot independently prove the server runs exactly this code.
Frequently asked questions
How do I know which code a2ally is running?
This page and /v1/transparency/build report the deployed commit and build hash, and each deploy is recorded on the ledger.
Can a2ally change its rules overnight?
No. Changes to grading, arbitration, pricing or policy rules are announced at /transparency/changes and wait 7 days before taking effect; production refuses to boot with a rule change that skips the wait.