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.
- Sequence
- #2
- Score
- 30 → 30 (0)
- Cluster
- mainnet-beta
- Slot
- 464352401
- Off-chain at
- 2026-11-02T03:57:44.416Z
- Anchored at
- 2026-11-02T03:58:11.000Z
- Block time
- 2026-11-02T03:58:11.000Z
Independent verification
- 1. Database (off-chain)
- FHoZgPARW1cZiShjM3vEDGUctDs7xXcurSopdN5r3CyQ
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1356 chars)
{"actor":"reviewer","artifact_identity":"9d0c038e5d87d3a8addbbef85cb3cb2c","decided_at":"2026-11-02T03:57:44.356Z","decision":"review","disputed_pct":0.625,"findings_hash":"TMCnEGo2V5y89XP4jr2UiHqkeAwT8stXLp5dKZ6KGdB","investigation_id":"90b40c3c-e5f4-4306-b5dc-a1d036dbe1f0","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":30,"page_content_hash":"219d1f7a5a5ffef78f108d8c1aad5ac64b6f800837a72182da1ed19f8ed5a4ce","page_slug":"revolut-data-breach-fake-government-request-september-2026","prev_score":30,"reason":"The page is broadly consistent with September 2026 reporting on the incident, the ransom demand, the Hudson Rock credential finding and the five-month duration. A material attribution error appears in the summary and Incident Overview: the 680 figure is attributed to Revolut, but Revolut gave only 'limited' and the number came from the actors and press. The Reggio Calabria detail and the ZachXBT claim could not be found in the sources cited for them. Only three of the cited sources were read.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":2,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}