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 · Yield Protocol
- Sequence
- #3
- Score
- 50 → 50 (0)
- Cluster
- mainnet-beta
- Slot
- 464369594
- Off-chain at
- 2026-11-02T04:59:10.189Z
- Anchored at
- 2026-11-02T04:59:33.000Z
- Block time
- 2026-11-02T04:59:33.000Z
Independent verification
- 1. Database (off-chain)
- U4NDnqAUCqZw17i3gwqkBWyKWttqPVuPUMPZu2au6E4
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1365 chars)
{"actor":"reviewer","artifact_identity":"ee605ec35527354c9bb1377ab5cb4e0c","blocked_count":1,"decided_at":"2026-11-02T04:59:10.131Z","decision":"review","disputed_pct":0.4286,"findings_hash":"28oLY8DHaTZDDWVfn8P4NmPQkvzbdmWDT9KRHRXc4HYZ","investigation_id":"c23832e5-c885-4fee-8d4e-28e2d4ca9576","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":50,"page_content_hash":"fc401aacd7ce84885c6069ddbbdae0c6aa4e29162ee1f5d74ef4d199211a32b2","page_slug":"yield-protocol","prev_score":50,"reason":"The core factual spine holds: the Immunefi bug bounty details, the Euler collateral losses, the October 2023 wind-down and the roughly $181k April 2024 exploit all match sources I could read. Weak points are the unsourced ZachXBT flag section, the CertiK post-mortem attribution and the 'DeFi security literature' claim, which no source supports, and the exact Euler recovery timing and the Feb 2, 2024 date, which I could not confirm. The page's current status (shut down, later exploited) is stated accurately.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":7,"sequence_num":3,"subject_status":"shut_down","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}