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
- 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. - 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.
- 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 · CrossCurve
- Sequence
- #4
- Score
- 67 → 67 (0)
- Cluster
- mainnet-beta
- Slot
- 464267306
- Off-chain at
- 2026-11-01T22:54:05.130Z
- Anchored at
- 2026-11-01T22:54:22.000Z
- Block time
- 2026-11-01T22:54:22.000Z
Independent verification
- 1. Database (off-chain)
- At1kkM64Eae9CKSef3FS7kzrumtjK98d9PtgEBS32Tg3
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1468 chars)
{"actor":"reviewer","artifact_identity":"59875ea48ab91b727e0afcd7635cdb0e","decided_at":"2026-11-01T22:54:05.067Z","decision":"review","disputed_pct":0.25,"findings_hash":"BQP5bjwwYzi9uLsdcowffhyPKY6PjaamAiuQtk7hUFi3","investigation_id":"c18c86d7-2fb4-4de4-9c16-385555f1a0cb","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":67,"omissions":{"material":1,"total":1},"page_content_hash":"22881686e67211e0bbaef330f248d771d69dd3c91266557f2e46db1871ab40c1","page_slug":"crosscurve","prev_score":67,"reason":"The core narrative of the February 2026 bridge exploit (ReceiverAxelar access-control flaw, about $3M initially reported, about $1.4M liquid after an exchange froze minted EYWA, SafeHarbor 10% bounty) is supported by Halborn, QuillAudits and press coverage I fetched. Defects found: the QuillAudits post-mortem is dated 3 Feb 2026 but the timeline says March; the only source for the Hashlock audit now returns 410; a long chain list is not supported by the sources checked; and the page omits the later service restoration and old-bridge withdrawal mode. Several funding, TVL and aggregate-loss claims were not checked.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}