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.

Sequence
#4
Score
62 → 62 (0)
Cluster
mainnet-beta
Slot
457663986
Off-chain at
2026-10-16T14:03:36.948Z
Anchored at
2026-10-16T14:03:38.577Z
Block time
—

Independent verification

1. Database (off-chain)
DocRTgkgQEwuEsdEavfuHRUXA558ZXTqzeCuKbwpGsu3
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2113 chars)
{"actor":"reviewer","artifact_identity":"f58dcf11b8e0659c8bda5b2d3ddb4bbf","decided_at":"2026-10-16T14:03:36.703Z","decision":"review","disputed_pct":0.6,"findings_hash":"D7UruazsZ7RXAWfpirUZUjPNNxyyz6SHvuJeHNapTPFN","investigation_id":"766c540c-a4ce-4c02-afb8-366643c4aaf1","mode":"findings_only","new_score":62,"page_content_hash":"f97688b2007c4a5e9f091c9f2d86aef35176838d614375471767a05ca59819fb","page_slug":"ekubo-protocol","prev_score":62,"reason":"The page's core narrative -- a Starknet-native concentrated-liquidity AMM founded by ex-Uniswap engineer Moody Salem, governed by an on-chain DAO, that suffered a May 2026 approval-based exploit on its deprecated EVM V2 router isolated from the Starknet core -- is well-supported by its cited sources, and the technical description of the exploit (Blockaid's IPayer.pay root cause and DarkNavy's competing victim-approval framing) is accurately and fairly summarized. The security-audit history (Nethermind, Plainshift, Cairo Security Clan, Code4rena, Riley Holterhus, ABDK) and the Uniswap DAO investment-proposal narrative both check out in detail against primary sources. However, several claims are overstated, unsupported by their own citations, or stale: Ekubo, Inc.'s state of incorporation is given as New York when a Bloomberg LEI record shows Delaware; the claim that the July 2026 Blockworks transparency filing had 'no noted disclosure gaps' is contradicted by the filing itself, which lists multiple open items including a still-unresolved WBTC recovery claims process tied to the very exploit covered on this page; the advisor list and a reported Delphi Ventures investment are not found in any of the sources cited for them; and the 60% Starknet DEX dominance figure rests on a single unofficial secondary source. The page's generally positive 'Competitive Position' framing also omits a directly relevant negative assessment ('a big flop so far' for the 2025 EVM expansion) from its own cited source.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}