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
- 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. - 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.
- 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 · Orbit Bridge
- Sequence
- #5
- Score
- 53 → 53 (0)
- Cluster
- mainnet-beta
- Slot
- 464256482
- Off-chain at
- 2026-11-01T22:15:13.641Z
- Anchored at
- 2026-11-01T22:15:39.000Z
- Block time
- 2026-11-01T22:15:39.000Z
Independent verification
- 1. Database (off-chain)
- ubXXY7zVgefhATupL4DCEyU1w64sS32PN11kFuWqL4d
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1379 chars)
{"actor":"judge","artifact_identity":"700e6251870d37150270db84d6509a98","band_override":null,"decided_at":"2026-11-01T22:15:13.399Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3333,"investigation_id":"4e61eb7d-03f2-41e4-b415-2f288389f598","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":53,"page_slug":"orbit-bridge","prev_score":53,"reason":"Of 6 claims checked, 3 were confirmed or partly supported against Rekt News and The Block (claim_findings[0], [1], [3] on amounts, timing and the CISO timeline). Two claims (claim_findings[4] and [5]) about the attacker's remaining holdings and the absence of recovery as of mid-2025 could not be verified and are now about 16 months out of date, which puts 2 of 6 (33%) in the significant band. claim_findings[2] cited Rekt for a multisig threshold that Rekt does not state, and uses internal wording ('Both source pages') that should not appear on a published page. Nothing was disputed and no shutdown, sanction or omission was found, and the reviewer's confidence was low (0.4), so the penalty is set at the mild end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}