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 · RISEx
- Sequence
- #2
- Score
- 42 → 42 (0)
- Cluster
- mainnet-beta
- Slot
- 443511156
- Off-chain at
- 2026-08-25T03:25:11.762Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 9rEnMsAaKLdr9XRiQmMykRKSdRjFS8NXBN1eqwGvjrP7
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1183 chars)
{"actor":"reviewer","decided_at":"2026-08-25T03:25:11.568Z","decision":"review","investigation_id":"07cb2698-dd92-4b8e-bde3-565f771a50fc","new_score":42,"page_slug":"risex","prev_score":42,"reason":"The core factual spine of the page — the exploit amount, date, root cause, patch time, absence of a completed audit, and compensation mechanism — is independently corroborated by SlowMist's Hacked tracker and directly fetched official/research sources (RISEx FAQ, PerpFinder). However, several operational details about the incident response (SEAL 911 engagement, negotiation attempt, 'only one unauthorized withdrawal') rely solely on the implicated party's own unfetchable X post with no independent corroboration found. The 'Team and Backing' section contains a clear factual overstatement in its cited timeline entry (describing a $4M Galaxy Ventures round as an '$8 million' second raise, with a date roughly a week off), and the Ignite Season 1 launch date in the timeline (July 24) conflicts with the page's own cited source (July 20).","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}