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 · Meter
View on Solana ↗
Sequence
#6
Score
60 → 60 (0)
Cluster
mainnet-beta
Slot
464266563
Off-chain at
2026-11-01T22:51:21.397Z
Anchored at
2026-11-01T22:51:43.000Z
Block time
2026-11-01T22:51:43.000Z

Independent verification

1. Database (off-chain)
8cARwAk2TRFi3CuXADgtrLDCV5g9LJFHWxBK7ccJmqg4
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1806 chars)
{"actor":"judge","artifact_identity":"46fd1bf2b310a7ed6f45a263433938c9","band_override":null,"blocked_count":1,"decided_at":"2026-11-01T22:51:21.181Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4,"investigation_id":"981f6d35-bdda-4b2f-9388-c7ccdb8e7521","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":60,"page_slug":"meter","prev_score":60,"reason":"Of the five scored claim findings, two could not be verified (claim_findings[1], the May 2026 price, and claim_findings[4], the 77% local price drop), and one is stale (claim_findings[0]). Counting only unverifiable and disputed findings gives about 40%, which is the significant band. The core 2022 exploit account is confirmed by rekt.news (claim_findings[2], [3]). The page omits a second exploit on 2026-09-23 and the pause of Meter's mainnet and bridge (omission_findings[0], [1]), and its statement that the bridge was continuing contradicts the current status. One finding was blocked by the source (claim_findings[5]) and is a coverage limit, not a defect. The verdict is not deny because the 2022 narrative holds up and the update rests on tier-3 reports.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":5,"sequence_num":6,"severity_override":{"applied":true,"band":"significant","from_band":"significant","reason":"The review reports a critical omission (the September 2026 second exploit of Meter Passport and the pause of mainnet and bridge) and subject_status.contradicts_page is true. The page says the bridge was continuing at reduced scale. Judged at the significant band at minimum."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}