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 · Vesu Protocol (Pragma Oracle Malfunction — September 2026)
- Sequence
- #3
- Score
- 62 → 51 (-11)
- Cluster
- mainnet-beta
- Slot
- 462055358
- Off-chain at
- 2026-10-27T11:34:18.937Z
- Anchored at
- 2026-10-27T11:34:39.000Z
- Block time
- 2026-10-27T11:34:39.000Z
Independent verification
- 1. Database (off-chain)
- 2n3HbZw9KGNz2QHSBTxQ8RBiqL3oQc9v6aUQXWT88Gs4
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1587 chars)
{"actor":"judge","artifact_identity":"c6552cfbf4141e97b4c11fc5351ca235","band_override":null,"decided_at":"2026-10-27T11:34:18.350Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2667,"investigation_id":"247c355e-1ef8-4e1d-abb9-8f99f961ab83","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":51,"page_slug":"vesu-protocol-pragma-oracle-malfunction-september-2026","prev_score":62,"reason":"Of 15 claim findings, 2 were disputed (claim_findings[2], [6]) and 2 could not be verified (claim_findings[11], [13]), so about 27% were disputed or unverified. That falls in the minor-issues band. The core incident narrative, loss figures, root cause and recovery amounts match the Pragma and Vesu primary sources. The errors are a wrong pricing date for the 95% recovery figure (September 13 instead of September 11), a multisig migration and publisher activation misdated to September 15, a borrower refund description that leaves out the required Discord ticket, an Aave comparison that misstates the cause, and a source archive link that points to an unrelated article. The Nostra section is unchecked, and the reviewer's confidence of 0.7 is moderate. No status change is warranted.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-11,"score_limit":{"applied":-11,"limited":true,"proposed":-12,"rule":"limited_no_second_opinion","second":null},"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}