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 · Asymmetric Research
View on Solana ↗
Sequence
#2
Score
82 → 82 (0)
Cluster
mainnet-beta
Slot
443561317
Off-chain at
2026-09-02T00:36:47.235Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
6XonQwkjBe6Pgx7VVgXZvYqECAzuxPbK1hN6bsoCcaJv
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1268 chars)
{"actor":"reviewer","artifact_identity":"5b452159421dfb1103168078a636ef7c","decided_at":"2026-09-02T00:36:47.151Z","decision":"review","disputed_pct":0.0588,"investigation_id":"32e99313-f1cd-4ae6-aed7-c70d28b72801","new_score":82,"page_slug":"asymmetric-research","prev_score":82,"reason":"The page's factual claims are, with minor exceptions, strongly corroborated by primary sources (the firm's own GitHub advisories and blog, Solana Foundation's official post-mortem, Stacks and Wormhole Foundation announcements) and independent Tier 1/2 press (CoinDesk, CoinTelegraph, Blockworks). All checked vulnerability disclosure dates, dollar figures, and outcomes (no funds lost) matched cited sources exactly. Two minor issues were found: one timeline citation links to an unrelated blog post rather than the correct source, and one bio claim (Jeff Schroeder lacking a public biography) understates that he does have an official team page and Crunchbase profile, albeit a thin one. No disputed or stale claims were identified, and no regulatory or fraud history was found independently, consistent with the page's own conclusion.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}