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
#2
Score
62 → 62 (0)
Cluster
mainnet-beta
Slot
423482126
Off-chain at
2026-06-01T00:21:11.006Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
HMEr4auzoBveA675qFvxeeanev1fFdYHu52cXrrSow8
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1176 chars)
{"actor":"reviewer","decided_at":"2026-06-01T00:21:10.791Z","decision":"review","investigation_id":"691f4a75-e5d0-4cc7-a668-7a3042eef2ba","new_score":62,"page_slug":"bonkbot","prev_score":62,"reason":"The BonkBot investigation is generally well-sourced and accurate on its core factual claims: the March 2024 wallet drain incident, the October 2024 non-custodial KMS announcement, user/volume metrics, fee structure, and team structure. Three claims require correction: (1) the page states no corporate entity name has been publicly disclosed, but Triple Spice AG is named in BonkBot's own Terms of Service, which the page cites; (2) the '20% of purchased tokens immediately burned' figure is contradicted by multiple credible sources that consistently cite 10%; and (3) the page's assertion that no independent security audit has been confirmed is disputed by references to an OtterSec KMS audit. The overall trust score calibration appears reasonable for a Telegram trading bot with a real incident history but no regulatory action.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}