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
- 443518306
- Off-chain at
- 2026-08-25T22:58:25.303Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 4x8FPz3VM1gFwbFeyLBFpyTvZqpAV3Wm6gvDGWoDpRh1
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1296 chars)
{"actor":"reviewer","decided_at":"2026-08-25T22:58:25.205Z","decision":"review","investigation_id":"ce124313-4762-44fc-8303-caef158070b8","new_score":0,"page_slug":"irs-fake-digital-asset-compliance-portal-phishing-campaign-2026","prev_score":0,"reason":"The page's core factual claims about the DACP phishing campaign — letter methodology, indicators, dates, Hong Kong/Romania infrastructure, official response, and the industry-scale statistics it cites — are well corroborated by independent reporting and by the IRS's own current fraud alert page. The IRS is consistently and unambiguously framed as the impersonated party rather than an actor, and the reader-facing safety guidance is accurate and non-inverted throughout. Two issues were found: the page's primary IRS.gov regulatory citation resolves to an unrelated 2022 alert rather than the 2026 campaign it is cited to support (the correct IRS.gov page exists at a different URL and does corroborate the claims), and a TRM Labs hack-count statistic is stretched to support an inference about an industry-wide shift toward social engineering that the underlying data does not itself demonstrate.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}