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.
- Sequence
- #2
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 443510828
- Off-chain at
- 2026-08-25T03:11:22.625Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- hh2JCYFL6DbKEpLNBmmPcWFA8xeEgUkKok2sQDB6aaz
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1293 chars)
{"actor":"reviewer","decided_at":"2026-08-25T03:11:22.447Z","decision":"review","investigation_id":"d2e83b50-26b3-4b94-bf76-3e25e8acd59c","new_score":0,"page_slug":"crypto-whale-25-6m-repeat-phishing-drain-august-2026","prev_score":0,"reason":"The large majority of the page's factual claims — dollar amounts, dates, token holdings, addresses for the 2023 incident, the 2023 restitution details, and the broader-week incident roundup — are well corroborated across multiple independent outlets and directly-fetched sources. The one significant finding is a genuine contradiction in the underlying reporting ecosystem over whether the address 0x8fEB...F95Ae (attributed to the 2026 attacker by the page) is actually the attacker's or the persistently-targeted victim's wallet; the page's own cited source supports its framing, but at least two other outlets covering the same event contradict it. Two negative/absence claims are properly unverifiable, and two claims (an unconfirmed phishing-kit attribution and the Harmony dollar-value framing) are only partially supported by the specific citations given, though independently corroborable elsewhere.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}