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
- #6
- Score
- 56 → 56 (0)
- Cluster
- mainnet-beta
- Slot
- 464264659
- Off-chain at
- 2026-11-01T22:44:44.133Z
- Anchored at
- 2026-11-01T22:44:55.000Z
- Block time
- 2026-11-01T22:44:55.000Z
Independent verification
- 1. Database (off-chain)
- E6Xvu62rSuvLRVqsQ4fuS1RPRnr3EPzo4dztgbTDScLP
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1300 chars)
{"actor":"reviewer","artifact_identity":"493aa91e8b85b90259f2728d7c1434e3","decided_at":"2026-11-01T22:44:44.025Z","decision":"review","disputed_pct":0.25,"findings_hash":"C7epi53qjfwmUuCXmtwigBVUPwxC8Sca3K6iJjCnychr","investigation_id":"ec1b71e2-3ef9-41a8-8b3a-c9c84f52f244","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":56,"page_content_hash":"78ed5f54d62ce053accc8bcc7042e5353e116c91748528069c20345331d5e02a","page_slug":"sir-trading","prev_score":56,"reason":"The core narrative holds against Rekt, Cointelegraph and the protocol docs: launch Feb 20, 2025, $355K drained Mar 30, Railgun laundering, $100K bounty unanswered, single Egis audit, relaunch after four self-reported audits. Weak points are the unsourced September 2025 relaunch month, an unsourced Railgun-contact entry, and the framing of the North Korean candidate anecdote as community observation. I did not independently verify the technical exploit details or on-chain identifiers.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":6,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}