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 · Symbiosis Finance BridgeV2 syBTC Exploit (September 2026)
- Sequence
- #4
- Score
- 29 → 19 (-10)
- Cluster
- mainnet-beta
- Slot
- 463286053
- Off-chain at
- 2026-10-30T12:31:24.328Z
- Anchored at
- 2026-10-30T12:31:32.000Z
- Block time
- 2026-10-30T12:31:32.000Z
Independent verification
- 1. Database (off-chain)
- 6PaThyWeqHAddee2UNAkxNfEK8UJMt3Vd9nCFJ2zo5xw
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2211 chars)
{"actor":"judge","artifact_identity":"dbbc8b91df076eafa6e9f84ae1e50f6c","band_override":null,"decided_at":"2026-10-30T12:31:24.076Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"2eb38693-7b58-462d-9a08-8698c50e40b4","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":19,"page_slug":"symbiosis-finance-bridgev2-sybtc-exploit-september-2026","prev_score":29,"reason":"The page's core facts hold up: the 330-satoshi deposit and 12 transactions, the 9.97 BTC (~$770,000) preliminary loss, and the ~15 BTC recovery and bounty were confirmed against independent outlets (claim_findings[2], [3], [4]). However, the page states that no post-mortem existed, while CoinDesk reports one was published on September 15, 2026. This also affects its framing of the root cause as disputed (claim_findings[0], omission_findings[0]). Two archive links for the CoinCentral and Blockonomi sources point to unrelated articles (claim_findings[5], [6]). The page also ends at September 17 and relies mostly on secondary news, so it needs the post-mortem, working archive links and a status update.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-10,"score_limit":{"applied":-10,"limited":false,"proposed":-10,"rule":"second_opinion_agreed","second":-12},"sequence_num":4,"severity_override":{"applied":true,"band":"minor","from_band":"approve","reason":"Counting only disputed and unverifiable findings gives 0 of 7 (0%), which would be the approve band. The review reports a material omission: CoinDesk says Symbiosis published a post-mortem on September 15, and the page says none existed and treats the root cause as disputed (claim_findings[0] stale, omission_findings[0]). Two high-priority coverage gaps are also open: no primary source, and nothing after September 17. The percentage understates this, so the verdict is escalated to the minor band. The core facts were confirmed and the subject_status does not contradict the page, so the significant band is not warranted."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}