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 · ZeroLend
View on Solana ↗
Sequence
#4
Score
38 → 38 (0)
Cluster
mainnet-beta
Slot
462180033
Off-chain at
2026-10-27T18:56:10.172Z
Anchored at
2026-10-27T18:56:31.000Z
Block time
2026-10-27T18:56:31.000Z

Independent verification

1. Database (off-chain)
5JixnzdQP973Sy5kfStmMWtbUDu9KbPscYpZCSe4Caar
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1502 chars)
{"actor":"judge","artifact_identity":"561300d8fd74cf264478f559c4acdfb2","band_override":null,"decided_at":"2026-10-27T18:56:09.706Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1667,"investigation_id":"12163874-2970-4688-8c28-db45d5d86824","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":38,"page_slug":"zerolend","prev_score":38,"reason":"The core account holds up: the February 2026 wind-down, the TVL and token-price figures, and the February 2025 Base exploit details match Tier 1 and Tier 2 sources (claim_findings[0-4]). Of 17 claims, 1 was disputed and 2 could not be verified, giving about 18% disputed or unverifiable, which falls in the minor-issues band. The disputed item is the 'lying' remark attributed to Rekt News when it was Torakapa's wording (claim_findings[9]). The two unverified items are the 2023-01-01 launch date (claim_findings[14]) and the Athens headquarters and founder names (claim_findings[15]). Several partial issues add to the penalty: a bad archive link, an overstated 'no acknowledgment' claim, an uncited 'no support' claim, and the exploit's collateral described differently by CoinDesk. The omission is minor and the subject status does not contradict the page.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}