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 · Garden
- Sequence
- #4
- Score
- 26 → 26 (0)
- Cluster
- mainnet-beta
- Slot
- 464267157
- Off-chain at
- 2026-11-01T22:53:48.982Z
- Anchored at
- 2026-11-01T22:53:50.000Z
- Block time
- 2026-11-01T22:53:50.000Z
Independent verification
- 1. Database (off-chain)
- 5MyMNmyU5mbZC44PntYcyFmKFVtfBA6WRKmnhiYA3acM
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1298 chars)
{"actor":"reviewer","artifact_identity":"d2efd5cdd48c4a7fbb2e79bca5992aed","decided_at":"2026-11-01T22:53:48.916Z","decision":"review","disputed_pct":0.25,"findings_hash":"UPfDPGyeUAQfxNsayAxRo9kqSLAAyBjLjRXKmpJwf5c","investigation_id":"af469430-2d96-4ad7-80a1-b893bf5d3479","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"omissions":{"material":1,"total":2},"page_content_hash":"dce1fe3cd07efe2c130383d2b66ff7b19e363715f48a55983b0850214ca362e7","page_slug":"garden","prev_score":26,"reason":"The October 2025 incident, forensic findings and attribution match the sources I fetched, although the forensic report is a sponsored press release. The Companies House link looks like an unrelated company, and several lineage and launch-date claims are unsupported by their cited sources. The page misses a July 2026 second exploit and app pause, so it is stale on the subject's current status. Many cited sources were not fetched, so coverage is partial.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"subject_status":"exploited","subject_status_contradicts_page":true,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}