Open source
Open source
The part that holds your stake is the part you can read, fork and run.
The boundary
Apache-2.0 covers the on-chain programs, the circuits, the IDL, the TypeScript and Rust SDKs, the bot framework for both Discord and Telegram, the market templates and the embeddable odds widget. We run the hosted bots, the web app, the indexer and public API, the wallet service, and dispute council operations.
The fee switch
The protocol fee goes to a program constant, not to a configurable address. A deployer cannot redirect it. Someone who forks the program can change the constant, and that is precisely the point: the boundary between "using Pari" and "running your own" is a code change, not a setting.
What survives us
Markets, pools, positions and claims live in the program. An open market stays open, a locked one still resolves on its schedule, and a final one stays claimable, whether or not any of our services are running. The indexer is a cache: odds history rebuilds from the chain’s own events and the leaderboards are on chain.
Self-hosting
A self-hosted instance sets its own creator and resolver economics within the bounds the program enforces. Protocol takeout, the early-exit fee, the creation fee and boost revenue always route to the protocol address. Federated instances moderate themselves; we can delist them from discovery and decline to serve them, and nothing more.