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
- Sequence
- #4
- Score
- 12 → 12 (0)
- Cluster
- mainnet-beta
- Slot
- 457551077
- Off-chain at
- 2026-10-16T07:17:47.143Z
- Anchored at
- 2026-10-16T07:17:54.091Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- AtPqy1LNfZJF2d5EhzXHBkU1YWuT8MaE6wruu4dEc8Wz
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2273 chars)
{"actor":"reviewer","artifact_identity":"2f7bf501d8a44477d671770dfe55d604","decided_at":"2026-10-16T07:17:46.710Z","decision":"review","disputed_pct":0.24,"findings_hash":"7pobx2HfFU6CH7yJB9Hc7Fq1BqkeH8V4LX49cBBU4oG4","investigation_id":"c728ec71-a5d0-4641-9fd6-93840cd32777","mode":"findings_only","new_score":12,"page_content_hash":"90d463892293a830ddb9f2cbe7006dd1656d1a293ca2cb1220f4136eb7fa4515","page_slug":"supra-oracle-bonzo-lend-attack-vector","prev_score":12,"reason":"The core narrative — a Supra oracle verifier flaw (requireHashVerified_V2 accepting a zeroed BLS signature via an out-of-range committee ID), the resulting $9.05M Bonzo Lend exploit on July 11, 2026, the 11-chains-patched-before-Hedera disclosure, and the detailed attack timeline and financial impact — is well supported by the official Bonzo Finance incident report, rekt.news, Protos, and CoinDesk, and nearly every quote and figure checked against those primary/credible sources matched closely. However, the review found two misattributed 'verbatim' quotes presented in quotation marks that do not match the cited sources' actual wording (a fabricated Bonzo team quote in the Audit Gaps section, and a fabricated Tobkin quote about AI persistence in the Public Response section — though the underlying facts of that section, including the specific bounty terms and recovery address, are independently confirmed by rekt.news, just not by the three sources the page cites for that section). More seriously, the 'Oracle Dependency Transition on Hedera' section and its parallel timeline entry assert a March 2024 Chainlink-to-Supra migration that neither the cited source nor independent reporting (Hedera's own case study, QuillAudits) supports — reporting instead shows Bonzo running Chainlink and Supra concurrently for different assets. Entity-background details (Miami HQ, exact funding total, two of three co-founder names) could not be independently corroborated and showed some conflicting signals across low-tier aggregators. The page also omits a significant July 17, 2026 Bonzo restitution announcement that affects the net-impact picture.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}