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.

Sequence
#2
Score
22 → 22 (0)
Cluster
mainnet-beta
Slot
464358086
Off-chain at
2026-11-02T04:18:08.964Z
Anchored at
2026-11-02T04:18:28.000Z
Block time
2026-11-02T04:18:28.000Z

Independent verification

1. Database (off-chain)
AGYpMCugtwqEJmx3MtHicyE2crsBumTdoaUkCuyLgc4v
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1334 chars)
{"actor":"reviewer","artifact_identity":"ea28413de2ed5a3a024dd51416e3981c","decided_at":"2026-11-02T04:18:08.913Z","decision":"review","disputed_pct":0.5714,"findings_hash":"HdjPKLa47MWDN1uwMfpYvc41hy2ZPDQpUYiE7XTGD9nx","investigation_id":"ef9d20ac-7b82-459a-84c2-2560148b7857","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":22,"omissions":{"material":0,"total":1},"page_content_hash":"7f48e20c2bcb6d854292789b492f31b1de4e365ec65e7f731bd6810ab5c17b84","page_slug":"onyx-protocol","prev_score":22,"reason":"The core facts check out against CertiK and Rekt: the Feb 2023 audit warning, the Nov 2023 $2.1M exploit and the Sep 2024 $3.8M exploit with its assets and addresses. One point is disputed: who reported the second exploit first. Several claims were not checked, among them the ETH amount, the vote count, the background history and the relaunch status. The page's status coverage may be out of date, since snippets suggest a 2026 Goliath mainnet launch, but I could not confirm that.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":2,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}