$ZKOS overview
Official $ZKOS contract, intended utility, bonds, coordination and governance.
What $ZKOS is for#
$ZKOS is designed for four jobs: access to higher usage limits, bonds that back good behavior, coordination of the insurance pool, and governance of bounded parameters. These utility modules remain on the roadmap where marked.
$ZKOS does not control user funds and cannot change a locked launch manifest.
Utility#
| # | Module | Function | Mechanism | Status |
|---|---|---|---|---|
| 1 | Access tiers | Higher usage limits: scan quotas, FractalNets trace budget, saved reports, alerts, export | Hold or stake $ZKOS. Core tools stay free | Planned |
| 2 | Crawl credits | Pay for compute on large FractalNets traces | $ZKOS is spent per large trace | Planned |
| 3 | Launch bonds | List a launch in the curated feed | Creator posts a bond, returned at the end unless objective manifest conditions are violated, such as liquidity removal inside the protected window. Slashed bonds fund the insurance pool | Planned |
| 4 | Vouch staking | Vouch for a launch | Stake returned unless the same objective failure conditions occur, then slashed. No reward is promised | Planned |
| 5 | Insured launches pool | Partial refunds under published rules | Funded by slashed bonds and vouch slashes | Planned |
| 6 | Keeper and prover bonding | Secure Pool settlement | Operators bond $ZKOS and are slashed for late or invalid settlement. They are paid in USDG, not $ZKOS | Planned |
| 7 | Daemon registry bonds | List an agent | Publishers bond $ZKOS, slashed if the agent's proven actions break its declared policy | Planned |
| 8 | Governance | Vote on bounded parameters: window lengths, price-guard band, wallet caps, infrastructure exclusion list, supported markets | Holder votes with a timelock. Cannot touch user balances or locked manifests | Planned |
| 9 | Fee discounts | Lower protocol fees | For stakers | Planned |
Fee and treasury flow#
Protocol feesTreasuryGoverned by holders (timelock)
Slashed bonds and vouchesInsured launches poolPartial refunds under published rules
No revenue share or yield is planned for v1. Any change would go through governance and legal review.
What $ZKOS does not do#
- No promised yield
- No revenue share in v1
- No priority allocation in fair launches, to protect launch fairness
- No custody of user funds
- No ability to alter a deployed manifest
Last updated 2026-09-28