Skip to main content
Sign in
← avoid.net

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

  1. 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.
  2. 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.
  3. 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 · Kaspa
View on Solana ↗
Sequence
#2
Score
74 → 74 (0)
Cluster
mainnet-beta
Slot
424049846
Off-chain at
2026-06-03T15:02:04.200Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
EFtiRMndpg4EQrerxeBUkS9kotJz74VfYZ39P4SZsBiD
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1325 chars)
{"actor":"reviewer","decided_at":"2026-06-03T15:02:04.140Z","decision":"review","investigation_id":"2286f6e9-0799-45fe-855c-afa4281fab8f","new_score":74,"page_slug":"kaspa","prev_score":74,"reason":"The Kaspa investigation is substantially well-sourced and factually accurate for its core historical, technical, and governance claims. Four material errors were identified: (1) the Bitmain Antminer KS7 hashrate is stated as ~23 TH/s when it is actually ~40 TH/s at ~3,080W; (2) the claim that Kaspa is listed on Binance appears to confuse Binance Futures/Pool access with a spot listing, which multiple current sources say does not exist; (3) the timeline entry for Marathon Digital incorrectly states 60 PH deployed (the actual deployed figure was 30 PH at announcement, with 60 PH the total purchase order); and (4) the 95% supply mined figure is attributed to 'late 2025' when emission schedule data places this milestone around July 2026. The kaspa.org/kaspa-updates-to-crescendo-and-10bps/ URL returned 404 during review. The genesis reset narrative and fair-launch structure are credibly documented, and the regulatory analysis is grounded in real March 2026 SEC-CFTC guidance.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}