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 · Arena SocialFi
- Sequence
- #5
- Score
- 53 → 53 (0)
- Cluster
- mainnet-beta
- Slot
- 464286097
- Off-chain at
- 2026-11-02T00:01:15.716Z
- Anchored at
- 2026-11-02T00:01:19.000Z
- Block time
- 2026-11-02T00:01:19.000Z
Independent verification
- 1. Database (off-chain)
- 3Vkjy9FhvecT1JoSpnMzuKQ3zLsLLjeE7cVDB2A2kRcY
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1400 chars)
{"actor":"judge","artifact_identity":"abe9cc82e2f7dc19d31cd289b416ce1f","band_override":null,"decided_at":"2026-11-02T00:01:15.425Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1429,"investigation_id":"a03fdac3-1e75-4012-a687-39075c822e80","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":53,"page_slug":"arena-socialfi","prev_score":53,"reason":"Of 7 checked claims, none were disputed and 1 could not be verified (claim_findings[5], the unsourced Monad and Google/Apple sign-in timeline entry), giving about 14% unverified. The core account holds: the October 2023 exploit, the roughly 90% bounty recovery (claim_findings[0]) and the 2024 pre-seed round (claim_findings[1]) match Tier 1 sources. Minor issues are the Paladin audit claim cited to a page that does not mention it (claim_findings[2]) and the 96% price drawdown stated without an as-of date or source, against about 97.6% on current data (claim_findings[3], [4]). The reviewer found no shutdown, sanction or later exploit and no omissions, and reviewer confidence was moderate (0.5), so the penalty is kept at the low end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}