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

Independent verification

1. Database (off-chain)
2roDqnoK9NiCPpFH2a89LZTga41MPAjsQ923QDfHVxR9
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1566 chars)
{"actor":"judge","decided_at":"2026-08-25T02:53:19.532Z","decision":"review_revise","investigation_id":"b029d553-f9b3-4290-8dfb-d8db25d5d52b","new_score":20,"page_slug":"bouncebit","prev_score":28,"reason":"The reviewer confirmed 26 of 32 factual claims on the page, including the core exploit timeline, dollar and token amounts, technical root cause, and the shutdown/migration plan, several via exact-quote matches across independent outlets. The single disputed item (claim_findings[29]) is a peripheral timeline date — the YZi Labs investment announcement is listed as April 1, 2024, when more precise sourcing points to April 11, 2024 — an error of degree, not substance, since the month and the fact of the investment are correct. Three claims were marked unverifiable, and the reviewer notes some of that stemmed from source-fetch blocks (403/402 errors) rather than any actual absence of evidence, which limits how much weight those should carry against the page. The reviewer also flagged a high-priority coverage gap (coverage_gaps[0]): the page never addresses whether BounceBit's Evmos vesting module had prior audit coverage, which is a meaningful omission given that framework obsolescence is presented as a material risk factor. Combined, this supports a light revision rather than approval or denial: the page is fundamentally accurate but should correct the one disputed date and add audit-history context.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}