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
- 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. - 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.
- 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 · Ekubo Protocol
- Sequence
- #10
- Score
- 61 → 61 (0)
- Cluster
- mainnet-beta
- Slot
- 464453148
- Off-chain at
- 2026-11-02T09:57:33.557Z
- Anchored at
- 2026-11-02T09:57:39.000Z
- Block time
- 2026-11-02T09:57:39.000Z
Independent verification
- 1. Database (off-chain)
- HVWagvj9UaxvmcDyyuGvF15mybF8KHBRCFUabzQSFa1L
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1460 chars)
{"actor":"reviewer","artifact_identity":"b7d565be2996da3743f63efab7802a89","blocked_count":1,"decided_at":"2026-11-02T09:57:33.463Z","decision":"review","disputed_pct":0.0909,"findings_hash":"4NNevH7HBB3erXWtPqbWRig3Y8cYheipgxanVnzZxeGD","investigation_id":"766c540c-a4ce-4c02-afb8-366643c4aaf1","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":61,"omissions":{"material":0,"total":2},"page_content_hash":"8a28f79e9f5784fdf216f86c45e3be6b30fb249a0a5773423e16c040d74f81d4","page_slug":"ekubo-protocol","prev_score":61,"reason":"The page is well sourced and mostly accurate on the May 2026 exploit, the Blockworks filing details, the Crypto Briefing score, the governance grant and the audit list. One defect appears twice: the Limit Orders exploit is described as leaving orders unwithdrawable, but the cited filing says the DAO funded the shortfall and balances were restored on 21 September 2026. The 158-day approval detail is not in the cited articles. The token-allocation wording is slightly loose. The DeFiLlama figures and the Grenade, Uniswap forum and Snapshot sources were not checked.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":11,"sequence_num":10,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}