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 · SIR.trading
- Sequence
- #3
- Score
- 38 → 30 (-8)
- Cluster
- mainnet-beta
- Slot
- 424157098
- Off-chain at
- 2026-06-04T02:54:28.338Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 6KQPD755JmpA3pqvaazrNgQ8dbiko285Gse7hT6mafc9
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1359 chars)
{"actor":"judge","decided_at":"2026-06-04T02:54:28.176Z","decision":"review_revise","investigation_id":"ec1b71e2-3ef9-41a8-8b3a-c9c84f52f244","new_score":30,"page_slug":"sir-trading","prev_score":38,"reason":"The page's core facts — the exploit date, mechanism, TVL drained, attacker and vault addresses, audit history, and team response — are well-supported across multiple independent sources. However, the review identified four issues requiring correction: claim_findings[18] disputes the attribution of researcher SupLabsYi to 'Sup Labs' when two independent sources confirm the firm is 'Supremacy'; timeline entry [7] carries a date of 2025-01-01 for the protocol relaunch, which is an impossible date given the exploit occurred in March 2025; timeline entry [3] cites a TVL upper bound of '$400,000' that is unsourced across all reviewed material; and claim_findings[16] notes that a key CoinTelegraph citation is a dead link (404). The lone formally disputed claim concerns a secondary contextual detail, not the exploit mechanism or loss amount. Penalty is set at the lower end of the 10–30% band given the high reviewer confidence (0.82) and the absence of any dispute touching the page's core allegations.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}