Signer transparency
AVOID.NET anchors every editorial decision and a daily heartbeat on Solana. The keypairs below sign those memos. Anyone can take the public keys, paste them into a Solana explorer, and verify our on-chain history directly — without trusting anything we say on this page.
Decision publisher
Signs every state-changing event for an investigation page: accept, reject, correction, update, revoke. One memo per event.
SOLANA_PUBLISHER_PUBKEY on the deploy).Heartbeat
One memo per day from the same publisher key, signed even on quiet editorial days. A gap in heartbeats is a publicly visible signal that the system stopped — we cannot silently turn it off.
Memo schema
Every memo committed by the publisher key follows one of these canonical formats. Anyone parsing our on-chain history can rely on the version prefix and field ordering.
AVOID.NET|v1|h:<sha256-base58>|d:<event-id>|t:<iso-utc>AVOID.NET|v1|h:<sha256-base58>|d:hb:<iso-date>|t:<iso-utc>Verify offline
The cleanest verification doesn’t involve avoid.net at all. Clone the repo, point at any decision event id, and the CLI re-derives the canonical hash from the database row and confirms it matches the on-chain memo at the disclosed signature.
python -m src.verify_decision <event_id>Why this page exists. Trust intelligence platforms make claims; most can’t be checked. Pasting our publisher pubkey into Solana Explorer should show the same anchor signatures listed here — and a steady drip of heartbeats. If we ever stop signing, that gap will be visible on-chain forever, regardless of what avoid.net itself says.