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 · Orange Finance
- Sequence
- #3
- Score
- 50 → 50 (0)
- Cluster
- mainnet-beta
- Slot
- 464289698
- Off-chain at
- 2026-11-02T00:13:51.965Z
- Anchored at
- 2026-11-02T00:14:08.000Z
- Block time
- 2026-11-02T00:14:08.000Z
Independent verification
- 1. Database (off-chain)
- 98ugADnPDBRYf4MDyuewkBx9h1i3ubVeV65eQemA1Wzc
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1296 chars)
{"actor":"reviewer","artifact_identity":"6c69ab08c6eee7a2dd4a7ad3187c28e5","blocked_count":1,"decided_at":"2026-11-02T00:13:51.892Z","decision":"review","disputed_pct":0.375,"findings_hash":"18CKxpLbbQHcBZaSqnUWkFYPUpz3ox1yCPrBbqi6Jdu","investigation_id":"553a92d2-ee3f-4280-ae05-a6e447c45f5c","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":50,"page_content_hash":"edac48a0582902244e1ea6bc6c9c0267bebdcf6031cd8f490bd68101092587b9","page_slug":"orange-finance","prev_score":50,"reason":"The core exploit facts (date, total loss, per-DEX breakdown, loss categories, attacker address, single-signature multisig, Stargate exit, white-hat message) are supported by Rekt and Web3 Is Going Great. The ZachXBT flagging claim, which appears in the summary and a section heading, has no supporting source and cites only a generic Telegram channel root. The Seal 911 and Stryke 50% claims were not verified. Timeline entries carry no sources.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":8,"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}