SPLICE ROUTER
BUY + BURNProject tokens settle directly to 0x…dEaD.
V2 CONTRACT PENDINGRelease a bounded fraction of the queue every configured interval once the minimum balance is reached.
Program the execution layer for an existing Pons project.
SPLICE does more than split fees. Each integrated project can define where fees queue, when a bounded tranche may execute, and which budget, depth, slippage, and market-condition guards must pass. This page is a design preview; only existing manual buyback and burn execution bounds are fork-tested.
TIMER POLICIESIMPLEMENTABLE NEXTPRICE POLICIESHISTORICAL ORACLE REQUIREDLIQUIDITYEXECUTOR REQUIRED
V2 POLICY LAB · DESIGN PREVIEW
UNSIGNED · NOT DEPLOYEDChoose when each market route may execute.
Weights decide where fees queue. Policies decide timing, conditions and tranche size. No policy below is published onchain.
NO SPOT TRIGGERS
A current-price threshold is easy to manipulate. Drawdown and recovery modes require sustained historical observations.
BOUNDED TRANCHES
Every execution is capped per call, per day and as a share of venue depth—even when the trigger is valid.
PUBLIC CHANGES
Policy edits inherit the four-hour public delay. One-shot ladder epochs prevent replaying the same trigger.
HONEST MEV BOUNDARY
Private delivery may help, but the contracts must remain safe on a public mempool. SPLICE will not claim MEV immunity.