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 · Mint Blockchain
View on Solana ↗
Sequence
#4
Score
50 → 50 (0)
Cluster
mainnet-beta
Slot
462180805
Off-chain at
2026-10-27T18:58:58.452Z
Anchored at
2026-10-27T18:59:16.000Z
Block time
2026-10-27T18:59:16.000Z

Independent verification

1. Database (off-chain)
GyycPPz58VMPkTkQzmiKMwCgLchF7L22qT4visds3iNA
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1833 chars)
{"actor":"judge","artifact_identity":"8e644470b7d460a0c3826256adca9d37","band_override":null,"decided_at":"2026-10-27T18:58:58.188Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3333,"investigation_id":"ebc44c52-64d7-4c4d-a590-9d88e7832bea","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":50,"page_slug":"mint-blockchain","prev_score":50,"reason":"Of 14 checked claims, 1 was disputed (claim_findings[8], the $42,110 TVS figure, which the cited L2BEAT page does not show) and 4 could not be verified (specific launch day, no-official-explanation claim, PCRisk date, October 2023 start), giving about 36%, the significant-issues band. The core shutdown facts are confirmed, but the page presents the October 20, 2026 withdrawal deadline as upcoming when it has passed (claim_findings[1] and [2], omission_findings[1]). It also omits L2BEAT's report that bridge contracts were upgraded in April 2026 to let a multisig drain funds, while describing an orderly wind-down (claim_findings[10], omission_findings[0]). The page needs revision rather than denial because the main facts hold and the reviewer's confidence is moderate (0.7).","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"severity_override":{"applied":true,"band":"significant","from_band":"significant","reason":"The review reports two material omissions (the April 24, 2026 multisig drain-function upgrade, and the passed October 20 withdrawal deadline) and subject_status.contradicts_page is true. The percentage band is already significant, so the page is judged in that band, with the penalty set in its upper half."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}