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 · Rubic
- Sequence
- #4
- Score
- 63 → 63 (0)
- Cluster
- mainnet-beta
- Slot
- 464365699
- Off-chain at
- 2026-11-02T04:45:24.119Z
- Anchored at
- 2026-11-02T04:45:40.000Z
- Block time
- 2026-11-02T04:45:40.000Z
Independent verification
- 1. Database (off-chain)
- 8tzrKSzxpN6DL6M8Qegz4KipSFW94B2Z2s3y5oSw8V4J
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1437 chars)
{"actor":"judge","artifact_identity":"6282d418755fe49db1cbd4182dae33ee","band_override":null,"blocked_count":1,"decided_at":"2026-11-02T04:45:23.830Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2222,"investigation_id":"88f93946-9f2c-4759-9f76-2b60c05315a3","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":63,"page_slug":"rubic","prev_score":63,"reason":"Of 9 checkable claims (one was excluded because its source blocked the reviewer), none were disputed and 2 could not be verified, giving about 22%, which falls in the minor-issues band. The core incident facts (November 2022 key compromise, December 2022 USDC exploit, Tornado Cash laundering, security overhaul) are supported by Tier 1 and Tier 2 sources. The unverified items are the founder-funded $5,000 compensation cap and 49-user figure (claim_findings[3]) and the year of the April 3 relaunch (claim_findings[5]); two further claims were only partly supported (claim_findings[1], claim_findings[4]). No omissions or status contradictions were reported, and the reviewer's confidence was moderate (0.55), so the penalty is kept at the low end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":9,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}