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 · GoldPesa
- Sequence
- #2
- Score
- 32 → 32 (0)
- Cluster
- mainnet-beta
- Slot
- 461979000
- Off-chain at
- 2026-10-27T07:03:32.756Z
- Anchored at
- 2026-10-27T07:04:00.000Z
- Block time
- 2026-10-27T07:04:00.000Z
Independent verification
- 1. Database (off-chain)
- GfMLvsrbi5Kk5jPScsryteYiWv9Y1GBVQyzZtvnNBwig
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1572 chars)
{"actor":"reviewer","artifact_identity":"b8a2ad3dcbb0ecfe4c6173ffec9fa507","decided_at":"2026-10-27T07:03:32.482Z","decision":"review","disputed_pct":0.2308,"findings_hash":"7FSnuvLaCUqMMXmQxUTHgawwuFtgf4JpY6jWB94p4PYS","investigation_id":"a1739ade-02c2-4d3c-8080-0ebe7b72b112","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":32,"omissions":{"material":0,"total":1},"page_content_hash":"da4bef654d5368f0cf7371947301be7fc26ae53571b28eb0832b1791378c1a02","page_slug":"goldpesa","prev_score":32,"reason":"The core exploit story (GPXHooks on Base, about $114K to $114.9K, Oct 2 2026, flash-loan-assisted delta-accounting flaw, zero volume afterward) is corroborated by several outlets. Granular details such as the tx hash, addresses, timestamp and exact deltas could not be verified because the primary sources were blocked or unreadable. Background claims are weakly sourced: the Yahoo and BeInCrypto references are a 2021 release about a different token (GPO, on Ethereum), and the October 2025 Base launch date, the 1 gram peg and the CertiK audit claim are not supported by any source I could fetch. The 2013 timeline entry overstates 'established' where the source says 'licensed since'. No later change in status was found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":2,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}