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 · Seamless Protocol
- Sequence
- #4
- Score
- 50 → 50 (0)
- Cluster
- mainnet-beta
- Slot
- 462173049
- Off-chain at
- 2026-10-27T18:31:21.024Z
- Anchored at
- 2026-10-27T18:31:54.000Z
- Block time
- 2026-10-27T18:31:54.000Z
Independent verification
- 1. Database (off-chain)
- 7uCS4rrpfmRG5jugHWukfd5RAfAAZ2Ey5KTKTzjvX62X
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1900 chars)
{"actor":"judge","artifact_identity":"dce922f708a3a1496e137d7c61084c76","band_override":null,"blocked_count":2,"decided_at":"2026-10-27T18:31:20.428Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4118,"investigation_id":"f30b7146-2df0-4463-ab88-8f51152a077f","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":50,"page_slug":"seamless-protocol","prev_score":50,"reason":"Of 17 countable claim findings (two were blocked by the source and are left out), 7 were disputed or unverifiable, about 41%, which falls in the significant band. Five disputes are one-day date errors (the announcement was April 7, not April 8, in claim_findings[0-2]; the SEAM listing was December 11, not December 10, in claim_findings[3-4]), and the verbatim official quote was not found in the cited sources (claim_findings[7]). More seriously, the page omits the 381,904 USDC vault bad debt tied to the Resolv exploit and frames the wind-down as orderly with no incidents (omission_findings[0], claim_findings[10-12]). The TVL sentence is internally inconsistent and needs a manual check, and the page is otherwise supported on the core wind-down narrative, so the penalty sits at the lower end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":17,"sequence_num":4,"severity_override":{"applied":true,"band":"significant","from_band":"significant","reason":"omission_findings[0] is material: the Seamless USDC Morpho vault accrued 381,904 USDC of bad debt from Resolv exposure, which the DAO partly covered, while the page says there were no incidents and the wind-down was orderly. This supports holding the page in the significant band rather than a lower one."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}