Skip to main content
Sign in
← avoid.net

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

  1. 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.
  2. 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.
  3. 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 · Starknet
View on Solana ↗
Sequence
#5
Score
45 → 62 (+17)
Cluster
mainnet-beta
Slot
426514651
Off-chain at
2026-06-14T23:16:07.363Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
J8VACYUPyygrqZYYxwekJAd1uzuGpjVfdKDC9pE4ytAr
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1601 chars)
{"actor":"judge","decided_at":"2026-06-14T23:16:07.256Z","decision":"review_approve","investigation_id":"60467ada-cfc0-4f9d-9b8c-1b4c334089c8","new_score":62,"page_slug":"starknet","prev_score":45,"reason":"The calibration review found zero disputed claims across all six claim findings (disputed_pct = 0%). The current score of 45 (WARNING band) is demonstrably too harsh: the largest loss event cited on the page — the zkLend $9.57M exploit (claim_findings[1]) — was a vulnerability in a third-party DeFi protocol built on Starknet, not a flaw in Starknet's own infrastructure, confirmed by Halborn and BlockSec post-mortems. The airdrop controversy and token unlock dispute (claim_findings[2] and claim_findings[3]) reflect governance friction with no user fund loss, and StarkWare's positive response — voluntarily reducing the April 2024 unlock from 13.4% to 0.64% — is noted by the reviewer as evidence of responsive governance. Starknet achieved L2Beat Stage 1 decentralization in May 2025 (claim_findings[4]), a material positive milestone inconsistent with a WARNING classification. A score of 62 (CAUTIONARY band) appropriately reflects real residual concerns — 99% revenue decline from peak, two network outages in 2025-2026, ongoing sequencer externalization, and token unlock opacity (claim_findings[5] and claim_findings[6]) — without conflating ecosystem-level incidents with entity-level fraud. Page content is accurate and remains published.","score_delta":17,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}