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 · 8ightDAO
- Sequence
- #3
- Score
- 18 → 3 (-15)
- Cluster
- mainnet-beta
- Slot
- 462279903
- Off-chain at
- 2026-10-28T00:50:58.115Z
- Anchored at
- 2026-10-28T00:51:18.000Z
- Block time
- 2026-10-28T00:51:18.000Z
Independent verification
- 1. Database (off-chain)
- DTbeK95dgvoNAFjnRzTz1PaPdU37JnLzKGcSExW3BZuH
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1756 chars)
{"actor":"judge","artifact_identity":"47215cdeb726477dc11cf15b82198155","band_override":null,"blocked_count":1,"decided_at":"2026-10-28T00:50:57.917Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3,"investigation_id":"cb6dbc1b-c466-4a62-b24b-9e33ac816240","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":3,"page_slug":"8ightdao","prev_score":18,"reason":"The core incident is well supported: the roughly $1.75M treasury loss, the keys shared over Facebook and Google Drive, the missing multisig, and the two-option recovery plan are confirmed by rekt.news and CoinCodeCap (claim_findings[0], [1], [5], [8], [9]). Of 10 countable findings (one blocked-source finding excluded), 3 are unverifiable (launch and Snowdog framing with a dead fullycrypto.com citation, the ZachXBT mention, the intermediate-address claim), giving 30%, the top of the minor band. Two further claims overstate their sources: the 'serial fraud pattern' framing turns rekt.news's conditional speculation into a noted pattern (claim_findings[7]), and the Tornado Cash 'all funds' and chain detail is only partly confirmed (claim_findings[2]). The price-drop figures could not be checked because the source was blocked, which is a coverage limit rather than a defect. The only omission is minor and the page's past tense is consistent with the project being deprecated, so the penalty sits at the upper end of the minor band without moving to the significant band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-15,"scored_claims":10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}