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.

Sequence
#4
Score
26 → 26 (0)
Cluster
mainnet-beta
Slot
464278033
Off-chain at
2026-11-01T23:32:24.068Z
Anchored at
2026-11-01T23:32:37.000Z
Block time
2026-11-01T23:32:37.000Z

Independent verification

1. Database (off-chain)
D8FGdJjFEKs429RjraSbbkTe12nN3YCZ28Bhiv6EPjvP
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2043 chars)
{"actor":"judge","artifact_identity":"53e13126461619d5a516de6a59da1aaa","band_override":null,"blocked_count":1,"decided_at":"2026-11-01T23:32:23.792Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.0833,"investigation_id":"f570804d-ea6e-44c3-b89f-30c13bf29d21","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"page_slug":"tartswap-tart-solana-mint-6mxygsp9qdjieqgcuhjbsru6vu1ymtyndwntsx6uwbtv","prev_score":26,"reason":"The identity-confusion section, the BNB Chain whitepaper claims and the Hokanews summary were confirmed (claim_findings[0], [1], [2]). The RugCheck section is out of date: the score is now 67 rather than 54, and the holder data the page called an empty anomaly is now populated (claim_findings[5], [6], [8]). That data shows one wallet holding about 99.66% of supply, which the page leaves out (omission_findings[0], critical). The DexScreener volume figures could not be checked because the source blocked the reviewer, so that is a coverage limit and not a defect of the page. The reviewer's confidence was moderate (0.6) and found no shutdown or exploit, so the penalty is set in the middle of the significant band and the page is not denied.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":12,"sequence_num":4,"severity_override":{"applied":true,"band":"significant","from_band":"approve","reason":"omission_findings[0] is critical: the current RugCheck report shows one wallet holding about 99.66% of supply (34 holders, top 10 over 70%), while the page calls the holder data an empty anomaly. Counting the three stale findings as disputed gives about 33% (4 of 12, one source-blocked finding excluded), which is already the significant band. Even on a narrower count that excludes stale findings, the critical omission would put the page in the significant band."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}