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 · Yelo (yelotree)
View on Solana ↗
Sequence
#3
Score
40 (-10)
Cluster
mainnet-beta
Slot
425420516
Off-chain at
2026-06-09T22:42:32.249Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
CsQKMYuUenL6Mtgymxi1y66XEm2BseHrwaJfjhBExMch
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1242 chars)
{"actor":"judge","decided_at":"2026-06-09T22:42:31.911Z","decision":"review_revise","investigation_id":"197af20a-93f9-4cbb-9a18-d052cd62de0b","new_score":0,"page_slug":"yelo-yelotree","prev_score":4,"reason":"The reviewer confirmed 17 of 21 claims, with no claims outright disputed. The central criminal charge allegation (claim_findings[2]) is only partially supported: all sourcing traces to ZachXBT's X post and downstream crypto press, and no primary government source — DOJ press release, PACER docket, or charging instrument naming Yelo by legal name — was located. This is the page's most serious allegation and its evidentiary base is weaker than the claim's severity warrants. Two additional claims (claim_findings[18], token contract addresses) are unverifiable due to the live nature of on-chain data. Two high-priority coverage gaps remain open: Yelo's legal name and a primary government source for the charges. The page appropriately flags these limitations, which prevents a harsher penalty, but revision to strengthen the evidentiary attribution on the charges section is warranted.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}