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
- #7
- Score
- 56 → 56 (0)
- Cluster
- mainnet-beta
- Slot
- 464264664
- Off-chain at
- 2026-11-01T22:44:44.308Z
- Anchored at
- 2026-11-01T22:44:56.000Z
- Block time
- 2026-11-01T22:44:56.000Z
Independent verification
- 1. Database (off-chain)
- BUoQke97S7UtZoQzFN9K6BUwL19ifCgPSf3pR6MUWezH
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1439 chars)
{"actor":"judge","artifact_identity":"493aa91e8b85b90259f2728d7c1434e3","band_override":null,"decided_at":"2026-11-01T22:44:44.025Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.25,"investigation_id":"ec1b71e2-3ef9-41a8-8b3a-c9c84f52f244","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":56,"page_slug":"sir-trading","prev_score":56,"reason":"The core account holds up: launch date, the $355K exploit on March 30, 2025, Railgun laundering, the $100K bounty offer and the single prior audit were all confirmed by Tier 1 and Tier 2 sources (claim_findings[0-3, 5]). Two of eight claims could not be verified: the September 2025 relaunch month (claim_findings[6]) and the April 2025 Railgun-contact entry (claim_findings[7]), which has no source. A third claim, about community observers and the North Korean candidate story, was only partly supported (claim_findings[4]). That puts the unverified share at 25%, in the minor band. The penalty is kept at the light end because no core allegation is disputed, there are no omissions, and the protocol is reported as operating with no contradicting status. The reviewer's confidence is moderate.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":7,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}