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 · UNUS SED LEO
View on Solana ↗
Sequence
#4
Score
36 → 36 (0)
Cluster
mainnet-beta
Slot
464291087
Off-chain at
2026-11-02T00:18:53.543Z
Anchored at
2026-11-02T00:19:06.000Z
Block time
2026-11-02T00:19:06.000Z

Independent verification

1. Database (off-chain)
GEpubRfiMZtdUQJeFUhN99u2pJiJgXMH4hi9AHNGtJWy
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1588 chars)
{"actor":"judge","artifact_identity":"998663f2ba15b6539d13cc9af02a7570","band_override":null,"decided_at":"2026-11-02T00:18:53.205Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2,"investigation_id":"aefc133a-5e13-45a6-967e-ee7f1780b0fc","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":36,"page_slug":"leo-token","prev_score":36,"reason":"The core facts hold up: the $18.5M February 2021 NYAG settlement, the New York trading bar, and the 27% and 80% buyback terms all match the cited sources (claim_findings[0], [1], [5], [6]). Two of ten claims could not be verified, giving a 20% unverified rate and no disputed claims. These are the 2024 timeline entry about recovered hack BTC transfers, which the cited source does not support (claim_findings[7]), and the list of governments that seized Crypto Capital funds (claim_findings[9]). The price and market-cap figures are undated in the summary and conflict with later tracker data, and the Cointelligence allegation is presented without noting it is an unproven 2019 claim (claim_findings[2], [3], [4]). The reviewer also flagged missing on-chain verification of burn totals and the unresolved BTC recovery status as high-priority gaps. The omission about iFinex controlling supply and burns is minor, and the token is still operating.","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}