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 · Seamless Protocol
- Sequence
- #3
- Score
- 50 → 50 (0)
- Cluster
- mainnet-beta
- Slot
- 462173044
- Off-chain at
- 2026-10-27T18:31:20.539Z
- Anchored at
- 2026-10-27T18:31:53.000Z
- Block time
- 2026-10-27T18:31:53.000Z
Independent verification
- 1. Database (off-chain)
- Qm5XKwjyKLBixotmKDgw9swZbtan2nf3SEktteLRZ7t
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1429 chars)
{"actor":"reviewer","artifact_identity":"dce922f708a3a1496e137d7c61084c76","blocked_count":2,"decided_at":"2026-10-27T18:31:20.428Z","decision":"review","disputed_pct":0.4118,"findings_hash":"3MxT8xeFm2ghrrSidh9kJx155xo1c73JeBZsKsgedQym","investigation_id":"f30b7146-2df0-4463-ab88-8f51152a077f","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":50,"omissions":{"material":1,"total":2},"page_content_hash":"3a4f49bf0edd98386b2b54182c4342ec456da26581cd9d9cbc53da3aef664c74","page_slug":"seamless-protocol","prev_score":50,"reason":"The core narrative (Base Aave v3 fork, wind-down announced in April 2026 for commercial reasons, UI offline around end of June or July 1) is supported. Two date errors are fixable: the announcement was April 7, not April 8, and the SEAM listing was December 11, not December 10. The TVL sentence is internally inconsistent. The verbatim official quote was not found in the cited sources. The page misses the Resolv-related bad debt in the Seamless USDC Morpho vault and the passage of SIP-51, and its no-incident framing is incomplete.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":17,"sequence_num":3,"subject_status":"shut_down","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}