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.

Decision
review · Monero
View on Solana ↗
Sequence
#4
Score
58 → 58 (0)
Cluster
mainnet-beta
Slot
457478100
Off-chain at
2026-10-16T02:55:18.250Z
Anchored at
2026-10-16T02:55:30.337Z
Block time
—

Independent verification

1. Database (off-chain)
7z4MXnEwcLd7yY4CirdMmqKgJCSCDTQ98KQpMW9fqUxW
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1714 chars)
{"actor":"reviewer","artifact_identity":"81a9af7f2812378725f4ee87ddb01f44","decided_at":"2026-10-16T02:55:18.062Z","decision":"review","disputed_pct":0.1667,"findings_hash":"8sLtaYH6CCFq5RuwQz7WdyXddhcnpNNbL13svtfZTrA3","investigation_id":"ab69b864-4fd5-4abf-8bcb-9c6f65db0c25","mode":"findings_only","new_score":58,"page_content_hash":"f55ce9f7a2a2548c275f0050e9688db15bba6e005c5aaf2b96602d84d760315c","page_slug":"monero","prev_score":58,"reason":"The page's core technical and historical claims about Monero (launch, protocol features, exchange delistings, Spagni's legal situation, Archetyp/Nemesis enforcement actions, EU AMLR timeline, IRS bounty, cryptojacking) are well-supported by their cited sources and independent corroboration. The most significant defect is the $282M theft, which the page dates to January 2025 and cites to a CoinDesk article that never mentions it; independent reporting places that theft in January 2026, where it is in fact the proximate cause of the January 2026 all-time-high price event described elsewhere on the same page -- the page is unknowingly describing the same event twice, a year apart. Secondary issues include a market-cap figure that is now ~39% stale relative to its own cited source, a timeline date for Spagni's arrest that reflects the article's publish date rather than the arrest date, a one-day-off date for the 2019 binary compromise, and a few claims (18 Japan arrests, 60+ exchange delistings, CipherTrace patents) that are factually accurate but not actually supported by the specific sources cited for them.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}