LFG

Deployment and Guardrails

How a launch seals the engine, and which checks the live bytecode enforces.

A launch is one PonsOmniDeployer.createOmniToken transaction. It deploys a new OmniTokenomicsEngine and a new Pons bonding curve, configures the fee weights, runs an ETH dev buy if the creator sent extra value, then seals bookkeeping to the router and transfers engine ownership to the creator. Engines are ordinary contracts. They are not proxies, and a later launcher cannot upgrade an engine that is already on chain.

What the current launcher seals

The live launcher is 0x432E7c7E0191659B3249D652b3747D22f053Dd6a. It writes the X and Telegram URLs from the launch form onto the Pons token, and exempts the launching wallet from the opening snipe tax so an ETH dev buy clears. It deploys each engine through OmniTokenomicsEngineFactory 0xfa6d7b80C93d350E874Bd641e77Ccd8A15F1a8B4. Creator fees can be bound to platform wallet and the launching address, or to an X (twitter) account. That account claims the escrow to any wallet. createOmniToken calls setFeeCollector(router) only when the router is set, then transferOwnership(creator), which freezes fee weights, the royalty handle, and the escrow. setFeeCollector reverts once feeCollector is already non-zero, so the creator cannot retarget it. recordPurchase and updateCurvePrice are onlyFeeCollector. The dev buy is recorded before that seal, while the deployer is still allowed to write the books. ponsFactory and LFG_TREASURY_WALLET are immutable. Engines from 0x0a4dF940c3362788782d3288Fc88670cB56af6dC and the older launchers listed on Contract Addresses keep the bytecode they were created with.

  • Router 0x70A0a219bb5f9EE87854B1c0c47f7f85774668Fb is registered as the fee collector, and the router stores the engine and curve for the new token.
  • Curve tax is totalTaxBps() at launch, passed as creatorTaxBps. Pons buybackEnabled is left false so pullPonsFees can call sweepFees.
  • Creator ownership on a new engine arrives after the fee freeze. setFees, setCreatorRoyalty, and setTippingEscrow revert. That does not change the curve tax already set, and it does not write entry prices. Engines launched before this launcher can still change those settings.

Reentrancy and payout order

pullPonsFees, claimHolderReward, claimTopBlastPayout, executeBuybackBurn, recordPurchase, router buy/sell, and createOmniToken use nonReentrant. receive() is intentionally not guarded: claim() pays ETH back into the engine, and a second lock would make every native pull revert. Holder claims write rewardDebt before the quote transfer, and restore it if the transfer fails. Buy & burn sets buybackVaultBalance to zero before calling the curve. TopBlast sends the payout while the reentrancy lock is held, then shrinks entryTokenAmount and resets avgEntryPrice.

Same-block dividend and price rules

  • Holder index. Tokens bought this block are left out of earningBalance. The first observation of a wallet only arms holderRewardEligibleBlock for the next block.
  • Seen balance. A transfer onto an already-checkpointed wallet does not raise the balance that earns, so a sender's already-accrued index cannot be collected again by the recipient.
  • TopBlast price. The first updateCurvePrice in a block is staged. currentCurvePrice adopts it on a later block, which is the price claimTopBlastPayout uses.
  • TopBlast loss cap. The quote paid is the minimum of the vault slice and (entry - price) * tokensStillHeld / 1e18.

Warning

The router owner can pause buys and sells and can rescue tokens left on the router. The engine has no function that sweeps an arbitrary token out of the mode vaults. A claim can still revert if (entry - price) * effectiveTokens overflows. That stops the claim. It does not move the vault to the caller.