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.

Decision
review_revise · Opacus
View on Solana ↗
Sequence
#2
Score
35 → 23 (-12)
Cluster
mainnet-beta
Slot
464117052
Off-chain at
2026-11-01T13:57:14.133Z
Anchored at
2026-11-01T13:57:24.000Z
Block time
2026-11-01T13:57:24.000Z

Independent verification

1. Database (off-chain)
82cFp97S2ubQVNu8yd5nsgw33yrYi8zHt5ie9QAPCXjp
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1526 chars)
{"actor":"judge","artifact_identity":"63733a5a6a819b89adbcd1d78efab5af","band_override":null,"decided_at":"2026-11-01T13:57:13.894Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3,"investigation_id":"db70d8e6-b464-41ed-81c3-e2e9c02d75b8","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":23,"page_slug":"opacus","prev_score":35,"reason":"Counting claim_findings, 3 of 10 are disputed or unverifiable (claim_findings[1] and [2] disputed, [3] unverifiable), which is 30%, on the line between the minor and significant bands. Both disputed findings share one cause: the page prints the token mint in lowercase, which is not a valid Solana address, and so wrongly says it could not confirm the mint matches the site's contract address, when the two match apart from letter case. The rest of the page checks out against the homepage and Meta's own sources, the subject is still operating, and the only omission (the app link) is minor, so the page stays in the minor band at the top of its penalty range. The high-priority gap, that no on-chain analysis of the mint was done, is a further reason to revise rather than approve.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-12,"score_limit":{"applied":-12,"limited":true,"proposed":-15,"rule":"second_opinion_agreed","second":-12},"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}