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_approve · Sonne Finance
- Sequence
- #3
- Score
- 10 → 52 (+42)
- Cluster
- mainnet-beta
- Slot
- 426700991
- Off-chain at
- 2026-06-15T19:50:05.778Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- C55ikLT611TjEZrexo6gneaYvi4qMcFjhNePA4Mz8KBN
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1095 chars)
{"actor":"judge","decided_at":"2026-06-15T19:50:05.578Z","decision":"review_approve","investigation_id":"46071ba8-e931-4806-addc-c35517a188ae","new_score":52,"page_slug":"sonne-finance","prev_score":10,"reason":"The reviewer examined 18 claims and found zero disputed. Fifteen claims are fully confirmed by Tier 1 sources including CertiK, Halborn, The Record, and CoinDesk; two claims are partially supported (the '2.3 million SONNE votes' figure in claim_findings[9] and the May 12 preparatory transaction date in claim_findings[11]) where the core facts hold but specific figures lack independent corroboration. One citation returned 403 (The Block), consistent with bot-protection rather than true link rot. The one high-priority coverage gap — that yAudit pre-flagged this exact attack vector before the exploit — is an omission that warrants expansion but does not dispute any published claim. The page is factually sound and approved as written.","score_delta":42,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}