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 · ZKsync
- Sequence
- #2
- Score
- 38 → 38 (0)
- Cluster
- mainnet-beta
- Slot
- 426514530
- Off-chain at
- 2026-06-14T23:16:01.138Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- Gn9trVgWC1CTCYHJa68FkuLaBo7fr4fAv1uUB3DDEFn7
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1830 chars)
{"actor":"reviewer","decided_at":"2026-06-14T23:16:01.082Z","decision":"review","investigation_id":"9d227bdb-3345-4be5-aa9a-d03dcf819c80","new_score":38,"page_slug":"zksync","prev_score":38,"reason":"Blue-chip calibration review (Prompt A). Verdict: over-penalized. Page content is treated as accurate; the trust_score band is miscalibrated. ZKsync is a legitimate Ethereum Layer 2 scaling protocol operated by Matter Labs, a well-funded company ($458M raised from credible institutional investors) with no fraud conviction, no exit-scam mechanics, and no Ponzi structure. Every material incident documented on the page — the airdrop admin key exploit, the Upbit price manipulation, the X account breach — was either suffered by ZKsync (external attacker) or occurred on a third-party platform. The airdrop exploit, the most serious event, was largely remediated: core user funds were never at risk, and ~$5.7M was recovered via safe harbor. The pending BANKEX civil lawsuit is unresolved and denied by Matter Labs; it does not constitute a finding of wrongdoing. The airdrop controversy (poor Sybil filtering, post-launch sell-off) reflects governance and product-quality weaknesses rather than fraud. Under the post-policy band semantics, WARNING (20–49) is reserved for entities with elevated fraud/loss risk or unresolved severe incidents; ZKsync fits CAUTIONARY (50–69) — a legitimate operator with material caveats including the unresolved IP lawsuit, documented operational-security shortcomings (two key compromises in one month), and persistent ecosystem engagement decline. A score of 57 reflects these caveats while correctly not punishing the entity for incidents it suffered.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}