LFG

Fee Structure

The treasury skim, the 90% mode split, and how ETH and ERC-20 quotes are handled.

A trade on the bonding curve credits fees to a shared Pons fee escrow, in the curve's quote asset. Nothing is pushed to the engine by itself. Anyone can call pullPonsFees() on that token's OmniTokenomicsEngine. The engine sweeps the curve, claims its escrow balance, and splits the quote it actually receives.

This page covers Robinhood Chain. For Solana, see Solana (Raydium LaunchLab).

The 10% LFG treasury skim

Every receipt is skimmed before the launch modes see it. LFG_PROTOCOL_CUT_BPS is 1,000, so 10% of the amount goes to LFG_TREASURY_WALLET. That address is immutable on the engine: 0x2A9f5c0fC9639b80725E9f3A20537DA4644b4DBE. Native quotes are sent as ETH. ERC-20 quotes are transferred as that token. Dust below 1 bps is carried in lfgCutDust so later receipts still pay the treasury.

OmniTokenomicsEngine.solsolidity
uint16 public constant LFG_PROTOCOL_CUT_BPS = 1_000; // 10% of each receipt
address payable public immutable LFG_TREASURY_WALLET;

The remaining 90%

The other 90% is divided by the relative weights of the modes that are actually active: buybackBurnFeeBps, holderRewardFeeBps, topBlastProtectionFeeBps, and creatorFeeBps. A 300 / 400 / 300 configuration of buyback, holder share, and TopBlast splits that 90% as 30% / 40% / 30%. Rounding dust on the split stays in the TopBlast share. If a creator handle is not configured, creatorFeeBps is treated as zero and that weight falls through to TopBlast. If every active weight is zero, the entire 90% is parked in buybackVaultBalance.

WeightWhere the 90% slice goes
buybackBurnFeeBpsbuybackVaultBalance, spent later by executeBuybackBurn().
holderRewardFeeBpsThe holder-reward index, accRewardPerShare.
topBlastProtectionFeeBpstopBlastVaultBalance, the drawdown pool.
creatorFeeBpsOmniTippingEscrow.depositToCreatorKey for the launch handle.

ETH and ERC-20 quotes

The split does not depend on the quote. address(0) means native ETH: pullPonsFees calls claim(), and receive() runs _collectFee. Any other quote, including USDC or a factory-approved token, is claimed with claimToken and split from the ERC-20 balance the engine just received. Vault balances, holder payouts, TopBlast payouts, and the treasury skim all stay in that same quote. A native transfer sent to an ERC-20-quoted engine reverts with UnexpectedNativeFee.

What the curve charges

At launch, the sum of the four weights is passed to the Pons factory as creatorTaxBps. The maximum curve tax on Robinhood Chain is 10% (1,000 bps). The engine refuses a configuration above MAX_TOTAL_FEE_BPS (1,000 bps), and Pons enforces its own cap at launch: the factory's maxCreatorTaxBps() is 1,000 bps (10%) on Robinhood Chain mainnet, and launchToken reverts above it. That curve tax rate is set in the launch transaction. Later setFees or setCreatorRoyalty calls, which the creator can make as engine owner on older engines, change how future receipts are weighted. They do not raise the tax the curve already charges. The sum of the four weights still cannot exceed 1,000 bps.

Pons sets maxCreatorTaxBps() and can change it. The factory checks it inside the launch transaction, so a launch above the live value reverts.

Note

Pons also takes its own base protocol fee into the same escrow path. pullPonsFees skims 10% of whatever balance the engine claims, then applies the mode weights to the rest. LFG launches leave Pons's separate buyback flag off so the engine can sweep the curve itself.