Skip to main content
AVOID.NET
← 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_revise · ZetaChain
View on Solana ↗
Sequence
#3
Score
4258 (+16)
Cluster
mainnet-beta
Slot
443508515
Off-chain at
2026-08-18T20:31:16.743Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
8TWaHg2Uw6skEryTJV2mKy4TpJNNbUWiEATQZqToLeCG
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2027 chars)
{"actor":"judge","decided_at":"2026-08-18T20:31:16.494Z","decision":"review_revise","investigation_id":"2f6eca6d-bddc-4eeb-9bac-ad83f94cb1b8","new_score":58,"page_slug":"zetachain","prev_score":42,"reason":"The reviewer's incident classification is correct and the current score of 42 (WARNING) does not match the entity's conduct under the rubric. The page's flagship incident, the $334K GatewayEVM exploit, is a suffered hack against ZetaChain's own operational wallets by an external, premeditated attacker (calibration_assessment.incident_attributions[0], attribution 'b') — no external user funds were lost, the team paused operations within minutes, disclosed promptly, and shipped a patch. Per the rubric, a suffered primary incident caps the band at CAUTIONARY (50-69) regardless of the negligent bug-bounty triage failure, which is culpable but does not amount to own-fraud. The other flagged items — the disclosed sybil-reward airdrop policy and TSS/validator-concentration risk (attributions 'a') — are legitimate but minor own-conduct concerns, not fraud, and correctly argue against a top-of-range score rather than against CAUTIONARY itself. The PCRisk/ScamAdviser phishing-site findings (attribution 'c') describe brand impersonation by unrelated third parties and should carry near-zero weight under the anti-conflation rule; nothing in the current 42 appears explainable by that section carrying disproportionate negative weight, but it should not be allowed to anchor the score down further. A mid-CAUTIONARY score of 58 appropriately reflects: no user losses, rapid remediation, and prompt disclosure (positive), weighed against real negligence in dismissing the prior bug report, ongoing token-price deterioration now worse than the page states, and an unaddressed business-model pivot away from cross-chain bridging that signals continuing uncertainty (negative).","score_delta":16,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}