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
#4
Score
34 → 34 (0)
Cluster
mainnet-beta
Slot
462185061
Off-chain at
2026-10-27T19:14:06.909Z
Anchored at
2026-10-27T19:14:20.000Z
Block time
2026-10-27T19:14:20.000Z

Independent verification

1. Database (off-chain)
HVvUwFx6VsJLcxEtD2FMJAgnTZu9tcxeWm4rd78Qh39c
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1508 chars)
{"actor":"judge","artifact_identity":"84d21779fb9bd199aef0cfaab21d3014","band_override":null,"decided_at":"2026-10-27T19:14:06.584Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3636,"investigation_id":"d8fdda2e-2ce6-4195-b423-584e9bb1739e","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":34,"page_slug":"hnut-holly-the-squirrel-solana-meme-coin","prev_score":34,"reason":"Of 11 claims checked, 3 were disputed and 1 could not be verified (36%), which falls in the significant-issues band. The three disputed claims (claim_findings[0], [1], [2]) are one repeated error: the page credits PeckShield with the 78% bundled-transaction figure, but the sources attribute it to unnamed reports, and this sits in the summary, a core section and the timeline. claim_findings[3] also overstates the pre-collapse price high ($0.055-$0.07 against about $0.007 in the collapse reporting). The core facts held (703% surge, about 99% collapse, remaining liquidity, no reported regulatory action), the reviewer's confidence was moderate, and the one unverifiable claim is a tangential Pump.fun lawsuit, so the penalty is set at the mild end of the band. A high-priority gap (no on-chain holder or bundler analysis) is open.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}