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
- Sequence
- #4
- Score
- 52 → 52 (0)
- Cluster
- mainnet-beta
- Slot
- 464260109
- Off-chain at
- 2026-11-01T22:28:12.953Z
- Anchored at
- 2026-11-01T22:28:37.000Z
- Block time
- 2026-11-01T22:28:37.000Z
Independent verification
- 1. Database (off-chain)
- EMFg4n1MxEXbAvjos3C2wZdN6WvBNaB2tGrKMMsKN5Wt
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1574 chars)
{"actor":"judge","artifact_identity":"17d7d15177f4b7aa754944ecdb38a18b","band_override":null,"blocked_count":2,"decided_at":"2026-11-01T22:28:12.720Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1,"investigation_id":"bdc18c4c-62c3-49e1-9b70-70ad4505be14","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":52,"page_slug":"symbiosis-finance","prev_score":52,"reason":"The core exploit account (date, mechanism, $336,000 proceeds, 9.97 BTC loss estimate, 20% bounty, bridge offline) was confirmed by the sources the reviewer read. Of 10 countable claim findings, 1 was unverifiable (claim_findings[9], the founders' Russia-based status and prior employers, which the cited LI.FI page does not support), giving a disputed share of 10%, at the edge of the approve band. Three further claims were only partly supported: the Sept 11 date on the rerouting entry (claim_findings[4]), the page contradicting itself on whether the post-mortem was published (claim_findings[6]), and the March 2022 launch date (claim_findings[8]). A high-priority coverage gap, nothing reported after mid-September 2026, tips the result to a minor revision. Two findings were blocked sources (claim_findings[7] and [11]) and are excluded as a coverage limit, not a defect of the page.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":10,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}