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.

Sequence
#7
Score
17 → 0 (-30)
Cluster
mainnet-beta
Slot
464272072
Off-chain at
2026-11-01T23:11:10.900Z
Anchored at
2026-11-01T23:11:20.000Z
Block time
2026-11-01T23:11:20.000Z

Independent verification

1. Database (off-chain)
H9LWFJR9nWS1J7mB4nsyxgSouvNBrRUJqVZCJjjkcLeS
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2831 chars)
{"actor":"judge","artifact_identity":"113e9ea7ff42889203e8123f6949f84e","band_override":{"actual_delta":-30,"actual_verdict":"review_revise","disputed_pct":0.625,"expected_delta_range":[-50,-30],"expected_verdict":"review_deny","rationale":"Of 8 countable claim findings (one excluded as source_blocked), 5 were disputed or unverifiable, about 62%, which would normally fall in the failed-factcheck band. Four of the disputed findings (claim_findings[0], [1], [2], [6]) are one repeated error: the page says the smart contract upgrade was completed, while The Block reports it as planned after a two-week review. Core facts were confirmed (claim_findings[3], [4], [5]) and reviewer confidence is 0.55, so the page is revised and placed under investigation rather than failed or delisted. The page also does not say whether the review window, upgrade or distribution has happened in the months since, which the review rated a material omission."},"blocked_count":1,"decided_at":"2026-11-01T23:11:10.631Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.625,"investigation_id":"a9a7a1bb-b9d5-47b9-8247-6afdaee77e40","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"loopring-dex-shutdown-june-2026","prev_score":17,"reason":"Of 8 countable claim findings (one excluded as source_blocked), 5 were disputed or unverifiable, about 62%, which would normally fall in the failed-factcheck band. Four of the disputed findings (claim_findings[0], [1], [2], [6]) are one repeated error: the page says the smart contract upgrade was completed, while The Block reports it as planned after a two-week review. Core facts were confirmed (claim_findings[3], [4], [5]) and reviewer confidence is 0.55, so the page is revised and placed under investigation rather than failed or delisted. The page also does not say whether the review window, upgrade or distribution has happened in the months since, which the review rated a material omission.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-30,"score_limit":{"applied":-30,"limited":false,"proposed":-30,"rule":"second_opinion_agreed","second":-30},"scored_claims":8,"sequence_num":7,"severity_override":{"applied":false,"band":null,"from_band":"deny","reason":"The material omission (no update on the review window, contract upgrade or distribution since June 2026) is real, but the review found no authoritative source showing a different outcome, and subject_status.contradicts_page is false because the page does reflect the shutdown. The omission is handled as a revision request and a coverage gap rather than a reason to move to a harsher band."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}