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_revise · M2 Exchange
- Sequence
- #5
- Score
- 51 → 51 (0)
- Cluster
- mainnet-beta
- Slot
- 464273723
- Off-chain at
- 2026-11-01T23:16:51.316Z
- Anchored at
- 2026-11-01T23:17:14.000Z
- Block time
- 2026-11-01T23:17:14.000Z
Independent verification
- 1. Database (off-chain)
- DTDhN4pBDE1oiJPgsCUC7XBeapTydAbZNt4pUHkGMCNF
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1347 chars)
{"actor":"judge","artifact_identity":"1c6e5aea75725cb42379c5e54f52b275","band_override":null,"decided_at":"2026-11-01T23:16:51.053Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2,"investigation_id":"26bce48e-5acc-4bbb-a451-cca47010ca11","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":51,"page_slug":"m2-exchange","prev_score":51,"reason":"Of 5 claims checked, 1 (20%) could not be verified: claim_findings[2], the statement that Cyvers and ZachXBT first detected the breach, was not found in the sources read, and ZachXBT appears in neither. Two more claims were only partly supported. claim_findings[0] says QuillAudits noted MFA and multi-sig were absent, but the source only recommends them. claim_findings[4] likely has the wrong month for the CEO change. The core incident figures (about $13.7M, assets, ADGM permission in August 2023) were confirmed. No shutdown, sanction or omission was found. The reviewer's confidence is low (0.5) and several cited sources were inaccessible, so the penalty is kept at the lower end of the minor band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}