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 · Crema Finance
- Sequence
- #3
- Score
- 54 → 54 (0)
- Cluster
- mainnet-beta
- Slot
- 466740488
- Off-chain at
- 2026-11-08T02:04:03.604Z
- Anchored at
- 2026-11-08T02:04:17.000Z
- Block time
- 2026-11-08T02:04:17.000Z
Independent verification
- 1. Database (off-chain)
- 8x6fpo9fUcd7hvqNsCMQq3wU3GS5CPmGBEwfenz3WDvy
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1322 chars)
{"actor":"reviewer","artifact_identity":"bea5a98447ddbb8f049fc5bb39e4d2fe","blocked_count":1,"decided_at":"2026-11-08T02:04:03.562Z","decision":"review","disputed_pct":0.3333,"findings_hash":"6AaqKDfoyKkpeeprSTLC2EP6pqk8qsa2jrREnCHvrwXx","investigation_id":"42a98fcb-c67c-4a73-abf4-ca61dd3c31fe","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":54,"page_content_hash":"0fa6dbb4365dfe1864b5becc30e073d246d0dcc668183f9ed5044035753b5620","page_slug":"crema-finance","prev_score":54,"reason":"The core exploit narrative (date, ~$8.78M, tick-account and Solend flash-loan method, TVL drop, 45,455 SOL bounty kept) is well supported. The recovered-amount figure of $7.1M (and 81%) conflicts with sources reporting about $8M returned. The ZachXBT section and the 'fourth serious breach' remark have no supporting source. Only a sample of claims was checked; the funding, team, compensation and audit details were not independently verified in this time-boxed review.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"scored_claims":6,"sequence_num":3,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}