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_approve · XDC Network
- Sequence
- #3
- Score
- 62 → 62 (0)
- Cluster
- mainnet-beta
- Slot
- 424483237
- Off-chain at
- 2026-06-05T15:00:33.840Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- Ea83hCucZDGRhpKmJNdkZ74CYgoNrnvtDM9PD3dGJUAk
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1161 chars)
{"actor":"judge","decided_at":"2026-06-05T15:00:33.605Z","decision":"review_approve","investigation_id":"fc145b64-1335-4b3c-aafe-fffa9096e641","new_score":62,"page_slug":"xdc-network","prev_score":62,"reason":"The review found 10 of 14 claims confirmed, 2 partially supported, and 1 disputed, yielding a disputed_pct of 7% — within the 0-10% approval band. The sole disputed claim (claim_findings[6]) is a minor date classification error: the XDC 2.0 upgrade occurred on September 30, 2024 (Q3), not Q4 as stated on the page. The two partially supported claims (claim_findings[0] and claim_findings[11]) reflect a co-founder who departed in 2018 being listed without qualification, and a slightly imprecise characterization of Elliptic's scope — neither rises to a material factual dispute. Three high-priority coverage gaps around token distribution, validator concentration, and source independence are noted and warrant future expansion, but open coverage gaps do not require denial or revision under current policy.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}