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 · BounceBit
View on Solana ↗
Sequence
#2
Score
28 → 28 (0)
Cluster
mainnet-beta
Slot
443510480
Off-chain at
2026-08-25T02:53:19.644Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
698Nn8AUtzcckLwDa2juws5t6WFX94gaHKQySyhJBRms
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1000 chars)
{"actor":"reviewer","decided_at":"2026-08-25T02:53:19.532Z","decision":"review","investigation_id":"b029d553-f9b3-4290-8dfb-d8db25d5d52b","new_score":28,"page_slug":"bouncebit","prev_score":28,"reason":"The vast majority of factual claims on the page — the exploit's timeline, amounts, transaction/account counts, technical root cause, Evmos shutdown details, migration plan, and funding history — are corroborated by multiple independent outlets and, in several cases, exact-quote matches. One timeline date (YZi Labs investment announcement listed as 2024-04-01) is contradicted by more precise sourcing pointing to April 11, 2024. A handful of granular operational details (staked/unbonding position treatment, exact wording of one BounceBit quote, Cosmos EVM's absorption of Evmos code) could not be independently verified but were not found to be false.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}