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 · Rhea Finance
- Sequence
- #3
- Score
- 54 → 54 (0)
- Cluster
- mainnet-beta
- Slot
- 464345283
- Off-chain at
- 2026-11-02T03:32:21.071Z
- Anchored at
- 2026-11-02T03:32:43.000Z
- Block time
- 2026-11-02T03:32:43.000Z
Independent verification
- 1. Database (off-chain)
- GeQq8ofohzCFQYCL7EyisEbRWGYki5z2ycHF8Ft2Ks6t
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1321 chars)
{"actor":"reviewer","artifact_identity":"6ac2c0691c8ab3d16dccab38f5cb23b9","blocked_count":1,"decided_at":"2026-11-02T03:32:21.021Z","decision":"review","disputed_pct":0.4286,"findings_hash":"FpeiFXN36B7DajDaAUV7oWrqmFnnhNV6vyjbWzuW4L9x","investigation_id":"75e439fb-33ad-4ea1-b87d-51dc3e5ec7f7","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":54,"omissions":{"material":2,"total":2},"page_content_hash":"8912f326925599d9ae71e58af0323b1e35b0cdb878f208af05b1c2a1bc49df61","page_slug":"rhea-finance","prev_score":54,"reason":"The exploit narrative (date, 18.4M loss, root cause, attacker preparation) is well supported by The Block and Coin Edition. The recovery section and summary are stale or inconsistent: the 9.2M figure differs across sources, the outstanding balance is shown as large when later reporting puts it near 0.4M with a coverage pledge, and the page omits the margin product shutdown and DEX reopening. One timeline date appears off by a day.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":7,"sequence_num":3,"subject_status":"operating","subject_status_contradicts_page":true,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}