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
- Sequence
- #2
- Score
- 10 → 10 (0)
- Cluster
- mainnet-beta
- Slot
- 462055364
- Off-chain at
- 2026-10-27T11:34:30.120Z
- Anchored at
- 2026-10-27T11:34:40.000Z
- Block time
- 2026-10-27T11:34:40.000Z
Independent verification
- 1. Database (off-chain)
- Et2RLLw6fQ458yedX9sfFjjBqv42r95jjwrs3oZrBYXy
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1352 chars)
{"actor":"reviewer","artifact_identity":"178fafd05121d7b22b93b15fedb8523b","decided_at":"2026-10-27T11:34:29.700Z","decision":"review","disputed_pct":0.3333,"findings_hash":"DLkeYiy3U23g5PVgz8tFrKs6EMA8Kj6zwWaexgupVCW5","investigation_id":"7765bf42-3a60-4115-9b3d-61f5bf49a1ce","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":10,"omissions":{"material":2,"total":3},"page_content_hash":"4db467072adca988c0a3398be6149e26cc1206e7c55f616e719c3363b5bafdfc","page_slug":"dcent-app-wallet-exploit-september-2026","prev_score":10,"reason":"The core incident facts and the Crypto Basic on-chain timeline match their sources. The page has a self-contradictory timeline entry on version 8.1.0, attributes the 10.0.0 patch to a report that does not name it, and lists law enforcement involvement as unconfirmed although DCENT's report states it. The loss and date scope is out of date: reporting through Sept 25 shows about 12.4M XRP drained over about 10 days. Four sources_used archive URLs point to unrelated pages.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":2,"subject_status":"exploited","subject_status_contradicts_page":true,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}