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_approve · Slope Wallet
View on Solana ↗
Sequence
#3
Score
12 → 28 (+16)
Cluster
mainnet-beta
Slot
426697976
Off-chain at
2026-06-15T19:30:07.866Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
5dnTj3pibUQ3xdsMetpt1PwTcCrz5JrP2XMP6rKuhyUq
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1548 chars)
{"actor":"judge","decided_at":"2026-06-15T19:30:07.626Z","decision":"review_approve","investigation_id":"cfabca4b-5d49-449c-847e-9a2e980c614c","new_score":28,"page_slug":"slope-wallet","prev_score":12,"reason":"The reviewer verified 18 claims across the summary and timeline: 12 confirmed, 4 partially supported, and 0 disputed, yielding a 0% disputed rate. Content is factually sound and supported by primary sources including the Solana Foundation incident report, Slope Finance's own DFIR report, and multiple Tier 1 outlets. The page's current score of 12 (CRITICAL) is inconsistent with the nature of the incident: the root cause was a severe security misconfiguration in Slope's own code — own-negligence, not intentional fraud. No exit scam, Ponzi structure, or criminal conviction is present. Under fraud-likelihood scoring semantics, own-negligence without criminal fraud sits in the WARNING band (20–49), not CRITICAL (0–19). The reviewer's recommended score of 28 reflects the severity of the negligence (~$4M user loss, no compensation, post-incident abandonment) while correctly distinguishing it from deliberate criminal conduct. Two instances of link rot noted in claim_findings[5] and claim_findings[17] do not affect the factual record as the underlying content is confirmed through alternate URLs and secondary sources. Score is corrected upward by +16 to align with calibration anchors.","score_delta":16,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}