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 · Virtuals Protocol
- Sequence
- #4
- Score
- 74 → 74 (0)
- Cluster
- mainnet-beta
- Slot
- 462178449
- Off-chain at
- 2026-10-27T18:50:42.609Z
- Anchored at
- 2026-10-27T18:50:57.000Z
- Block time
- 2026-10-27T18:50:57.000Z
Independent verification
- 1. Database (off-chain)
- cNbL99KwuzdQwg2ZwrCRb6JGs5YwuqujK265SpWFkqe
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1336 chars)
{"actor":"judge","artifact_identity":"fb0e5d479703babed1a11566d6d14a7b","band_override":null,"decided_at":"2026-10-27T18:50:42.283Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2,"investigation_id":"43ef5152-8fbd-44ce-a088-ae1f4a26d5cd","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":74,"page_slug":"virtuals-protocol","prev_score":74,"reason":"Of five claims reviewed, three were confirmed by Tier 2 sources (claim_findings[0], [1], [2]), one was partly supported (claim_findings[3]: the patch and bounty plan are confirmed, but the researcher name, date and technical details were not visible in the cited source), and one origin and funding claim was not checked in this pass (claim_findings[4], not_found). That puts the unverified share at 20%, in the minor-issues band. No claim was contradicted, the subject is still operating, and the only omission (2026 expansion) is minor. The penalty is kept at the low end because reviewer confidence is moderate (0.55) and the unchecked claim is one the page already hedges as reported.","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}