Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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 · Flying Tulip
View on Solana ↗
Sequence
#10
Score
72 → 72 (0)
Cluster
mainnet-beta
Slot
471295589
Off-chain at
2026-11-19T10:03:51.708Z
Anchored at
2026-11-19T10:03:59.000Z
Block time
2026-11-19T10:03:59.000Z

Independent verification

1. Database (off-chain)
85DkPJc9D7R45eSaNkJwrGhb7r3hrw5wmCa6tPitm321
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1445 chars)
{"actor":"judge","artifact_identity":"88540f2892be32d2b285994d81f9e972","band_override":null,"decided_at":"2026-11-19T10:03:51.870Z","decision":"review_approve","delist_requested":false,"disputed_pct":0.0313,"investigation_id":"1d5754e9-8a31-4384-a46f-e2f13b4d653b","judge_def_hash":"23facbd253d9791a0f76ed4171330b75d7080c45235d46c5c7a83b4502acc290","new_score":72,"page_slug":"flying-tulip","prev_score":72,"reason":"27 of 29 checked claims were fully confirmed by independent sources. One finding (claim_findings[22]) is partially supported — a minor rounding difference in circulating supply (page states ~483M FT, CoinGecko shows ~480M at time of review), and one (claim_findings[28]) is unverifiable due to lack of historical price data for a past date, not a source refusal. This yields a disputed/unverifiable rate of approximately 6.9%, placing the page in the 0–10% approval band. Subject status confirms the protocol is actively operating as of November 2026 with no contradictions to page content. All three omission findings are rated minor and do not alter the band. The one high-priority coverage gap (independent on-chain verification of PUT reserve backing) is a recommended expansion, not a defect.","reviewer_def_hash":"0ab16d28840cf555a9c931564bdbc96f6c68d1b1eaf9d89506afaeb2c143b050","score_delta":0,"sequence_num":10,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}