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 · Bond Protocol
- Sequence
- #14
- Score
- 74 → 74 (0)
- Cluster
- mainnet-beta
- Slot
- 464250426
- Off-chain at
- 2026-11-01T21:53:55.232Z
- Anchored at
- 2026-11-01T21:54:02.000Z
- Block time
- 2026-11-01T21:54:02.000Z
Independent verification
- 1. Database (off-chain)
- J69Eyqyv6yPgjeA2oJJ2WT9WkPmQbNf5xb9wdMNnRAeh
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2712 chars)
{"actor":"judge","artifact_identity":"064751b63fe56b10f678be85e16a7f37","band_override":{"actual_delta":-5,"actual_verdict":"review_revise","disputed_pct":0,"expected_delta_range":[0,0],"expected_verdict":"review_approve","rationale":"None of the checkable claims were disputed. claim_findings[0] to [4] (the October 2022 exploit amount, date, PeckShield attribution, auditors, bounty and same-day return) were confirmed by The Block and Decrypt, and claim_findings[6] (the October 2026 TVL collapse) was partly confirmed. Three of nine findings (the seed round, the PitchBook status and the 2023 all-time-high TVL) could not be checked because the sources blocked the reviewer or the data was truncated; these are left out of the percentage and are a coverage limit, not a defect of the page. The calculated dispute rate is 0%, but the review has an open high-priority coverage gap on the project's official 2026 status, the only current-status claim on the page, and reviewer confidence is moderate (0.55), so the verdict is a small revision rather than a plain approval. The only omission, a reported $75k bounty paid to the attacker, is minor and does not change the verdict."},"blocked_count":3,"decided_at":"2026-11-01T21:53:54.757Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"d9137293-15db-46cf-b00d-94ca66903d90","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":74,"page_slug":"bond-protocol","prev_score":74,"reason":"None of the checkable claims were disputed. claim_findings[0] to [4] (the October 2022 exploit amount, date, PeckShield attribution, auditors, bounty and same-day return) were confirmed by The Block and Decrypt, and claim_findings[6] (the October 2026 TVL collapse) was partly confirmed. Three of nine findings (the seed round, the PitchBook status and the 2023 all-time-high TVL) could not be checked because the sources blocked the reviewer or the data was truncated; these are left out of the percentage and are a coverage limit, not a defect of the page. The calculated dispute rate is 0%, but the review has an open high-priority coverage gap on the project's official 2026 status, the only current-status claim on the page, and reviewer confidence is moderate (0.55), so the verdict is a small revision rather than a plain approval. The only omission, a reported $75k bounty paid to the attacker, is minor and does not change the verdict.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":6,"sequence_num":14,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}