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 · Audius
View on Solana ↗
Sequence
#3
Score
32 → 58 (+26)
Cluster
mainnet-beta
Slot
426514352
Off-chain at
2026-06-14T23:15:51.980Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
68FGkBHqLaAiBuETGBZhKTtbuDtKMHkSfNCg4kcETaA7
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1494 chars)
{"actor":"judge","decided_at":"2026-06-14T23:15:51.875Z","decision":"review_approve","investigation_id":"783e4b94-9c36-46a8-b071-ef7fc56191b5","new_score":58,"page_slug":"audius","prev_score":32,"reason":"All six claim_findings were independently supported with no disputed claims (disputed_pct = 0%). The calibration review establishes that Audius is a legitimate, still-operating decentralized music protocol backed by top-tier institutional investors, with no fraud, no SEC action, and no exit-scam indicators. The sole material incident — the July 23, 2022 treasury exploit (claim_findings[0] and [1]) — was perpetrated by an external attacker exploiting a storage-collision bug; the team patched the vulnerability within 87 minutes. Placing a hack victim with rapid incident response in the WARNING band (20–49), which is reserved for elevated fraud risk or unresolved severe incidents, is a mis-band under the platform's own band semantics. Residual caveats (unresolved NMPA copyright concerns, severe token price decline, and two audits that missed the specific vulnerability) support a mid-CAUTIONARY score of 58 rather than a higher VERIFIED rating, but do not warrant the current WARNING band. The page content is accurate and must remain published; the score delta of +26 moves the score from 32 to the reviewer-recommended 58 (CAUTIONARY).","score_delta":26,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}