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
#5
Score
56 → 56 (0)
Cluster
mainnet-beta
Slot
462376466
Off-chain at
2026-10-28T06:33:40.065Z
Anchored at
2026-10-28T06:33:56.000Z
Block time
2026-10-28T06:33:56.000Z

Independent verification

1. Database (off-chain)
53u51SkipxbrWs5uH7S2EeW7VEchpuDRa2XS2rwNz95
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1955 chars)
{"actor":"reviewer","artifact_identity":"f890d60026b98250450b35dc7e88b156","blocked_count":1,"decided_at":"2026-10-28T06:33:39.866Z","decision":"review","disputed_pct":0.2273,"findings_hash":"GqCSknsFRoQFEzhxaZuqwvH34H3zCHpiEtx1e3ocHgvu","investigation_id":"cdc56e65-d362-4453-97bd-5b5f6f3137e7","mode":"findings_only","new_score":56,"page_content_hash":"705cc8e18c52878ca4d405307cb06f80b91f925014412ff54aa1583cf5219956","page_slug":"toobit-exchange","prev_score":56,"reason":"Most of the page's claims about Toobit's corporate structure, regulatory status, withdrawal-complaint pattern, and public rebuttals are accurately sourced and corroborated by independent checks, and the page is already careful to hedge low-credibility material (the Blockopedia post, the single-source ZachXBT/BDAG claim). The clearest problem is the Token Listing Due Diligence Concerns section and its matching timeline/summary language: the sole source naming Toobit in ZachXBT's BDAG-listing criticism is a low-quality, apparently templated outlet, while more credible contemporaneous reporting on the same ZachXBT campaign names LBank as the exchange involved, casting real doubt on Toobit's role in that specific episode. A secondary, more minor issue is that the Corporate Structure section's FinCEN-registry claim is sourced to Bitget Academy without disclosing that another of the page's own cited sources (Coin Bureau) reports the opposite finding. The Hacken '13 findings' figure could not be verified due to a blocked primary source. No evidence of a hack, shutdown, sanction, or regulatory action against Toobit was found, consistent with the page.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":22,"sequence_num":5,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}