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 · Orbit Bridge
- Sequence
- #4
- Score
- 53 → 53 (0)
- Cluster
- mainnet-beta
- Slot
- 464256476
- Off-chain at
- 2026-11-01T22:15:13.466Z
- Anchored at
- 2026-11-01T22:15:38.000Z
- Block time
- 2026-11-01T22:15:38.000Z
Independent verification
- 1. Database (off-chain)
- UHMQCHznwixVtjmEeUww3iyvVJjMras4D224JMYQuLw
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1241 chars)
{"actor":"reviewer","artifact_identity":"700e6251870d37150270db84d6509a98","decided_at":"2026-11-01T22:15:13.399Z","decision":"review","disputed_pct":0.3333,"findings_hash":"6aXM4sPzGHfwnBKPCEv3EhZd94K3tQ236LDM5CTN2tbB","investigation_id":"4e61eb7d-03f2-41e4-b415-2f288389f598","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":53,"page_content_hash":"bbb550b60180c792c6142453c915ab4a554dfa135e857a14c913c10468550f2b","page_slug":"orbit-bridge","prev_score":53,"reason":"The two sources fetched (Rekt News, The Block) support the core facts: amounts, UTC timing and the CISO allegation timeline. The page is carefully hedged on Lazarus and the insider claims. One claim about the multisig threshold is not supported by Rekt, and the 'Both source pages' wording is internal process language. The mid-2025 cutoff is stale and no later status could be found. Many claims were not independently checked.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}