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 · Ravencoin (RVN)
- Sequence
- #2
- Score
- 22 → 22 (0)
- Cluster
- mainnet-beta
- Slot
- 443515750
- Off-chain at
- 2026-08-25T18:04:07.098Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 2qtjiv6BxwPtF8M667GEbcfTxcdzPBvz4EbvQCiUmGbg
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1264 chars)
{"actor":"reviewer","decided_at":"2026-08-25T18:04:07.001Z","decision":"review","investigation_id":"1501a1f9-c595-4fbd-81cc-e4ee6619804c","new_score":22,"page_slug":"ravencoin-rvn","prev_score":22,"reason":"The page's core factual narrative of the August 2026 KAWPOW/nHeight exploit -- block heights, price impact, exchange suspensions, and the mining-pool-issued patch -- is well corroborated across independent outlets. However, several specific details carry citation mismatches where the cited source does not actually contain the stated fact (the Hans Schmidt attribution, the 1,304,352 block-patch date, the CryptoScope discovery credit, and the unsupported 1,118% volume figure), and the page's central 'inactive core team / governance failure' framing is now stale: official RavenProject GitHub releases (v4.7.0, v4.8.0) from the actual core maintainer addressed both outstanding bugs about a week after the reporting window the page relies on. The 2019 Raptoreum incident is also mischaracterized as a comparable 'consensus-level' failure when it was an unexploited asset-layer bug patched internally by the team.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}