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 · Binance
View on Solana ↗
Sequence
#10
Score
26 → 26 (0)
Cluster
mainnet-beta
Slot
466739610
Off-chain at
2026-11-08T02:00:21.321Z
Anchored at
2026-11-08T02:01:10.000Z
Block time
2026-11-08T02:01:10.000Z

Independent verification

1. Database (off-chain)
FxYZcmuLih2rxSJ6m1kGUSmPCE3WKr5wwAZd7Lvbrhd7
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1709 chars)
{"actor":"judge","artifact_identity":"cf1f39bc1018d323e0de77d5dee4baf4","band_override":null,"decided_at":"2026-11-08T02:00:20.921Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1429,"investigation_id":"ee0b172d-1fd3-47c7-812a-115748f8108a","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":26,"page_slug":"binance","prev_score":26,"reason":"Of 7 claim findings, 1 was disputed (claim_findings[5]: the timeline gives 60,000 users in the KYC leak while the cited Hacker News article says 10,000), so about 14% are disputed, which falls in the minor band. claim_findings[4] is partially supported for the same reason. The core October 2026 theft figures, the attribution and the monitorship claims were confirmed against Chainalysis and wire coverage. The page also omits Binance's June-July 2026 EU service halt after withdrawing its MiCA application (omission_findings[0], material), which keeps this from being approved. The review was a time-boxed spot check, so the penalty is kept modest.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":10,"severity_override":{"applied":true,"band":"minor","from_band":"minor","reason":"The review reports a material omission (Binance's June-July 2026 EU service halt after withdrawing its Greek MiCA application) and a high-priority coverage gap on it. Approval is not appropriate, but the page is operating and the core October 2026 theft section is confirmed, so the minor band is kept rather than escalating further."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}