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 · Maya Protocol
- Sequence
- #4
- Score
- 28 → 28 (0)
- Cluster
- mainnet-beta
- Slot
- 457418157
- Off-chain at
- 2026-10-15T23:18:27.771Z
- Anchored at
- 2026-10-15T23:18:49.855Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 7XGj6ZtmugzMp1wZ5VDnnuuBwHf4Mz66tdrBTmJDsMyL
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1933 chars)
{"actor":"reviewer","artifact_identity":"380dc957b67fa470bcb0d683f130f818","decided_at":"2026-10-15T23:18:27.579Z","decision":"review","disputed_pct":0.2593,"findings_hash":"BV2mVCX8y3cj2e7jgy2JbkfxoBqs3U9LsWVTXMJR6kUK","investigation_id":"e892733a-1f37-4939-86a7-e4a859bbf6b0","mode":"findings_only","new_score":28,"page_content_hash":"6e31615e26248326f918cd1214a5828d65a3d250ed9cdb9e5ac4094544efa58f","page_slug":"maya-protocol","prev_score":28,"reason":"The page's reconstruction of the August 18, 2026 exploit mechanics, dollar figures, block numbers, BTC address, and CACAO price collapse holds up well against the primary technical write-up (Defimon) and independent news coverage (Decrypt, CoinDesk, Cryptopolitan, Cryip), and the Halborn 'Draft 3' ETH router audit status and Immunefi $35,000 critical-bounty cap were independently confirmed. However, two distinct factual errors were found and should be corrected: (1) the page asserts no team-authored post-mortem existed and credits an external analyst (Defimon) instead, which is contradicted by the page's own cited Decrypt article, which attributes the detailed bug/loss figures to the Maya team's own post-mortem report; and (2) the page conflates two separate shared-vulnerability narratives, attributing to the August 2026 Maya trade-account exploit a 'present in both codebases' claim that reporting actually made about the distinct May 2026 THORChain GG20 Threshold Signature Scheme flaw. A minor link-rot issue (a 301-redirected THORChain blog URL) was also found. The ~38 validators figure, the Halborn-carryover-findings claim, and the absence of regulatory action could not be independently verified. The page would benefit from a refresh given it is being reviewed roughly two months after its latest cited reporting.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}