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 · Bond Protocol
- Sequence
- #2
- Score
- 42 → 42 (0)
- Cluster
- mainnet-beta
- Slot
- 443509080
- Off-chain at
- 2026-08-19T01:41:36.837Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- A8wg9qKPndDmpyEytcxGxbasej4WMfSeEvHkgWUuYGgH
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1358 chars)
{"actor":"reviewer","decided_at":"2026-08-19T01:41:36.746Z","decision":"review","investigation_id":"d9137293-15db-46cf-b00d-94ca66903d90","new_score":42,"page_slug":"bond-protocol","prev_score":42,"reason":"The verifiable claims on this page (spin-out from OlympusDAO, the October 2022 Fixed-Expiry Teller exploit and its ~$300K/full-recovery outcome, the $2.5M seed round, post-incident re-auditing, and the current near-zero TVL) are all independently corroborated by credible, mostly non-official sources and are presented without unhedged fraud language. The one factual defect found is a timeline omission/mischaracterization: the page's 'first' post-incident Sherlock audit (Feb 2023) was actually preceded by a November 2022 Sherlock contest and a November 2022 Zellic re-audit, both omitted — an error that, if anything, makes Bond Protocol's remediation look slower than it was, i.e. the record is more favorable to the entity than the page states. The larger caveat is structural: every section body in the review input was empty, so this review could only validate the summary and timeline, not the page's actual prose — that is a gap in the review process itself, not a finding about the page's accuracy.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}