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 · Blockchain Capital
View on Solana ↗
Sequence
#3
Score
68 → 68 (0)
Cluster
mainnet-beta
Slot
424160455
Off-chain at
2026-06-04T03:16:41.853Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
CjjniAYJmD8YLsudJdQJHx3eEXgVYaYQDodk8Vu8768r
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1392 chars)
{"actor":"judge","decided_at":"2026-06-04T03:16:41.642Z","decision":"review_approve","investigation_id":"fd98925b-474f-4834-bc05-5e457faa9029","new_score":68,"page_slug":"blockchain-capital","prev_score":68,"reason":"The review verified 26 claims and found 23 confirmed, 1 partially supported, and 1 disputed, yielding a disputed_pct of 7.7% — within the 0–10% approval band. The single disputed finding (claim_findings[22]) concerns the framing that Epstein invested 'alongside Blockchain Capital' in the 2014 Coinbase round; the reviewer established that Blockchain Capital's planned investment was never consummated, making the co-investment framing inaccurate. However, this error is confined to a peripheral section marked medium severity, does not affect the firm's core reputation or fund-safety assessment, and carries no allegation of wrongdoing against the firm. The partially supported claim (claim_findings[4]) reflects a stale NAV snapshot (~$964M vs. current ~$975M), directionally correct and not material. One link rot instance (CoinTelegraph URL, 404) exists but the underlying event is confirmed by multiple independent sources. All coverage gaps are medium or low priority. Reviewer confidence of 0.87 supports a decisive approval.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}