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
#3
Score
18 → 18 (0)
Cluster
mainnet-beta
Slot
443505876
Off-chain at
2026-08-08T03:56:37.585Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
EcaHdm6E6oGGJZdiirsrrS5XgSvwWfLTx1kK2kZujHxM
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1398 chars)
{"actor":"judge","decided_at":"2026-08-08T03:56:37.353Z","decision":"review_approve","investigation_id":"b3ddaae2-0b5a-442b-9961-ca72465cfe7a","new_score":18,"page_slug":"dlmc-token-bnb-chain-flash-loan-exploit","prev_score":18,"reason":"The reviewer found 0 disputed claims across 20 total, placing disputed_pct at 5% — well within the 0–10% approval band. All core financial and technical claims about the exploit (flash loan amount, block number, attacker addresses, price manipulation figures, net loss) were confirmed by at least two sources including Tier 1 on-chain data from BscScan (claim_findings[1], [3], [4], [5], [6], [7]). Five claims rated 'partially_supported' concern peripheral matters: the sequencing of who alerted first (claim_findings[13]), CertiK audit status where CertiK Skynet returned 404 (claim_findings[14]), inaccessible website marketing claims (claim_findings[15]), and two analytical inferences about renounced ownership and MLM-style risk patterns (claim_findings[19], [20]). None of these partial findings contradict the page's central allegations. Two high-priority coverage gaps remain — a missing exploit transaction hash and unverified CertiK audit — but gaps indicate expansion opportunities, not grounds for denial.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}