Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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.

Sequence
#4
Score
7 → 7 (0)
Cluster
mainnet-beta
Slot
457574855
Off-chain at
2026-10-16T08:43:19.335Z
Anchored at
2026-10-16T08:43:25.328Z
Block time
—

Independent verification

1. Database (off-chain)
EaRzL4dkFnjzbZd1DokvrXm2isGZhGMtaEMpVfFq6B2p
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2148 chars)
{"actor":"reviewer","artifact_identity":"97ee6bf714d91b4ebef704f0b3fef686","decided_at":"2026-10-16T08:43:19.140Z","decision":"review","disputed_pct":0.2,"findings_hash":"4cvqaQ5Xy7uRZJNg3wGTgwKsLRM2muaJCvEm2yMttJMZ","investigation_id":"1501a1f9-c595-4fbd-81cc-e4ee6619804c","mode":"findings_only","new_score":7,"page_content_hash":"9463b9d1a1ec18df49a6d5a5759c7ffd8131f820e9e0cb239a92a54d88128b48","page_slug":"ravencoin-rvn","prev_score":7,"reason":"The core factual spine of the page — the KAWPOW nHeight validation flaw, the exploit's start at block 4,487,776 on August 7, 2026, the 2Miners/RavenMiner reorg standoff, exchange suspensions, and the roughly 18-20% price crash with a ~1,118% volume surge — is well corroborated across multiple independently fetched news sources and matches the page's own citations closely. The 2020 inflation exploit's headline figures ($5.7M, ~315M RVN, CryptoScope discovery, July 2 disclosure date) are also confirmed. Three issues stand out: (1) the specific timeline claim of a patch 'at block 1,304,352' on July 4, 2020 could not be verified anywhere, including in the source cited for it; (2) the named attribution to 'Ravencoin maintainer Hans Schmidt' appears nowhere in either cited source or in broader web search, and should be treated as unverified; and (3) the page's own cited source for the 'third known failure' framing (cryip.co) separately describes a September 2018 double-spend that the page's History section omits entirely, muddying what is actually being counted as three. A citation to a Medium/CryptoScope article is dead (403, and recorded by the page's own pipeline as unarchivable) though the claim it supports is otherwise corroborated elsewhere. The page is appropriately scoped to 'as of August 11, 2026' throughout, but given it is now October 2026, a follow-up on the incident's actual resolution and the subsequent real delistings at Upbit and Bitvavo would materially improve currency. No accepted_submissions were present to review.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}