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 · ORAMAMA X War-Panic Scam Network
- Sequence
- #6
- Score
- 2 → 0 (-10)
- Cluster
- mainnet-beta
- Slot
- 461972065
- Off-chain at
- 2026-10-27T06:39:16.050Z
- Anchored at
- 2026-10-27T06:39:23.000Z
- Block time
- 2026-10-27T06:39:23.000Z
Independent verification
- 1. Database (off-chain)
- B7PBN5hzkjoqr3B7qhYkqg16WsVK4s4h2DdXNQ47S1pR
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1491 chars)
{"actor":"judge","artifact_identity":"e5a6e42da2f9b6196ee128b998e3d2e0","band_override":null,"decided_at":"2026-10-27T06:39:15.675Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.25,"investigation_id":"03c192ed-953c-4829-b6f7-e199e2fd5783","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"oramama-x-war-panic-scam-network","prev_score":2,"reason":"Of 8 claims checked, none were disputed and 2 could not be verified (claim_findings[6] persona follower counts, claim_findings[7] the negative claim that no operator or law enforcement action is known), giving 25% disputed or unverifiable. The core narrative holds: the ZachXBT disclosure, the Feb 22 $ORAMAMA promotion and the attributed six-figure profit claim were confirmed. Four findings were only partly supported: the suspension claim and its Crypto.news attribution (claim_findings[2], [3]), the Bier causal wording in the timeline (claim_findings[4]) and the 'later the same day' timing of the 16-account total (claim_findings[5]). Two high-priority coverage gaps (ZachXBT's thread not readable, no independent on-chain trace) and the reviewer's moderate confidence keep the penalty at the lower end of the minor band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-10,"sequence_num":6,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}