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 · Badger DAO
- Sequence
- #4
- Score
- 62 → 62 (0)
- Cluster
- mainnet-beta
- Slot
- 464299462
- Off-chain at
- 2026-11-02T00:48:52.472Z
- Anchored at
- 2026-11-02T00:49:06.000Z
- Block time
- 2026-11-02T00:49:06.000Z
Independent verification
- 1. Database (off-chain)
- 62eeJYFngkPvW8uU6hwgTza9KZynvwVZ3uzLzAadXmeq
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1443 chars)
{"actor":"judge","artifact_identity":"fe5c8dcaa0620769e37aa8951ad2571b","band_override":null,"decided_at":"2026-11-02T00:48:52.197Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4286,"investigation_id":"5b1809fe-7e2c-473d-8f92-a6b7c0dce49b","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":62,"page_slug":"badger-dao","prev_score":62,"reason":"Of 7 checked claims, 3 could not be verified (claim_findings[1], [3], [4]), about 43%, which falls in the significant-issues band. The core hack narrative (Dec 2, 2021 front-end attack, roughly $120-130M, compromised Cloudflare key) and the Celsius and Binance claims were confirmed. The June 2025 eBTC sunset appears in the timeline and the Risk Assessment with no supporting source found (claim_findings[3], [4]), and the summary's 'low single-digit millions' TVL was only partially supported against a current figure near $12.9M (claim_findings[6]). Because the reviewer's confidence was moderate (0.5), the unverified hack-timeline dates may simply come from sources the reviewer did not reach, and no omissions or status contradictions were found, the penalty sits at the lower end of the band.","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}