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 · EraLend
View on Solana ↗
Sequence
#3
Score
43 → 43 (0)
Cluster
mainnet-beta
Slot
464370474
Off-chain at
2026-11-02T05:02:24.413Z
Anchored at
2026-11-02T05:02:45.000Z
Block time
2026-11-02T05:02:45.000Z

Independent verification

1. Database (off-chain)
3JpzzHZyfTuaQRFeEn9uRYSJvXyyzKMDFkPgQffnEoJe
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1259 chars)
{"actor":"reviewer","artifact_identity":"9d7e6a9df54a922ad852a67b72c2f822","blocked_count":3,"decided_at":"2026-11-02T05:02:24.363Z","decision":"review","disputed_pct":0.3333,"findings_hash":"4hk2WKZgnLQexvhJw1Qobmk2UZtCRRDFvmAU3EhmhVDC","investigation_id":"58dfd95d-061d-4889-8631-bdb547d06e1a","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":43,"page_content_hash":"2f6a13f65afa80d96a74707b810fc672aeb262c731202a2fdf0087b3d63638e3","page_slug":"eralend","prev_score":43,"reason":"The core incident facts (July 25, 2023, ~$3.4M, read-only reentrancy, SyncSwap-derived code, PeckShield trusted-oracle assumption, attacker address) are supported by Rekt, CoinDesk and CertiK. Unsupported or unchecked are the Hacken multi-chain tracing, the marketing claim about avoiding external oracles, the August 2023 relaunch details and the current TVL (sources blocked). No outright disputed claims found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":9,"sequence_num":3,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}