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 · Polycule
- Sequence
- #4
- Score
- 45 → 45 (0)
- Cluster
- mainnet-beta
- Slot
- 462280654
- Off-chain at
- 2026-10-28T00:53:50.080Z
- Anchored at
- 2026-10-28T00:54:00.000Z
- Block time
- 2026-10-28T00:54:00.000Z
Independent verification
- 1. Database (off-chain)
- 6v2D7yN3tVXwaEBgfamYWjrNgW8mq32P1HxGqie2zUip
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1459 chars)
{"actor":"judge","artifact_identity":"345b4d109c5fc9e57ab343061d819d61","band_override":null,"decided_at":"2026-10-28T00:53:49.821Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.375,"investigation_id":"cab37a98-f0d8-4275-8952-7a793b1b5998","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":45,"page_slug":"polycule","prev_score":45,"reason":"Three of eight checked claims (37.5%) were disputed or could not be verified, which puts the page in the significant-issues band. The summary says ZachXBT flagged the entity (claim_findings[0], disputed) and the timeline repeats it (claim_findings[1], no source found), although the page body concedes this is unconfirmed. The $57M market cap figure conflicts with the $22.8M figure elsewhere on the page (claim_findings[5], partially supported), and the post-hack price move could not be reproduced (claim_findings[6]). The core facts (the AllianceDAO seed, the PMX rebrand surge, the roughly $230K hack and the team's silence) were confirmed, and the reviewer's confidence was moderate-to-low, so the penalty is set in the lower part of the band. Coverage gaps remain on primary sources and post-January 2026 status.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}