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 Token ($ORAMAMA)
- Sequence
- #3
- Score
- 3 → 0 (-8)
- Cluster
- mainnet-beta
- Slot
- 463289240
- Off-chain at
- 2026-10-30T12:42:32.075Z
- Anchored at
- 2026-10-30T12:42:51.000Z
- Block time
- 2026-10-30T12:42:51.000Z
Independent verification
- 1. Database (off-chain)
- D6P2SxKXTJrqAAAFsmUS2YM6wkbPyuuNw8hess78YEnr
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2450 chars)
{"actor":"judge","artifact_identity":"2649d5e196b1cfc4af5059b68bc1bac3","band_override":{"actual_delta":-8,"actual_verdict":"review_revise","disputed_pct":0,"expected_delta_range":[0,0],"expected_verdict":"review_approve","rationale":"The core claims (the February 22 promotion, about ten accounts, six-figure profits attributed to ZachXBT, and the user ID and AI persona) were confirmed against Cointelegraph and the original thread (claim_findings[0], [1]). By the strict formula the page has 0% disputed claims (0 of 7 counted findings; one finding was excluded because the source blocked the reviewer). The page is revised rather than approved because a Coinpedia citation returns 410 Gone and is used in several places (claim_findings[5], [6]), the statement that Nikita Bier was aware of the accounts is not supported by either readable cited source (claim_findings[3]), and a high-priority coverage gap remains: no independent on-chain analysis of the ORAMAMA mint and profit wallets. No shutdown, sanction or material omission was found."},"blocked_count":1,"decided_at":"2026-10-30T12:42:31.860Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"9cbb3911-3cfc-4e09-be09-ac868908e4e7","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"oramama-token-oramama","prev_score":3,"reason":"The core claims (the February 22 promotion, about ten accounts, six-figure profits attributed to ZachXBT, and the user ID and AI persona) were confirmed against Cointelegraph and the original thread (claim_findings[0], [1]). By the strict formula the page has 0% disputed claims (0 of 7 counted findings; one finding was excluded because the source blocked the reviewer). The page is revised rather than approved because a Coinpedia citation returns 410 Gone and is used in several places (claim_findings[5], [6]), the statement that Nikita Bier was aware of the accounts is not supported by either readable cited source (claim_findings[3]), and a high-priority coverage gap remains: no independent on-chain analysis of the ORAMAMA mint and profit wallets. No shutdown, sanction or material omission was found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-8,"scored_claims":7,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}