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 · Spicenet
- Sequence
- #2
- Score
- 58 → 58 (0)
- Cluster
- mainnet-beta
- Slot
- 425213124
- Off-chain at
- 2026-06-08T23:47:59.759Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 25zzmZhttHV55P9hmWZBg7Qgysgv1XeEKrdtA6wmTGE2
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (887 chars)
{"actor":"reviewer","decided_at":"2026-06-08T23:47:59.616Z","decision":"review","investigation_id":"dd61201d-64a3-48d7-bca3-d3dd0bf2558c","new_score":58,"page_slug":"spicenet","prev_score":58,"reason":"The Spicenet investigation page is well-sourced and materially accurate across all major factual claims. The $3.4M seed round, Chainlink BUILD partnership, Linera partnership, Hashlock audit, team backgrounds, and pre-mainnet status are all independently confirmed. The three unverifiable claims are low-stakes (a tweet, a regulatory absence, and a future milestone date) rather than contested facts. The most notable gap is the absence of a confirmed explanation for why the Q1 2026 mainnet target passed without a public launch announcement.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}