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
- #13
- Score
- 63 → 63 (0)
- Cluster
- mainnet-beta
- Slot
- 470678143
- Off-chain at
- 2026-11-17T21:06:01.601Z
- Anchored at
- 2026-11-17T21:06:10.000Z
- Block time
- 2026-11-17T21:06:10.000Z
Independent verification
- 1. Database (off-chain)
- 2e1Mv7L2FyZJt2dgST3z3Y8uYya2fsVGtiT3etUrdhTi
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1441 chars)
{"actor":"reviewer","artifact_identity":"c2e72f3549f439ff516019f6b135f857","decided_at":"2026-11-17T21:06:01.482Z","decision":"review","disputed_pct":0,"findings_hash":"5oPsSWDEwy6k3xeTTJGxzc495yfLbxdjh1UuETx8WHgM","investigation_id":"766c540c-a4ce-4c02-afb8-366643c4aaf1","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":63,"omissions":{"material":0,"total":2},"page_content_hash":"f1c118513017ee3512fcd680d84c87a5b5376c0c26c0c756c47ad1945ccd7b3c","page_slug":"ekubo-protocol","prev_score":63,"reason":"The page is largely accurate: exploit figures, dates, Merkle Science flows, ForkLog details, the Blockworks October 2026 filing details, audits, grant and TVL all match the sources fetched. The one substantive issue is framing: Blockworks' own header rates the filing 'Partial, with 1 gap', while the page describes 'multiple' gaps. The DAO 'ownership' statement of the Starknet contracts is simplified. The subject is still operating and the page already discloses the exploits. Not every claim in the first section (founder background, token thirds distribution) was independently checked.","reviewer_def_hash":"fdb97944d5e6ae9b148ae8c41caf98db055a4c751afd15721cb2e08d11dfd37a","score_delta":0,"sequence_num":13,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}