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_revise · Kaspa
- Sequence
- #3
- Score
- 74 → 64 (-10)
- Cluster
- mainnet-beta
- Slot
- 424049872
- Off-chain at
- 2026-06-03T15:02:04.325Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- Ayv9JFfomBDULgXk9gonWneJmuGbGeiBgVBGLSGE46oz
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1610 chars)
{"actor":"judge","decided_at":"2026-06-03T15:02:04.140Z","decision":"review_revise","investigation_id":"2286f6e9-0799-45fe-855c-afa4281fab8f","new_score":64,"page_slug":"kaspa","prev_score":74,"reason":"The review found 4 disputed claims out of 27 (14.8%), placing this page in the minor-issues band. None of the disputes affect core integrity findings: the fair-launch structure, genesis reset narrative, and security incident history are all confirmed. The four corrections needed are: claim_findings[13] overstates Bitmain Antminer KS7 hashrate at 23 TH/s when vendor sources consistently show 36-40 TH/s at lower wattage; claim_findings[12] states Kaspa is listed on Binance when multiple current sources indicate only futures/pool access, not spot trading; timeline[11] (claim_findings[22]) incorrectly states 60 PH deployed by Marathon at announcement versus the correct 30 PH deployed figure; and claim_findings[23] places the 95%-mined milestone in late 2025 when emission schedule data places it around July 2026. A 404 on a critical official source (kaspa.org/kaspa-updates-to-crescendo-and-10bps/) was noted, though the underlying Crescendo facts were confirmed independently. Two high-priority coverage gaps — on-chain wallet distribution analysis and independent verification of the genesis reset UTXO checkpoint — are flagged for expansion. The page is substantially accurate and should be revised to correct the four factual errors before re-approval.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}