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 · Hyperdrive HL
View on Solana ↗
Sequence
#5
Score
52 → 52 (0)
Cluster
mainnet-beta
Slot
459483399
Off-chain at
2026-10-21T03:43:46.807Z
Anchored at
2026-10-21T03:43:59.937Z
Block time
—

Independent verification

1. Database (off-chain)
CpEBhyqufcAKVPjSu4eVJJePf9Ur4EPf7Yec4awSvBNT
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1900 chars)
{"actor":"reviewer","artifact_identity":"f0707f70aeeee38509ddd5865cad3156","decided_at":"2026-10-21T03:43:46.539Z","decision":"review","disputed_pct":0.381,"findings_hash":"9sYjcYpLrNd83q9jdBqC36Gvrv1QFYD4qw6nCUUePcNG","investigation_id":"dd592b49-5cdd-4dcf-b6aa-39f2c6ac9a89","mode":"findings_only","new_score":52,"page_content_hash":"b0abd9f2f092465a1fa783f85c8d599d62c6a63fdfcb4302f4875a11e6dc9d2c","page_slug":"hyperdrive-hl","prev_score":52,"reason":"The page's core narrative — the May 2025 Series A and launch, the September 27, 2025 router exploit, the token/fund amounts, the cross-chain laundering via deBridge and Tornado Cash, and the HyperVault/Hyperliquid ecosystem context — is well-supported by independent reporting and matches cited sources closely, including exact quoted figures from CertiK. However, three prose claims are disputed: the page mischaracterizes an Arrington Capital blog post as a 'subsequent' post-incident commentary on the Hyperdrive exploit when it was actually published six months earlier about different incidents; it inverts the sequence of an audit-vs-refactor claim (refactors followed audits, not the reverse); and it asserts HYPED is 'listed with a live price' on CoinPedia when the cited page shows no price data at all. One source's archive_url in sources_used points to an unrelated CoinCentral article about Bitcoin and quantum computing rather than the Hyperdrive story (link_rot on the archive field specifically; the live URL itself works fine and a correct archive snapshot exists). A handful of claims (the 10% white-hat bounty offer, the Hyperdrive Miles Season 1/2 details, the DELV Cantina bounty comparison) could not be verified one way or the other, mostly due to inaccessible or absent sourcing.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}