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_revise · zkFinance
- Sequence
- #4
- Score
- 59 → 59 (0)
- Cluster
- mainnet-beta
- Slot
- 464346062
- Off-chain at
- 2026-11-02T03:35:25.419Z
- Anchored at
- 2026-11-02T03:35:32.000Z
- Block time
- 2026-11-02T03:35:32.000Z
Independent verification
- 1. Database (off-chain)
- ADcq7M4ztyVuPi8RNdj9UsabMqk1Th4aV2EsvBJQtnuw
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1834 chars)
{"actor":"judge","artifact_identity":"eb6979526ac4cb59360eaff402bba299","band_override":null,"blocked_count":2,"decided_at":"2026-11-02T03:35:25.163Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.375,"investigation_id":"295247f5-e876-4fb5-8728-9c0dc0c9d49d","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":59,"page_slug":"zkfinance","prev_score":59,"reason":"Excluding two findings the reviewer could not scored because the sources were blocked (claim_findings[5], [6]), 3 of 8 scored claims could not be verified (37.5%), and none were disputed. The unverified items are the current TVL figure of $24,990 (claim_findings[1]) and the ZachXBT flag, which has no source and is dated 2025 although the page says the date cannot be verified (claim_findings[3], [4]). The page also does not state that DefiLlama marks the protocol dead since the exploit date (omission_findings[0]). The core exploit facts (date, amount, DefiLlama's oracle-misconfiguration label) are consistent with DefiLlama, and the reviewer's confidence is low (0.4), so the penalty is set in the lower half of the band and the page is not denied.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":8,"sequence_num":4,"severity_override":{"applied":true,"band":"significant","from_band":"significant","reason":"omission_findings[0] is material: DefiLlama lists the protocol as a dead adapter since the 2024-11-11 exploit date and the page presents current TVL and a live product description without saying so. The percentage band is already significant, so the override holds at significant rather than going harsher."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}