Operations#
Public guides for submitting lifecycle transactions, operating a keeper, and estimating the capital required to keep markets available.
Overview#
Seesaw is designed for permissionless operation. Anyone can run infrastructure to keep the protocol running.
In This Section#
- Cranking - Running crank infrastructure
- Run a Pyth Pull Keeper - Open-source Pull keeper setup
- Market Economics - Rent float, closer budget, and launch cadence policy
- Self-hosted Reclaim Runner - Run and pair a credential-bearing proof service
- Source Availability and Licenses - Repository access, component licenses, and release status
Quick Start#
Running a Crank#
# Build and inspect the Solana CLI cranks from this repository
pnpm --filter @seesaw/cli build
pnpm --filter @seesaw/cli exec seesaw --help
Use Cranking for lifecycle prerequisites and the CLI guide for wallet and network configuration. A keeper is a separate service: follow its setup instructions to configure the target program, RPC, relay, signing key, and readiness checks before enabling transaction submission.
Crank Requirements#
Budget SOL for transaction fees, priority fees, and temporary oracle-update account rent. Required capital depends on workload and submission policy; a fixed wallet balance or process uptime does not establish that markets will advance. Monitor confirmed lifecycle transitions and the keeper's readiness state, and size the RPC service for the actual scan and submission load.
Operational Model#
Permissionless Design#
The following lifecycle operations accept permissionless callers, subject to their timing, account, oracle, and settlement-state checks:
| Operation | Anyone Can Execute | Incentive |
|---|---|---|
create_market | Yes | None; creator funds the market and prepaid lifecycle reward pool |
snapshot_end | Yes | Configured closer reward, subject to the rent-safe market budget |
resolve_market | Yes | Configured closer reward, subject to the rent-safe market budget |
expire_market | Yes | Configured closer reward, subject to the rent-safe market budget |
force_close | Yes | Configured closer reward, subject to the rent-safe market budget |
close_market | Yes | No closer bounty; remaining account rent and reward margin return to creator |
Redundancy#
Multiple crank operators compete to execute operations:
Only the first successful execution receives the reward.
Economics#
Revenue Sources#
| Source | Amount | Frequency |
|---|---|---|
| Market lifecycle | Current configured closer reward | Successful reward-bearing transitions |
| Position settlement | No fixed SOL closer reward | Per user |
Estimate gross revenue from the transitions your keeper actually lands and the
rewards it receives. The active config sets closer_reward_lamports; the market
must retain enough lamports above rent to pay it. See
reward constants and
Market Economics for budget funding and recovery.
Cost Factors#
| Cost | Amount | Notes |
|---|---|---|
| Transaction fees | Variable | Per transaction; depends on signatures |
| Priority fees | Variable | During congestion |
| Infrastructure | Variable | RPC, compute |
Estimating net revenue#
Subtract measured transaction fees, priority fees, failed-attempt costs, RPC charges, and hosting costs from confirmed rewards. Competing callers can win rewards, and insufficient rent-safe reward funds can reduce payouts. Recoverable account rent is working capital, not fee revenue. See Market Economics for the per-market cost model.
Support#
- Discord - Operations channel
Next Steps#
- Review Cranking for detailed setup
- Estimate working capital with Market Economics