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 · Hector Lending
- Sequence
- #4
- Score
- 45 → 45 (0)
- Cluster
- mainnet-beta
- Slot
- 464346814
- Off-chain at
- 2026-11-02T03:37:52.647Z
- Anchored at
- 2026-11-02T03:38:13.000Z
- Block time
- 2026-11-02T03:38:13.000Z
Independent verification
- 1. Database (off-chain)
- DV7TJw17JF7QgjVpBQ9knCHnUFt6HAr3Q3YM8MZ2js35
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1564 chars)
{"actor":"judge","artifact_identity":"4e334bd45f0564c1985031a869f20a89","band_override":null,"blocked_count":1,"decided_at":"2026-11-02T03:37:52.393Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3333,"investigation_id":"c8fa2a24-bd29-4f93-ade9-892432ade73a","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":45,"page_slug":"hector-lending","prev_score":45,"reason":"Of 9 checkable claims (one was excluded because DefiLlama blocked the reviewer), 3 could not be verified, which is 33% and falls in the significant-issues band. The unverifiable items are the roughly $40 million aggregate loss figure, which conflicts with the page's own incident totals of about $11.4 million (claim_findings[1]), the January 18, 2024 final communication (claim_findings[8]), and the April 9, 2024 final receivership order (claim_findings[9]). In addition, the inside-job or key-compromise statement overstates the CertiK post-mortem (claim_findings[0]). The core receivership, vote, exploit and Chapter 15 narrative is confirmed by CertiK, DL News and Bloomberg Law, so the penalty sits at the low end of the band. A high-priority coverage gap, that most content describes Hector Network rather than Hector Lending itself, supports revision rather than approval.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":9,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}