Bitdax Trust
TrustLedger
Tamper-evident proof registry for document hashes, timestamps and audit records.
Status and availability
Concept- What is available today
- Architecture documented. Proof anchoring not yet operational.
- Regulatory approvals required
- Communications Authority of KenyaApplication in preparation
Bitdax is preparing an application for accreditation as an Electronic Certification Service Provider with the Communications Authority of Kenya. No accreditation has been granted. Trust services are demonstrated in a controlled environment only.
Bitdax publishes the status of every service. A working interface is not evidence of an approval. See the regulatory status page for the full register.
Capabilities
What it does
Hash-only records
Only a hash, identifier or minimal proof is stored — never a personal document.
Tamper evidence
Any change to a recorded document becomes detectable.
Timestamped events
Credential issuance, revocation and verification events carry a time proof.
Independent checking
A third party can confirm a record existed at a point in time.
Audit export
Produce a defensible chain of events for an auditor or regulator.
Selective anchoring
Anchor only where a proof requirement justifies it.
How it works
The flow, end to end
Event occurs
A credential is issued, revoked, or a document is signed.
Hash computed
A cryptographic hash of the record is computed locally.
Proof recorded
The hash and metadata are written to the proof registry.
Anchor written
Where justified, a minimal proof is anchored externally.
Verifiable later
Anyone holding the original can prove it is unchanged.