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
#6
Score
61 → 61 (0)
Cluster
mainnet-beta
Slot
461981601
Off-chain at
2026-10-27T07:12:52.660Z
Anchored at
2026-10-27T07:13:13.000Z
Block time
2026-10-27T07:13:13.000Z

Independent verification

1. Database (off-chain)
EngCQbQ9ctaumzZjhoJguN5kiLhghYB4MnNME2gpbnBo
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1421 chars)
{"actor":"reviewer","artifact_identity":"2d1af4ad7092bc68e9f547a28c465d14","blocked_count":1,"decided_at":"2026-10-27T07:12:52.281Z","decision":"review","disputed_pct":0.3,"findings_hash":"Egb78wjXHcaScHiscsrcEYGG83fgsMYeXdQ3LQG211Qg","investigation_id":"766c540c-a4ce-4c02-afb8-366643c4aaf1","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":61,"omissions":{"material":2,"total":2},"page_content_hash":"f97688b2007c4a5e9f091c9f2d86aef35176838d614375471767a05ca59819fb","page_slug":"ekubo-protocol","prev_score":61,"reason":"The exploit narrative is mostly supported: $1.4M in WBTC, 85 transactions, 17 WBTC from one victim, Tornado Cash laundering and an unaffected Starknet deployment. The weak points are the 'on-chain recovery fund' wording, which no cited source supports and which looks like a proposed capped reimbursement plan, and the Blockworks claim of 39/40 with zero gaps. The live Blockworks filing is dated October 2026 and lists many disclosure gaps. Several other claims (TVL, Uniswap proposal, audits, contract date) were not fully checked.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":10,"sequence_num":6,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}