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_revise · Ekubo Protocol
View on Solana ↗
Sequence
#11
Score
61 → 61 (0)
Cluster
mainnet-beta
Slot
464453153
Off-chain at
2026-11-02T09:57:33.732Z
Anchored at
2026-11-02T09:57:40.000Z
Block time
2026-11-02T09:57:40.000Z

Independent verification

1. Database (off-chain)
HJ3kU7inRSTM65r1krxEcU6Zo9a75GwUd2x44252SwwH
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2664 chars)
{"actor":"judge","artifact_identity":"b7d565be2996da3743f63efab7802a89","band_override":{"actual_delta":-7,"actual_verdict":"review_revise","disputed_pct":0.0909,"expected_delta_range":[0,0],"expected_verdict":"review_approve","rationale":"The core account of the May 2026 exploit, the Merkle Science fund-flow figures, the Crypto Briefing score, the governance grant and the audit list were confirmed (claim_findings[0], [2], [7], [8], [9], [10]). Two findings (claim_findings[3] and [4]) are stale: the page says 63 Limit Orders positions remained unwithdrawable, but the cited Blockworks filing says the DAO funded the shortfall and balances were restored on 21 September 2026. In addition, the 158-day approval detail (claim_findings[1]) is not in the cited articles, and the token-allocation wording is slightly loose (claim_findings[6]). Counting the unverifiable and stale findings, about 27% of checkable claims have problems, which puts the page in the minor-issues band. The omissions are minor, the subject status does not contradict the page, and one DeFiLlama finding was excluded from the percentage because the source blocked the reviewer."},"blocked_count":1,"decided_at":"2026-11-02T09:57:33.463Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.0909,"investigation_id":"766c540c-a4ce-4c02-afb8-366643c4aaf1","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":61,"page_slug":"ekubo-protocol","prev_score":61,"reason":"The core account of the May 2026 exploit, the Merkle Science fund-flow figures, the Crypto Briefing score, the governance grant and the audit list were confirmed (claim_findings[0], [2], [7], [8], [9], [10]). Two findings (claim_findings[3] and [4]) are stale: the page says 63 Limit Orders positions remained unwithdrawable, but the cited Blockworks filing says the DAO funded the shortfall and balances were restored on 21 September 2026. In addition, the 158-day approval detail (claim_findings[1]) is not in the cited articles, and the token-allocation wording is slightly loose (claim_findings[6]). Counting the unverifiable and stale findings, about 27% of checkable claims have problems, which puts the page in the minor-issues band. The omissions are minor, the subject status does not contradict the page, and one DeFiLlama finding was excluded from the percentage because the source blocked the reviewer.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":11,"sequence_num":11,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}