EXEvery conclusion has a route back.
Connect a supported answer to its source identity, scope and time. Preserve conflicting observations and later corrections. A result becomes a starting point for deeper investigation.
BLOCKCHAIN RESEARCH & MONITORING
Make blockchain activity intelligible.
A research infrastructure for understanding what happened, who could act and what changed—with evidence you can inspect. Starting with control and change analysis. Building toward connected investigations across blockchain networks.
EXIT shows who can control a token or contract on Solana and Ethereum, what changed, and when we knew — with the on-chain evidence attached. For security teams, auditors, developers and careful holders.
Use free research ↗Explore recorded cases ↓Read the illustrated whitepaper ↗No wallet or token required. Open the free research interface or inspect the recorded cases.
FROM QUESTION TO EVIDENCE01—05
ASSET / PROGRAMObject → control surface
↓ACCOUNT / PROGRAMAuthority + execution conditions
↓INSPECTABLE SUPPORTSource + content identity
↓Two distinct timesWhen was it true? When was it known?
LIMIT
An address alone does not identify a person or institution.
THE BIG PICTURE / A RESEARCH INFRASTRUCTURE
Connect the activity. Keep the evidence.
The goal is a connected research environment for people, software and organizations. Every new capability must make a real investigation clearer, more reliable or less costly.
QUESTION → SCOPE → EVIDENCE → TIME → RESULT
Move from isolated transactions to a connected body of evidence: authority, events and observed fund relationships, with source conflicts and missing history kept visible.
Grow beyond one asset or network.
Extend typed authority, event and observed flow relations through tested adapters. Cross-chain relationships need an explicit binding; similar addresses or simultaneous activity are not enough.
Turn signals into investigations.
Develop bounded monitoring and anomaly modules with labelled evaluation, false alarms and missed events. A signal prioritizes a question; it does not prove intent or identify a person.
WHY THE TIME MODEL MATTERS
The same question can have two honest answers at two knowledge cutoffs.
An authority change may occur at 10:00 and become observable to EXIT at 13:00. A query asking what EXIT knew at 12:00 must not borrow the later evidence.
A(q, tvalid, tknown)
= evaluation of eligible, identified evidenceSynthetic example, not a measurement. A content hash binds bytes; it does not establish truth by itself.
= evaluation of eligible, identified evidenceSynthetic example, not a measurement. A content hash binds bytes; it does not establish truth by itself.
A FINITE FIRST SERVICE / CONTINUING DEVELOPMENT
Launch is a milestone in the engineering program.
The quota-limited free service is open and EXITP was created on 25 October 2026. Paid API Pass integration is a separate later release. Develop the next capabilities through relative three-month planning windows after the actual launch date, T0 (25 October 2026). Future quarters are not additional first-release conditions.
A clearer research workflow
Saved context, supported question planning, comparisons and service measurement.
Exit: a fixed task bank improves completion, user effort or cost against the first-service baseline.A temporal research graph
Typed evidence-backed relations and selective expansion to additional networks or surfaces.
Exit: paths replay, hostile wrong-join controls pass, and coverage/finality/cost meet the declared profile.Measured monitoring
Bounded anomaly investigations, replayable timelines and transparent detection quality.
Exit: held-out labels report false alerts, misses, precision/recall, latency and cost.Organizational workflows
Permission-scoped workspaces, integrations and reproducible report delivery.
Exit: isolation, revocation, restore and declared capacity pass; evidence conclusions remain payment-independent.Broader coverage. Faster investigation. More reliable answers.
Growth is judged on the same tasks: accuracy, completion, reproducibility, latency and cost. A method that adds complexity without measurable benefit is revised or stopped.
YOUR QUESTION → A DECLARED SCOPE → INSPECTABLE EVIDENCE
Start with a question.
Find a recorded case or prepare a new research brief. The public desk does not compute live answers.
A brief is a local draft, not an accepted investigation or a promised answer.
01 / RESEARCH DESK
From question to source.
Select a case. Follow the answer to its supporting observations.
Loading recorded cases…
RECORDED OBSERVATION
An EXIT-authored public case note. It is not the original API response or a complete raw-evidence export.
Inspect the recorded source identities below. Explorer links aid inspection; their current pages do not independently prove a historical snapshot.
VALID TIMEWhen on the chain?
The recorded block, slot or event time.
KNOWN TIMEWhen did EXIT know?
When evidence became available to the system. Later knowledge is not moved into the past.
Translations help presentation. Source identifiers and original technical records remain unchanged; English is the primary explanatory version.
PUBLIC NOTE FILE SHA-256
02 / METHOD
Look behind the claim.
01
Record
Keep the question, chain position, acquisition time and content identity together.
02
Distinguish
An account is not a person. Source conditions are not proof of runtime execution. Unknown is not absent.
03
Re-examine
Show changes and corrections without erasing history. Replay tests faithful reproduction, not universal truth.
A precise question. An explicit limit.
EXIT researches declared control surfaces. It does not promise safe investments, price prediction, every blockchain or the detection of all manipulation.
03 / FIND THE EVIDENCE
One address. Which conclusion?
A synthetic learning exercise, separate from the real cases above. No points, rewards or payment.
SYNTHETIC / 01
A record identifies address A as upgrade authority at block 12,000,000. What does that record establish?
04 / ONE RESEARCH ENGINE, THREE USES
One engine. Inspectable answers.
FOR PEOPLE
Research interface
Inspect supported permissions, changes, evidence and unknowns. These public examples require no wallet.
FOR BUILDERS
API
One free key for live control reads of Solana token mints and Ethereum contracts, research records for questions that cannot be answered yet, and watches you check on request. Get your key at api.exit-protocol.io; the API guide, OpenAPI description and agent tools are public.
FOR RE-EXAMINATION
Case notes & evidence packages
Download these public notes. Full replay packages require separate data-sharing clearance and are not included here.
FUTURE DESIGN
Optional API Pass
An optional token-to-service-credit integration is planned. EXITP exists, but buying or holding it does not currently redeem credits or activate a paid API Pass. The free API requires no token. Actual paid serving, chain rehearsal and final paid-security acceptance remain separate work.
Case texts and the overview are available in eight languages. The vision pillars, the quarter plan and the illustrated paper are English-first.
THE ROAD AHEAD / DELIVERED → NEXT → LONG HORIZON
From a verifiable answer
to connected investigations.
A public development map: what works today, what we are building next, and how each step is tested. Our post-launch growth program is measured in outcomes, not promises.
01 / FOUNDATIONControl + evidence + timeDelivered within declared scope02 / LIVE SERVICEYour Solana token → an evidence trailFree early access · 25 Oct–24 Nov 202603 / BUILDING NEXTResearch that can be saved and continuedResearch records · comparisons · change monitoring04 / NORTH STARA verifiable blockchain research layerConnected evidence for people, software and organizations
Explore the full visual roadmap ↗Q1–Q4 are planning windows after the 25 Oct 2026 token milestone. Planned capabilities are not delivered features or guaranteed dates.
DELIVERED / IN DEVELOPMENT / NEXT
A first release. Then continuous evolution.
A finite useful release is a milestone. It does not mean development stops.
Public research desk
Recorded public notes, evidence identities, time boundaries, downloads and an offline edition. Free to inspect. No wallet.
Free research API · open
Open 25 October–24 November 2026, 12:38:20 UTC. A single 30-day campaign: 20 completed answers and 60 attempts per account per UTC day; 300 service-wide attempts per UTC day. No wallet, token purchase or automatic payment.
API Pass
A private redemption and credit-accounting prototype exists. It is not the live free service and does not make EXITP redeemable today. Production integration, actual chain/wallet rehearsal and final paid-security acceptance remain open.
Free service open. EXITP identity published. Development continues.
EXIT Protocol created EXITP on 25 October 2026 through Jupiter Studio (Meteora Dynamic Bonding Curve) on Solana; the official mint is shown above. The free API opened the same day at 12:38:20 UTC. Paid token redemption is not live. The creation was a manual wallet action outside EXIT's services; product evidence and conclusions remain independent of token activity.
Current coverage and what comes next
| Surface | Public access | Boundary |
|---|---|---|
| Solana · any token mint | Free API: live read at a finalized block · one recorded case note (PYUSD) | Mint, freeze and supported Token-2022 authorities and holder accounts; not an arbitrary wallet investigator. |
| Ethereum · any contract | Free API: live read at a finalized block · two recorded case notes (USDC, PYUSD) | Proxy implementation and admin slots and the owner() getter, read as observations; not a full permission audit. |
| Research records, watches and graph | Free API, your own key | Records for questions that cannot be answered yet; watches you check on request; a graph that joins up to four of your own answers. Automatic webhook alerts are a limited pilot: one watched subject service-wide, read hourly. |
| Evidence log | Public: exit-protocol.io/log/ | Append-only and anchored on Solana once a day, with a standalone verifier. known_at is EXIT's own statement; an anchor bounds it from above. |
| Control Map | Public: exit-protocol.io/control-map/ | Who holds the control roles of the largest tokens on Ethereum and Solana at one finalized slot or block; every answered row is a log record. No score, no verdict. |
| Case study · Drift, 1 April 2026 | Public write-up: repository ↗ | What the chain showed before the admin takeover, re-read from Solana mainnet on 27 October 2026. |
| Solana launchpad and liquidity markets | Future scoped research | Creation, trades, liquidity and public narrative need distinct evidence. No manipulation verdict or person identity from a wallet alone. |
| Additional blockchain networks | Not delivered here | A chain-specific adapter and tested provenance are required. EVM compatibility is not automatic coverage. |
USING EXIT / CLEAR EXPECTATIONS
Start with the right question.
What you can use today, what needs access, and how the research program grows.
Can I type any blockchain question and get a live answer?
This desk searches recorded cases and creates local drafts. The separate free service at api.exit-protocol.io reads any Solana token mint or Ethereum contract live at a finalized block, opens a research record when a question cannot be answered yet, and lets you watch a mint or contract for changes. Free-form prose questions and open-ended wallet investigations are not offered.
Do I need a wallet or token?
No. Free research access requires no wallet, blockchain token, name, email or payment. The campaign is open until 24 November 2026, 12:38:20 UTC, subject to quotas and service capacity. Paid API Pass redemption is separate future work.
What does no answer, no charge mean?
In the private API Pass prototype, a primary supported question that remains unanswered consumes no research credit and receives a bounded follow-up record. This does not promise an automatic investigation or eventual resolution. A completed answer must show its evidence and time scope; payment cannot alter its conclusion.
What develops after the first release?
Some first steps are already live in the free service: a bounded research graph that joins up to four of your own answers, research records, and automatic watch alerts as a limited pilot (one watched subject service-wide, read hourly). The planned program widens research workflows, the temporal graph, measured monitoring and organizational integrations. Each increment has measurable acceptance criteria; none implies that all networks are supported.
How do I report an issue or discuss an integration?
Use the public issue templates for reproducible website or documentation problems. Never post sensitive findings, credentials or personal information in a public issue; a verified private intake channel is not offered yet. No response deadline or bounty is promised. Public issue templates ↗
BUILD WITH THE EVIDENCE
For developers and research teams.
Use the open free research interface, integrate its structured API, or inspect the public authored case files. Each has its own declared coverage.
Public case files · free
curl https://exit-protocol.io/solana-pyusd.jsonJSON case-note format: answer, selected observations, source links, time information and limits. This is not the original engine response or a full replay export.
Download the example JSONStructured research API · free early access
GET /v0/research/solana/mint?mint=…
GET /v0/research/ethereum/contract?address=…
GET /v0/research/records
GET /v0/research/watch
GET /v0/control_stateGet a free key at api.exit-protocol.io and send it as a bearer token, never in a URL or a public report. Live reads answer at a finalized block with their sources and stated limits; recorded subjects answer at declared times. This is bounded research, not an open-ended AI investigator.
API scope and access status ↗CURRENT DECISION / 25 OCTOBER 2026
Jupiter Studio · Meteora DBC · Solana
EXIT Protocol created EXITP on Solana on 25 October 2026. The official mint is 5vPz2s8NtkasmVRDz5ySz27V1E8UdSpzqc9xN678jups. The free service is now open; token payment is not live. Use the exact address to identify the asset.
Open free research ↗ Verified official Studio page ↗
Jupiter’s published graduation and fee model ↗ · Current token and service-right record ↗
Illustrated edition 0.6 includes the created EXITP identity, the actual free-service opening and the planned paid-integration boundary. Edition 0.5 remains an unchanged historical draft.
CLEAR RIGHTS. VISIBLE LIMITS. NO INVENTED MILESTONES.
Transparency without exposing private people.
Not affiliated with the $EXIT token (EXIT HOUSE), the EXIT Designer Token or exitprotocols.com. Names and tickers never identify this project; only the addresses and hashes published here do.
Verified official token identity
EXIT Protocol · EXITP · Solana. Official mint: 5vPz2s8NtkasmVRDz5ySz27V1E8UdSpzqc9xN678jups. Two finalized RPC reads on 25 October 2026 agreed: standard SPL Token, 6 decimals, 1 billion tokens, mint authority null and freeze authority null. This identifies the asset; it does not establish investment safety or future performance. Only this mint is official. A second token with the same name and symbol, 3ev5LvQN8weDndULdFwNwEgfJueaoGYLdBPtnHhnjups, was created by the same launch wallet 28 seconds earlier, during the launch flow; as of 26 October 2026 it has no trading history. It is not EXITP: always check the mint address.
Operating transparency
Service income, EXIT's creator share of the Jupiter Studio trading fee (half of a 1% fee) and any launch anti-sniper fee, expenses and reserves will be reported in dated disclosures. Proposed allocations are not executed transactions; no holder income or investment return is promised.
Continuous development
Release notes will distinguish shipped, tested, planned and unknown. New findings can correct earlier answers without erasing the historical record.
Public technical claims can be checked without publishing personal contact details, secrets, private client investigations or unrestricted raw archives.
Whitepaper · illustrated edition 0.6 ↗ · Download PDF · 14 pages ↓ · Public GitHub documentation ↗
05 / REPRODUCIBLE FEEDBACK
Challenge the answer.
Record steps and the expected/observed difference. The form creates a local file; it sends nothing.