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 · LND
View on Solana ↗
Sequence
#3
Score
12 → 0 (-25)
Cluster
mainnet-beta
Slot
465082480
Off-chain at
2026-11-03T23:24:36.718Z
Anchored at
2026-11-03T23:24:53.000Z
Block time
2026-11-03T23:24:53.000Z

Independent verification

1. Database (off-chain)
EtZUe7tTZ1JbUDwtms2RNW9aCsBckZ2PvVuxaTQsoBzd
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2651 chars)
{"actor":"judge","artifact_identity":"abb4048e0d77ab77c7d2126ed1a8bd4e","band_override":{"actual_delta":-25,"actual_verdict":"review_revise","disputed_pct":0.6,"expected_delta_range":[-50,-30],"expected_verdict":"review_deny","rationale":"Of 10 claims checked, 2 were disputed (claim_findings[0], [2]) and 4 could not be verified (claim_findings[6]-[9]), giving 60% by count. The disputes are real: a HackMD page by an independent analyst is labeled the team's official postmortem and quoted for a DPRK statement it does not contain, and the $1.42M loss figure is credited to the wrong source. We did not apply the 'failed factcheck' band because the core incident (exploit timeline, Pool Admin dates, fund flows) was confirmed (claim_findings[3]-[5]), none of the unverifiable items was contradicted (the reviewer did not fetch some sources, and a fetch summary may have missed one passage), and reviewer confidence was moderate at 0.6. The page stays under investigation until it cites LND's primary postmortem, which is the only basis of the DPRK attribution (high-priority coverage gap), and fixes the source labels."},"decided_at":"2026-11-03T23:24:36.485Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.6,"investigation_id":"2f7c30c1-4224-4431-b322-5be4c94348e6","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":0,"page_slug":"lnd","prev_score":12,"reason":"Of 10 claims checked, 2 were disputed (claim_findings[0], [2]) and 4 could not be verified (claim_findings[6]-[9]), giving 60% by count. The disputes are real: a HackMD page by an independent analyst is labeled the team's official postmortem and quoted for a DPRK statement it does not contain, and the $1.42M loss figure is credited to the wrong source. We did not apply the 'failed factcheck' band because the core incident (exploit timeline, Pool Admin dates, fund flows) was confirmed (claim_findings[3]-[5]), none of the unverifiable items was contradicted (the reviewer did not fetch some sources, and a fetch summary may have missed one passage), and reviewer confidence was moderate at 0.6. The page stays under investigation until it cites LND's primary postmortem, which is the only basis of the DPRK attribution (high-priority coverage gap), and fixes the source labels.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":-25,"score_limit":{"applied":-25,"limited":false,"proposed":-25,"rule":"second_opinion_agreed","second":-28},"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}