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 · Polygon (POL)
- Sequence
- #5
- Score
- 60 → 60 (0)
- Cluster
- mainnet-beta
- Slot
- 457918956
- Off-chain at
- 2026-10-17T05:23:19.833Z
- Anchored at
- 2026-10-17T05:23:26.181Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 35LY9V6nSQ9NqQqNdAfvuYZpSGB9jq6JDEnEGmx7RPKH
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1706 chars)
{"actor":"reviewer","artifact_identity":"28e3cf36dca7d3b283ab0bbb4db66380","decided_at":"2026-10-17T05:23:19.637Z","decision":"review","disputed_pct":0.2609,"findings_hash":"B64pRf2hPCRBZT7FXXZvYRkkR4c27wNQGDmijNkUzj72","investigation_id":"e1eee299-13f1-46e7-a2d8-249418ef628d","mode":"findings_only","new_score":60,"page_content_hash":"bfec33d7c8104dd921e5f4dbf7cdd4ec485e18b3d64886d4d2c9b3c154bd8054","page_slug":"polygon-pol","prev_score":60,"reason":"Most individual facts on the page (the two 2021 Immunefi bugs, co-founder departure dates and reasons, layoff figures, the Aave bridge-yield dispute, the October 2025 tokenomics proposal, the 15-validator hard fork, and the Boiron/Nailwal leadership dates) check out against independent reporting and are confirmed. However, the page has three distinct, non-trivial defects: (1) it conflates the MATIC-to-POL migration's September 2024 launch with its 99%-complete milestone, which multiple sources place a year later in September 2025; (2) its central SEC-related citation (sections[2].sources[0], two timeline entries, and the sources_used record) points to an unrelated SEC complaint against Consensys/MetaMask rather than the actual SEC v. Binance complaint, and the SEC section is stale because it omits that the entire Binance case was dismissed with prejudice in May 2025; and (3) the zkEVM deprecation is attributed to Polygon/Nailwal 'citing' a $1M annual operating loss, when that figure is an outside researcher's unverified estimate and Polygon's own stated rationale was strategic, not financial.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}