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 · Sturdy V1
- Sequence
- #7
- Score
- 54 → 54 (0)
- Cluster
- mainnet-beta
- Slot
- 462907795
- Off-chain at
- 2026-10-29T14:03:22.737Z
- Anchored at
- 2026-10-29T14:03:47.000Z
- Block time
- 2026-10-29T14:03:47.000Z
Independent verification
- 1. Database (off-chain)
- ETAycQWuYPiDe2pVKx1xCBWLJ2bfp9dd39cncFSNrgFb
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1308 chars)
{"actor":"reviewer","artifact_identity":"f8a8a8b4d6170775467c158f388cef23","blocked_count":1,"decided_at":"2026-10-29T14:03:22.614Z","decision":"review","disputed_pct":0,"findings_hash":"FVRZ38smV9DGeLctetWMZKzs85zxNFPNS6FAK21htLd4","investigation_id":"299815f1-eacc-4b93-ab24-10d1c6de9f95","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":54,"page_content_hash":"03e2134e3cb2e36dafd90744f0e0ac6a2c543ad2ca2f06e5058ad60bcdccb80e","page_slug":"sturdy-v1","prev_score":54,"reason":"The funding and exploit claims I checked match the sources: $3.9M seed in March 2022, June 12 2023 read-only reentrancy exploit, 442 ETH / about $800K, Tornado Cash laundering, and the audit-scope note. The sunset-proposal claims could not be read because the governance forum was unreachable. The regulatory section cites a 2023 newsletter that does not address regulation. The $884K / 504 ETH figure was not verified. No shutdown or sanction contradicts the page.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":6,"sequence_num":7,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}