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 · Orange Finance
- Sequence
- #4
- Score
- 50 → 50 (0)
- Cluster
- mainnet-beta
- Slot
- 464289703
- Off-chain at
- 2026-11-02T00:13:52.133Z
- Anchored at
- 2026-11-02T00:14:09.000Z
- Block time
- 2026-11-02T00:14:09.000Z
Independent verification
- 1. Database (off-chain)
- GDKYof9GgSnZ2oMrUnP1YJArJ41xztu8Ao24M3ou6in9
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1543 chars)
{"actor":"judge","artifact_identity":"6c69ab08c6eee7a2dd4a7ad3187c28e5","band_override":null,"blocked_count":1,"decided_at":"2026-11-02T00:13:51.892Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.375,"investigation_id":"553a92d2-ee3f-4280-ae05-a6e447c45f5c","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":50,"page_slug":"orange-finance","prev_score":50,"reason":"The core exploit facts hold up: the date, the roughly $843,557 loss, the per-DEX breakdown, the attacker address and the single-signature multisig misconfiguration are confirmed by Rekt and Web3 Is Going Great (claim_findings[0-2], [5]). However, 3 of 8 countable claims (37.5%) could not be verified: the ZachXBT flagging claim appears in the summary, a section heading and the timeline but has no supporting source and cites only a generic Telegram channel root (claim_findings[3-4]), and the Stryke '50% of TVL retained' figure was not found (claim_findings[8]). One further claim, the Seal 911 engagement, was excluded because its source blocked the reviewer. The penalty sits at the lighter end of the band because the central allegations are confirmed, the reviewer's confidence is moderate (0.6), and no omissions or status contradictions were reported.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":8,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}