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_approve · Dango
- Sequence
- #3
- Score
- 52 → 52 (0)
- Cluster
- mainnet-beta
- Slot
- 425433450
- Off-chain at
- 2026-06-10T00:07:42.808Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- DikWDRN2VJVXtvDvdQZaZbcBk4F1UqZnyX6UzixHdoJ6
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1257 chars)
{"actor":"judge","decided_at":"2026-06-10T00:07:42.617Z","decision":"review_approve","investigation_id":"79a41b54-63cf-4342-8c1b-516bf780f51d","new_score":52,"page_slug":"dango","prev_score":52,"reason":"All 12 claims reviewed returned zero disputed findings. Nine claims are fully confirmed by multiple independent sources; three are partially supported but involve only minor imprecision — an investor entity name variant (Delphi Labs vs. Delphi Ventures, claim_findings[2]), an uncertain campaign start date (claim_findings[10]), and an unverified specific post-exploit resume date (claim_findings[11]). The core factual record — the $3.6M seed round, the April 13 2026 sign-error exploit draining $1.9M USDC, the $410,010 bridged to Ethereum, chain pause with SEAL-911 engagement, and white hat full fund return — is confirmed across multiple credible sources. Three high-priority coverage gaps (missing on-chain transaction hashes, no official team postmortem, and empty section content fields) indicate the page needs substantive expansion but do not constitute factual failures warranting revision or denial.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}