Skip to main content
AVOID.NET
← 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
#5
Score
73 → 73 (0)
Cluster
mainnet-beta
Slot
457585304
Off-chain at
2026-10-16T09:20:30.373Z
Anchored at
2026-10-16T09:20:52.684Z
Block time
—

Independent verification

1. Database (off-chain)
C98FkcnqVX4LYxgQ9kYM2cTGX96pnYTvSVNbUBihHsra
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2544 chars)
{"actor":"reviewer","artifact_identity":"4cb4189928ac06ec86b2ab4397dc7472","decided_at":"2026-10-16T09:20:30.143Z","decision":"review","disputed_pct":0.1176,"findings_hash":"B7aUodtwM4yytBS1Y1wGgtDpwvkhf5HxGQ3NKNkMGCUG","investigation_id":"32e99313-f1cd-4ae6-aed7-c70d28b72801","mode":"findings_only","new_score":73,"page_content_hash":"e07c1170cf95c561d98b66efa00660eee85dd47d7131c152398c8e4d064b5c9a","page_slug":"asymmetric-research","prev_score":73,"reason":"The page's core narrative — two named co-founders with verifiable Jump Crypto/Google Project Zero backgrounds, a long list of responsibly-disclosed vulnerabilities across Cosmos, Evmos, Circle/Noble, Ethereum consensus clients, Helix/Titan MEV relay, Solana (ZK ElGamal, Marginfi, p-token), and Across Protocol, plus embedded partnerships with Wormhole, Stacks, Solana Foundation (STRIDE), and Jito — checks out against primary sources (Solana Foundation post-mortem, Wormhole Foundation announcement, Stacks Foundation announcement, CoinTelegraph/CoinDesk/Blockworks coverage, Asymmetric's own GitHub advisories and blog). The page is also appropriately skeptical of Asymmetric's own self-reported '$100B prevented' and '$300M recovered' marketing figures, correctly flagging them as unaudited. However, several discrete errors were found: (1) the page misattributes a $150 million CoinDesk figure as corroborating a $126 million CoinTelegraph figure for the Cosmos IBC bug, in both a section and the timeline; (2) the timeline's source_url for the Solana p-token bug disclosure points to an unrelated 2025 blog post rather than the actual April 2026 p-token post, even though the underlying claim is true; (3) the Stacks Foundation sBTC signer timeline date (2024-10-01) is three weeks off from the actual October 24, 2024 announcement date; (4) the current Asymmetric Research website states a larger team (50+) spanning four regions (Americas, Europe, Africa, Asia) rather than the 45+/three-region figure given in the page, suggesting the page's team-size claim has gone stale since its source snapshot; and (5) the STRIDE program description as 'co-led' slightly overstates the CoinDesk source, which describes Asymmetric as leading (not co-leading) the program. No regulatory, fraud, or legal issues were found anywhere, consistent with the page's own conclusion, though that absence is inherently unverifiable rather than provable.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}