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_revise · Flying Tulip
- Sequence
- #4
- Score
- 69 → 69 (0)
- Cluster
- mainnet-beta
- Slot
- 462187896
- Off-chain at
- 2026-10-27T19:24:16.076Z
- Anchored at
- 2026-10-27T19:24:25.000Z
- Block time
- 2026-10-27T19:24:25.000Z
Independent verification
- 1. Database (off-chain)
- EB4u2E1aAYXoQG8fdP3eK57WEzDG9MTVeyZbhCGYzFHh
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1852 chars)
{"actor":"judge","artifact_identity":"678154d3daa28904dd3113d33baa20fb","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T19:24:15.733Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.375,"investigation_id":"1d5754e9-8a31-4384-a46f-e2f13b4d653b","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":69,"page_slug":"flying-tulip","prev_score":69,"reason":"Excluding the one source_blocked finding (claim_findings[8], OFAC), 3 of 8 claims were disputed or unverifiable (37.5%), which falls in the significant band. claim_findings[0] shows the Sonic board resignation dated 2026-06-01 when the source points to about June 19-20, and claim_findings[3] found no support for the $275M total fundraising figure, which does not match the page's own $200M plus $25.5M. claim_findings[7] (Cronje's 2022 statement) could not be sourced, and claim_findings[6] shows the $2.2M TVL differing sharply from the founder's reported $70M. The core facts (seed round, TGE price dip, Sherlock result) were confirmed and no shutdown, exploit or sanction was found, so the page is revised and not denied.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":8,"sequence_num":4,"severity_override":{"applied":true,"band":"significant","from_band":"significant","reason":"The review reports a material omission (claim_findings do not capture it): the Sonic Labs board exit followed a roughly 97% S token decline and a leadership overhaul, which bears directly on the founder-track-record risk the page discusses. The percentage band is already significant, so the band is held at significant rather than lowered to minor."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}