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 · Bitfinex Hack
View on Solana ↗
Sequence
#6
Score
10 → 0 (-15)
Cluster
mainnet-beta
Slot
462187906
Off-chain at
2026-10-27T19:24:17.747Z
Anchored at
2026-10-27T19:24:27.000Z
Block time
2026-10-27T19:24:27.000Z

Independent verification

1. Database (off-chain)
FgHPctgGBUnGk7t6vjktApqbWcdEAtnAn53xEWRVsd2J
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1858 chars)
{"actor":"judge","artifact_identity":"5c35b151432a1aa8920db299c892150f","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T19:24:17.440Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4,"investigation_id":"755ee9e6-8b69-4f8a-a4f5-629dff9274f1","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"bitfinex-hack","prev_score":10,"reason":"Of the 5 claim findings that could be checked (1 more was blocked from review and is excluded), 2 were confirmed, 1 was only partly supported and 2 could not be verified, giving 40% disputed or unverifiable. The most important issue is claim_findings[3]: the page states that a court ordered return of about 94,000 BTC to Bitfinex in 2025, but the reviewer found the status was unsettled and that the judge questioned the return (omission_findings[0]). Morgan's 'eight months' release claim (claim_findings[2]) and the mid-2026 transfer status (claim_findings[4]) found no supporting source. The core 2016 theft, sentencing and arrest facts were confirmed, and the reviewer's confidence was low (0.5), so the penalty is set at the mild end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-15,"scored_claims":5,"sequence_num":6,"severity_override":{"applied":true,"band":"significant","from_band":"significant","reason":"The review reports a material omission: the page leaves out the judge's February 2025 reservations about returning the bitcoin to Bitfinex, while stating the restitution order as settled (claim_findings[3], omission_findings[0]). This is consistent with the significant band implied by the percentage, so no harsher band is used."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}