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 · SIR.trading
- Sequence
- #2
- Score
- 38 → 38 (0)
- Cluster
- mainnet-beta
- Slot
- 424157093
- Off-chain at
- 2026-06-04T02:54:28.285Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 78NDnCeBSg3ZsvrmJh4Gk3aFZQkVMdEQkuaD8XmqCT88
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1050 chars)
{"actor":"reviewer","decided_at":"2026-06-04T02:54:28.176Z","decision":"review","investigation_id":"ec1b71e2-3ef9-41a8-8b3a-c9c84f52f244","new_score":38,"page_slug":"sir-trading","prev_score":38,"reason":"The investigation is substantively accurate on its core claims — the exploit date, mechanism, TVL amount, attacker and vault addresses, audit history, team response, and relaunch status are all supported by independent sources. Key issues identified are: (1) the researcher firm is misidentified as 'Sup Labs' when it is 'Supremacy'; (2) the relaunch timeline entry carries an erroneous date of 2025-01-01; (3) the upper TVL bound of $400k cited in one timeline entry lacks sourcing; (4) the North Korean job candidate detail could not be independently verified; and (5) one CoinTelegraph URL returned 404. The exploit technical description is highly accurate based on two independent security analyses.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}