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 · SingularityNET
- Sequence
- #3
- Score
- 26 → 26 (0)
- Cluster
- mainnet-beta
- Slot
- 462184703
- Off-chain at
- 2026-10-27T19:12:33.769Z
- Anchored at
- 2026-10-27T19:13:05.000Z
- Block time
- 2026-10-27T19:13:05.000Z
Independent verification
- 1. Database (off-chain)
- D36JUzmZZ3Ln5Ca8YWoLNtEBpTMHTptAiEaz8bQumsSm
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1317 chars)
{"actor":"reviewer","artifact_identity":"88c71bb3196a597178377c320c2a3917","decided_at":"2026-10-27T19:12:33.637Z","decision":"review","disputed_pct":0.25,"findings_hash":"6ZjJ9Z9HgUbGihN46PiRWtfnxSDSEkn6VSZxsWsvzrbP","investigation_id":"f8c9cadf-e1e8-4696-b4d2-3f487a0ef174","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"omissions":{"material":1,"total":1},"page_content_hash":"b2ddc1f712f7df52698e34966869964450cdea4da7a9d2ddba30781663580c63","page_slug":"singularitynet","prev_score":26,"reason":"The core incident narrative (key-compromise exploit of the SingularityNET and Fetch.ai bridge, 260M AGIX and 53.8M WMTx minted, $16.77M attacker holdings, Sept 19-21) is consistent with the sources checked. Several specifics are not in the cited article: the 20:21 UTC time, the Bitquery 48-hour claim, the ninth-exploit and $345M figure, and the $2.25M 'through token sales' wording. One archive URL points to an unrelated article. The page is stale after Sept 21.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}