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 · Polygon
View on Solana ↗
Sequence
#3
Score
62 → 54 (-8)
Cluster
mainnet-beta
Slot
424319274
Off-chain at
2026-06-04T20:51:00.713Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
CCpvx2Dn1tPrQ8ZgQHLy9byErUAV4FYU11beqmagG3FU
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1422 chars)
{"actor":"judge","decided_at":"2026-06-04T20:51:00.503Z","decision":"review_revise","investigation_id":"6727e512-e9d3-4569-9b3c-43e919eba256","new_score":54,"page_slug":"polygon","prev_score":62,"reason":"The page is broadly accurate across its 24 reviewed claims (15 confirmed, 5 partially supported, 2 disputed), placing it at 8% disputed — nominally within the approve band. However, two disputed findings carry enough weight to require revision. claim_findings[14] (Discord breach, sections[4]) states that 'no on-chain user funds were reported stolen,' which directly contradicts the page's own primary cited source (CryptoSlate, Tier 1), as well as The Block and The Coin Republic, all of which document approximately $145,000–$150,000 in ETH losses from the incident. This is an internally inconsistent factual error on a user-harm claim. claim_findings[9] (ChainArgos analysis, sections[2] and timeline) incorrectly dates the ChainArgos report to 'early 2023' and timeline entry '2023-03-01' when the primary source (ChainArgos Medium post) was published January 15, 2024 — a ten-month error in a high-severity section. Two cited CoinTelegraph URLs also returned 404 errors. No status change or delist is warranted; both errors are correctable without wholesale revision.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}