Verify a decision
Every moderation decision on AVOID.NET is anchored to the Solana blockchain. You don't have to trust us — you can verify cryptographically that we committed to a verdict at a specific moment and have not rewritten it.
How verification works
- We commit. When a moderator accepts/rejects a submission, we serialize the decision into deterministic UTF-8 bytes (
payload_canonical_string), hash it with SHA-256, encode the digest as base58, and write it to Solana inside an SPL Memo v2 transaction. - We store the bytes. The exact bytes we hashed are stored alongside the decision in our database. Anyone can read them and recompute the hash in any language.
- You compare three values. Database hash, your independently-recomputed hash, and the hash inside the on-chain memo. If all three match, the decision is authentic and timestamped.
The on-chain memo format is
AVOID.NET|v1|h:<b58-sha256>|d:<id>|t:<iso>Find a signature on any investigation page's decision log, or run python -m src.verify_decision --signature <sig> for a CLI check.
Decision
review · Aurum Foundation
- Sequence
- #2
- Score
- 2 → 2 (0)
- Cluster
- mainnet-beta
- Slot
- 443517422
- Off-chain at
- 2026-08-25T22:19:56.085Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 2ThbrxT8qGrRsmQev8JPq7e9MxvBV7dnu8zLmmAdTZpu
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1405 chars)
{"actor":"reviewer","decided_at":"2026-08-25T22:19:55.948Z","decision":"review","investigation_id":"18c63c26-94e9-4cc8-9f89-9ed7c1901d0d","new_score":2,"page_slug":"aurum-foundation","prev_score":2,"reason":"The great majority of the page's claims -- regulatory warning dates, on-chain redistribution figures, the collapse timeline, and the identities/backgrounds of named individuals -- are directly and precisely corroborated by the cited or closely related independent sources. The most notable issues found are: one accusation about Shane Morand's 2018 departure from Organo Gold and its stated cause (a crypto pitch to distributors) that is contradicted by the page's own cited source, which instead describes a 2020/2023 departure for unrelated reasons; a summary claim of 'at least ten' warning jurisdictions when the page's own body documents only nine; a duplicated/mischaracterized timeline entry for a Russian regulatory action; a one-day discrepancy between two of the page's own cited Hong Kong SFC dates; and several SimilarWeb traffic statistics that are accurate but sourced to BehindMLM articles not listed among that section's citations. No fabricated sources, dead links, or claims contradicting more credible current reporting were identified.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}