Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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 · Radiant Capital
View on Solana ↗
Sequence
#5
Score
18 → 0 (-18)
Cluster
mainnet-beta
Slot
462042372
Off-chain at
2026-10-27T10:48:16.743Z
Anchored at
2026-10-27T10:48:36.000Z
Block time
2026-10-27T10:48:36.000Z

Independent verification

1. Database (off-chain)
3J5eXBxqQgrQTDo7cAAaCiD6xUBnGUFC7YHob7cz2pNH
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1795 chars)
{"actor":"judge","artifact_identity":"402ce9f4411dc175c87ac4ed14aa32b4","band_override":null,"decided_at":"2026-10-27T10:48:16.349Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3,"investigation_id":"2cf92517-f3d5-4d4e-ad0a-dcf16473b155","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"radiant-capital","prev_score":18,"reason":"Of 10 checked claims, 3 could not be verified (claim_findings[3], [5], [9]) and 1 is stale (claim_findings[7]), giving a disputed share of 30-40%. More importantly, the page does not mention that the Radiant DAO announced a wind-down in June 2026, and its current-status section still describes a V2 relaunch (omission_findings[0], subject_status). The core incident facts are well supported (UNC4736 attribution, the 3-of-11 multisig, Tornado Cash laundering, claim_findings[0], [4], [6]), so the page needs correction and not removal. Two other details also need fixing: the Dec 9 Mandiant attribution date (claim_findings[1]) and the unsourced 'six seconds' detail (claim_findings[2]).","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-18,"score_limit":{"applied":-18,"limited":true,"proposed":-22,"rule":"limited_no_second_opinion","second":null},"sequence_num":5,"severity_override":{"applied":true,"band":"significant","from_band":"significant","reason":"The review reports a critical omission (June 2026 DAO wind-down, omission_findings[0]) and subject_status.contradicts_page is true. The page presents the protocol as active with a V2 relaunch, so the percentage band is held at significant and not lowered."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}