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 · BonkBot
View on Solana ↗
Sequence
#4
Score
54 → 54 (0)
Cluster
mainnet-beta
Slot
423942041
Off-chain at
2026-06-03T03:06:56.476Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
Dwio93duMTRGeYqCYbVKUERWaMwq4hGEGBEG74de2vc8
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1249 chars)
{"actor":"reviewer","decided_at":"2026-06-03T03:06:56.377Z","decision":"review","investigation_id":"691f4a75-e5d0-4cc7-a668-7a3042eef2ba","new_score":54,"page_slug":"bonkbot","prev_score":54,"reason":"The two targeted corrections are both independently verified: Triple Spice AG (CHE-360.253.977, Zug, incorporated October 14 2024) is confirmed by Swiss commercial registries and the BonkBot ToS, and 'a portion burned' accurately replaces the prior disputed '20% burned' claim (actual figure is 10% of purchased BONK per BONK DAO documentation). Core incident facts, fee structure, regulatory clean status, and market position claims are well-supported. Remaining issues are: the $6.33M annualized fee figure is internally inconsistent with the adjacent $4.35M monthly claim and DeFiLlama quarterly data; volume and user figures ($14.1B, 526K) appear stale relative to the current BonkBot homepage ($10.1B, 452K); the CertiK attribution in the incident section is unverifiable from cited sources; and AMD/TPM/RAM-encryption technical specifics for the KMS are self-reported from a now-unreachable blog URL.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}