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 · Cetus CLMM
- Sequence
- #3
- Score
- 55 → 55 (0)
- Cluster
- mainnet-beta
- Slot
- 464445901
- Off-chain at
- 2026-11-02T09:31:41.976Z
- Anchored at
- 2026-11-02T09:31:51.000Z
- Block time
- 2026-11-02T09:31:51.000Z
Independent verification
- 1. Database (off-chain)
- 8vGPYZKUdHXh621zmSJuAdYG5HMX4nsc1byWCZyrzz8A
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1452 chars)
{"actor":"reviewer","artifact_identity":"6e1fee4ba977b33e91c3c59923f49985","blocked_count":2,"decided_at":"2026-11-02T09:31:41.923Z","decision":"review","disputed_pct":0.3333,"findings_hash":"81TwutC1Cm1MnC3D5niZpD5x6525ffGRbJrhFkuvYW8p","investigation_id":"cc1ddaee-d8b6-435b-9531-c78d1fdcd65c","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":55,"omissions":{"material":0,"total":1},"page_content_hash":"12436ffb9e0798688a855cb18893911654e492817bcb4d70b608df2cc6a05303","page_slug":"cetus-clmm","prev_score":55,"reason":"The core narrative holds: the overflow root cause, the $223M loss, the $162M freeze, the 90.9% vote, the multisig composition, the June 8 relaunch and the ZachXBT/Circle details match the sources I fetched. The main error is the vote schedule: Sui's own post gives a June 3 deadline and a May 27 start, so 'scheduled deadline on May 29' and the May 26 proposal date are wrong. Some specifics (10:30 UTC, the 15%/5%/10% compensation split, the 50% TVL restoration) could not be checked because sources were blocked or silent. Cetus is still operating as of mid-2026.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":12,"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}