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 · Symbiosis Finance
- Sequence
- #3
- Score
- 52 → 52 (0)
- Cluster
- mainnet-beta
- Slot
- 464260104
- Off-chain at
- 2026-11-01T22:28:12.786Z
- Anchored at
- 2026-11-01T22:28:36.000Z
- Block time
- 2026-11-01T22:28:36.000Z
Independent verification
- 1. Database (off-chain)
- 9r72cXS5iawr8viS7HxnvQhYL5pR3niWFJutKp3BcSjd
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1350 chars)
{"actor":"reviewer","artifact_identity":"17d7d15177f4b7aa754944ecdb38a18b","blocked_count":2,"decided_at":"2026-11-01T22:28:12.720Z","decision":"review","disputed_pct":0.1,"findings_hash":"HVwsRdodoRa2a7BeQa1oxHgzJSN4cYx8MrT7JpE7SV92","investigation_id":"bdc18c4c-62c3-49e1-9b70-70ad4505be14","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":52,"omissions":{"material":0,"total":2},"page_content_hash":"b448d575458af33773cfa7203baec2b2a65287b5b5ef4a978b118d8d78918f86","page_slug":"symbiosis-finance","prev_score":52,"reason":"The core exploit narrative (date, mechanism, $336K proceeds, 9.97 BTC loss estimate, 15 BTC recovery, 20% bounty, bridge offline) matches the sources I read. Weaker points are the funding and team background details, which cited sources do not support or which were blocked. The Sept 11 date on the rerouting timeline entry is doubtful, and the page contradicts itself on whether the post-mortem had been published. Nothing newer than mid-September was found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":10,"sequence_num":3,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}