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 · Vulcan Forged
- Sequence
- #4
- Score
- 61 → 61 (0)
- Cluster
- mainnet-beta
- Slot
- 462278803
- Off-chain at
- 2026-10-28T00:46:57.512Z
- Anchored at
- 2026-10-28T00:47:24.000Z
- Block time
- 2026-10-28T00:47:24.000Z
Independent verification
- 1. Database (off-chain)
- EMfu94dHLFbh7UdgfWjyUXpa3jcJZeR7SxBaatq2KZLS
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1480 chars)
{"actor":"judge","artifact_identity":"5409fcd12a2be126a6c429cad7557be2","band_override":null,"blocked_count":2,"decided_at":"2026-10-28T00:46:57.277Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.5,"investigation_id":"176142ef-6cc0-4fd2-9c2f-50b62c6e9fc1","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":61,"page_slug":"vulcan-forged","prev_score":61,"reason":"Of 14 claims reviewed, 2 price-tracker claims could not be checked because the source blocked the reviewer and were left out of the count. Of the remaining 12, 6 (50%) were disputed or could not be verified: the CertiK concentration figure was disputed (claim_findings[6]), the 27.49% audit-coverage figure was not found on the cited page (claim_findings[7]), the page contradicts itself on headquarters, UK versus Greece, with neither supported (claim_findings[3], [4]), and the 2026 website claim and the ZachXBT claim have no supporting source (claim_findings[12], [13]). The core hack facts (96 wallets, 4.5M PYR, $140M, price drop, Series A) were confirmed by Tier 2 sources, so the penalty sits at the lower end of the significant band. No shutdown, sanction or material omission was reported.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":12,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}