Skip to main content
Sign in
← 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 · Light Protocol
View on Solana ↗
Sequence
#5
Score
6961 (-8)
Cluster
mainnet-beta
Slot
425201760
Off-chain at
2026-06-08T22:32:22.843Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
BFDRhb1JrqeJ6Rb77ESC2v5JF6KhXqXe1xfX353Y4MZA
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1582 chars)
{"actor":"judge","decided_at":"2026-06-08T22:32:22.635Z","decision":"review_revise","investigation_id":"fa89a22c-e13a-4966-93ed-efd15257403c","new_score":61,"page_slug":"light-protocol","prev_score":69,"reason":"The reviewer found zero directly disputed claims across 29 findings, but five claims are only partially supported and three are unverifiable, yielding a disputed_pct of 0.14 (14%) — within the minor-issues band. The most consequential precision gaps are the Zellic audit date listed as August 28, 2024 while the official security page shows September (claim_findings[14]), the '$4.2M total across two rounds' framing where the pre-seed amount is undisclosed (claim_findings[10]), and approximate founding and pivot dates presented with false precision (claim_findings[26] and [28]). One link-rot instance was flagged: the Immunefi /information/ path returns HTTP 404 (claim_findings[18]), though the program itself is live. A high-priority coverage gap on the Groth16 trusted setup ceremony — number of participants, MPC structure, audit trail — is noted as a material risk dimension absent from the page. No core allegations were contradicted by independent sources, no regulatory or fraud concerns were identified, and reviewer confidence is 0.82. The page should be revised to correct the Zellic date, clarify the funding round framing, add a footnote on the Immunefi link, and expand the trusted setup ceremony description.","score_delta":-8,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}