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 · Nostra Finance
- Sequence
- #5
- Score
- 26 → 26 (0)
- Cluster
- mainnet-beta
- Slot
- 462187724
- Off-chain at
- 2026-10-27T19:23:37.176Z
- Anchored at
- 2026-10-27T19:23:48.000Z
- Block time
- 2026-10-27T19:23:48.000Z
Independent verification
- 1. Database (off-chain)
- EPyDWFLzEpE31RqERhR9msrXcdiJwtDTgZ5Wn2PViynP
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1371 chars)
{"actor":"judge","artifact_identity":"d696bbdc274ae2aa1068e777c8f25277","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T19:23:36.894Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2,"investigation_id":"581dea21-b92e-40cf-bc6f-6101b820e33e","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"page_slug":"nostra-finance","prev_score":26,"reason":"Of 11 claims checked, one source-blocked item was set aside and 2 of the remaining 10 were disputed or unverifiable (20%), which falls in the minor-issues band. The core September 2026 exploit account (claim_findings[0-4], [9]) was confirmed, but the 'peak TVL of $55 million' figure (claim_findings[5]) is a current figure mislabeled as a peak, and the nstSTRK launch (claim_findings[7]) could not be sourced. The Garai resignation (claim_findings[6]) appears true but is cited to a page that does not mention it. The two omissions are minor and the subject status matches the page. The high-priority gap is that the exploit rests on secondary sources and a single blog, not primary ones.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":10,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}