A deterministic evidence layer for on-chain control surfaces.

Who controls what, since when, what changed — answered from content-hashed chain evidence. Every answer is byte-reproducible, keeps valid-time and known-time distinct, and says plainly what is unknown.

byte-reproducible answers
content-hashed evidence
explicit unknowns
no scores · no hype

How it works

EXIT ingests chain state and events once, freezes them as content-addressed evidence, and answers control questions only from that frozen record. The same question always returns the same bytes — so an answer can be verified years later, by anyone, by recomputing its hash.

CONTROL STATE

response_content_hash: sha256:…

Who holds each authority of a program or mint now — holder account, multisig topology, since-when, with the evidence references inline.

CHANGE HISTORY

bitemporal · corrections preserved

Every observed authority transfer in a window — and what was knowable at any past moment, kept separate from what is true about it today.

ALERT FEED + DASHBOARD

window-independent alert ids

Authority changes as evidence-pinned alerts with stable identities, plus a read-only dashboard rendered byte-deterministically from the same record.

Boundaries — they are the product

A control-surface record is useful exactly as far as it refuses to speculate.

No risk scores, no severity, no recommendations.
No principal attribution — an address is never promoted to a person.
Absence is explicit: not_observed / UNKNOWN / WITHHELD.
A "no change" result is never claimed as proof nothing changed.
Corrections are appended, never erased.
Deterministic, replayable, LLM-free response engine.

Private alpha

A private alpha is open, and invitations are out to a small group of Solana security and operations teams. Coverage today is a pinned Solana reference set (program upgrade authorities, mint/freeze surfaces, Token-2022 admin roles) with repeated evidence cuts: every answer carries its evidence hashes, observation diffs are bounded and reproducible, and a clock-free freshness disclosure states exactly which subject was observed when. The engine itself is chain-agnostic; EVM control surfaces are the planned expansion. Access is tokenized and pseudonymous; a one-page mutual confidentiality note covers both sides.

Contact

Partnership / alpha inquiries: contact@exit-protocol.io  ·  X: @exitprotocolL