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 · MyAlgo
- Sequence
- #3
- Score
- 50 → 50 (0)
- Cluster
- mainnet-beta
- Slot
- 464287591
- Off-chain at
- 2026-11-02T00:06:34.522Z
- Anchored at
- 2026-11-02T00:06:38.000Z
- Block time
- 2026-11-02T00:06:38.000Z
Independent verification
- 1. Database (off-chain)
- CaTkjZtfVAWuVcthWSbpX1WVhtGFEFCBTqUVPoAcB2Df
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1329 chars)
{"actor":"reviewer","artifact_identity":"df880c17ad1cfad383b404236bdbf9ed","decided_at":"2026-11-02T00:06:34.457Z","decision":"review","disputed_pct":0.4,"findings_hash":"B3bQaW9JLaaTKLBhQD5Dj9F1mGb6hAfafu3n3yLzyenQ","investigation_id":"ebc658cd-7c9c-41a8-8ed3-dc7183c90a16","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":50,"page_content_hash":"4f49c5e4ec619b406af3803a4c465e3de5335d5dfe729b9122a283259ed38df3","page_slug":"myalgo","prev_score":50,"reason":"The core incident is real and well documented: a roughly $9.6M theft, the 19.5M ALGO and 3.5M USDC split, and the March 5, 17 and 31 wave dates all check out. The Foundation notice date also checks out. Problems are a timeline entry that presents a cumulative total as a single first-wave figure, an unconfirmed TRM Labs attribution, a CDN date that D13 does not support, and a shutdown date (Jan 30, 2024) that rests on a dead Bitget link. The page does state that MyAlgo shut down, consistent with the available evidence.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"shut_down","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}