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
#2
Score
22 → 22 (0)
Cluster
mainnet-beta
Slot
464284144
Off-chain at
2026-11-01T23:54:06.612Z
Anchored at
2026-11-01T23:54:22.000Z
Block time
2026-11-01T23:54:22.000Z

Independent verification

1. Database (off-chain)
7KAMpv6MttZbWoCm2xwW1zkvDp2Tmy9xr2TWNopecghG
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1534 chars)
{"actor":"reviewer","artifact_identity":"aa23e1a9a587f4a4b44a5bf6a6b76699","blocked_count":1,"decided_at":"2026-11-01T23:54:06.544Z","decision":"review","disputed_pct":0.125,"findings_hash":"H7cKK1AqpkqnKeuuGnp2WDVstySfkg9cdAvHeX3rWPKM","investigation_id":"b678fb7e-aebd-4836-866a-b453c020a4ab","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":22,"page_content_hash":"a8eb52f755fb2fc8ac02d17ec2e4d933ac13de736e2ae450b8ea0d0ec30c7be4","page_slug":"syscoin-bridge","prev_score":22,"reason":"The core incident narrative matches the Syscoin postmortem, Rekt, Halborn and Cryptopolitan. This covers the June 7 date, the 5 billion SYS, the root cause, the 4B/1B split, the June 9 recovery address, the return and burn, and the paused bridge. Two defects were found. The summary says the Binance delisting came 'about two weeks' before the exploit, but sources and the page's own body say eleven days. The Market Impact section says Cryptopolitan reported 'months after the incident', but that article is dated June 17, 2026. The Binance dates could not be checked because BeInCrypto returned 403. The CoinDesk URL failed a direct fetch and its title does not match its content.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":8,"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}