Skip to main content
The deployed mainnet policy applies an additional surcharge to buys during every new launch’s opening period. This covers FX-pair, single-currency, and dedicated official-FX launches. Each launch starts its clock after its canonical pool or pools are seeded. An FX-pair launch shares one clock across both token pools. Activation cannot restart, and the surcharge remains zero after expiry.

The current configured curve

The deployed R6 policy starts at 99%, uses a nominal 500-millisecond half-life, and expires after five seconds. These values are fixed in the release policy contract. EVM timestamps resolve to whole seconds. The half-life describes the curve’s parameter, rather than a timer that executes twice every second. These rates apply to the quote remainder after ordinary hook fees. Always check the actual deployment’s opening policy.

Calculation order

For a 100-USDC FX-pair buy at elapsed time zero: The native LP fee then applies on its own fee base. This example shows why the opening surcharge materially changes an immediate launch-time purchase.

Which trades pay it

Purchases through the canonical hooked pools pay the applicable surcharge, including purchases submitted by a different router or directly through PoolManager. Sells pay normal fees only. A separate secondary pool may have different rules.

Where it goes

The entire additional surcharge is protocol-owned revenue. It is collected in the local quote currency and follows the same 90% buyback / 10% operations accounting after USDC realization. It does not go to the creator or token holders. It does not trigger a currency conversion or $FX purchase synchronously inside the trader’s swap.

What it changes

The surcharge makes immediate extraction at the opening price expensive. It does not identify bots, eliminate sniping, or guarantee a protected price. Traders can wait for the window to expire. Its activation time is a chain timestamp. A browser countdown is a display of that policy, not the authority that sets the fee.