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
- Sequence
- #2
- Score
- 38 → 38 (0)
- Cluster
- mainnet-beta
- Slot
- 464351954
- Off-chain at
- 2026-11-02T03:56:28.262Z
- Anchored at
- 2026-11-02T03:56:36.000Z
- Block time
- 2026-11-02T03:56:36.000Z
Independent verification
- 1. Database (off-chain)
- FijJdRkNELsMZ9LSkcGacL2tmEc7szrCPEzb6W3sHZE
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1324 chars)
{"actor":"reviewer","artifact_identity":"9b56d3440735b34319ac5b0228516b3d","decided_at":"2026-11-02T03:56:28.202Z","decision":"review","disputed_pct":0.2857,"findings_hash":"12QvPwhvsihknwDCeyTZDH9aitVjhW9TY6xoXxgXCpQS","investigation_id":"7a7d6f74-f219-4c4c-8b8c-4a9c8ef4fbe9","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":38,"omissions":{"material":1,"total":2},"page_content_hash":"234be36b132f32fcf2f8bc3e803a00316a391cbb78d3237b75ebc3e31b4f5424","page_slug":"polymarket-june-2026-supply-chain-attack","prev_score":38,"reason":"The core incident facts hold: the June 25 date, about $3.1M lost, at least 11 wallets, 1,893 ETH, the refund pledge and the unnamed vendor all match fetched sources. The 70 percent marketing-video figure and the June 20 WSJ date could not be found in the cited sources. The consolidation address rests on one low-tier outlet. The page omits the October 29, 2026 repeat third-party breach and does not say whether the June refunds were completed.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":2,"subject_status":"operating","subject_status_contradicts_page":true,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}