Home Concept How it works Contact DE ES PT FR RU ZH

Verify authenticity

The ALD genesis manifest is signed with an Ed25519 key. You can verify its authenticity yourself in three steps — without trusting us, without a server, without an account.

Genesis identity

Address: ald1jrrvknsy0r8kllg280elfzqarfk8lerr
Public key: 6d7492d9046a466dcfb920285109e731096d46d7be702bb311b66f807f6b96a8
Curve: Ed25519 (RFC 8032)
Hash algorithm: BLAKE2b-256
Signature algorithm: Ed25519 (EdDSA)

Public files

These files are openly available. Anyone can download and inspect them.

MANIFEST.mdThe official statement — founders' commitments MANIFEST.sigDetached Ed25519 signature (human-readable) manifest_envelope.jsonMachine-readable wrapper for verifiers genesis_public_key.txtPublic key — safe to share genesis_address.txtALD address derived from public key verify_manifest.pyPython script for local verification (v0/v1/--all) CHANGELOG.mdAudit trail v0 → v1 (why, when, what) PUBLIC_ANCHOR.mdPublicly shareable hash summary

Historical version (v0): MANIFEST_v0.md · MANIFEST_v0.sig · manifest_envelope_v0.json

Manifest history — both versions verifiable

On 2026-05-28 the manifest was revised once (placeholder fix on line 9). Both versions are documented and signed by the identical Genesis Wallet. Full rationale: CHANGELOG.md.

Version	Status	Hash (BLAKE2b)
v1	current	49b44aeb1fa00978…2f6ce9a
v0	historical, superseded	5baa2d3954093e34…62ad313e

$ python3 verify_manifest.py --all
✅ v0 (historical): AUTHENTIC
✅ v1 (current):    AUTHENTIC
  Both versions were signed by the IDENTICAL Genesis Wallet.

You can verify each version separately (--version v0 or --version v1) or together (--all).

Public anchoring — like PGP keyservers

So that no one (not even we) can change the hash later, it is anchored on multiple independent public stores:

OpenTimestamps — the hash is anchored in the Bitcoin blockchain (mathematically immutable)
GitHub repository (live since 2026-05-28): github.com/pronin2025/ald-aladin-token-genesis-public- — audit log documents every commit
IPFS — content addressing: address = hash, change = different address
Internet Archive / Wayback Machine — permanent snapshots
PUBLIC_ANCHOR.md on Twitter/Telegram/Reddit — distributed visibility

If the hash on any one of these mirrors ever differs from what is shown here, then that mirror is tampered, not the real hash. Majority-truth of the other mirrors wins.

Full instructions: ANCHOR_INSTRUCTIONS.md

Verify it in 3 steps

Recompute the BLAKE2b hash of the manifest

Download MANIFEST.md and manifest_envelope.json. Recompute the hash and compare it to manifest_hash_hex in the envelope.

$ python3 -c "import hashlib; print(hashlib.blake2b(open('MANIFEST.md','rb').read(), digest_size=32).hexdigest())"
49b44aeb1fa00978e3f7498da8f58e2dcaddbd7c315e48f47468b139a2f6ce9a

If they match, the manifest is unmodified.

Verify the Ed25519 signature

Using the public key and the signed payload, you can validate the signature without any input from us. Requirement: Python package cryptography.

$ python3 verify_manifest.py

The script reads the files from the current genesis/ directory, recomputes the hash, verifies the Ed25519 signature, and derives the address from the public key. Three check marks = authentic.

Derive the address from the public key

The genesis address can only be produced from the public key shown above. The script verifies that BLAKE2b(pub, 20 bytes) base32-encoded equals the address ald1jrrvknsy0r8kllg280elfzqarfk8lerr.

Whoever holds the private key is the only entity authorized to sign future official ALD announcements.

QR code for mobile verification

Phase 1 note. This page documents the authenticity anchor. A browser-native live verification widget (JavaScript) is planned for Phase 2. Until then: run the Python script locally, or compare the hash manually.