docs / Runtime Funding and Farming

Runtime Funding and Farming

A frequency that runs continuously consumes compute. That cost is paid from a runtime escrow, which is funded by the residual majority of trading fees under the funding rule set at launch.

The funding split#

• · Up to 20% to the creator.
• · 10% to the protocol.
• · The residual majority to the runtime escrow; always the largest share.

Runtime states#

• · running; the escrow is funded and ticks are being applied.
• · stalled; the escrow is empty; ticks stop and the state is preserved at the last checkpoint.
• · paused; the creator halted ticks deliberately; the escrow is intact.

Depletion is expected#

Most frequencies will stall. A stalled frequency is not broken or lost: its specification, provenance, and checkpoints remain published, and anyone can replay it from the seed. A refill resumes it from the last checkpoint.