LFG

Fee Structure

The 10% hard cap, and how it splits across buyback, holders, and TopBlast.

Every token deployed through LFG Pad routes its trading fees through an OmniTokenomicsEngine instance, deployed and wired to that token at launch time. The engine enforces one invariant above everything else: no combination of fees can ever exceed 10% of trade volume in aggregate.

OmniTokenomicsEngine.solsolidity
uint16 public constant MAX_TOTAL_FEE_BPS = 1_000; // 1,000 bps = 10%

The four buckets

BucketPurpose
buybackBurnFeeBpsBuys back and burns the token, mechanically reducing circulating supply on every trade.
holderRewardFeeBpsStreams to existing holders as passive yield — see Holder Yield & Creator Royalties.
topBlastProtectionFeeBpsFunds the TopBlast Protection Hook, the anti-manipulation mechanism active around a token's migration to its post-curve AMM pool.
creatorFeeBpsStreams directly to the token's creator via their OmniTippingEscrow creatorKey — the same escrow bucket Universal Social Tipping deposits into.

Every one of these is expressed in basis points (bps) — 100 bps = 1%. Setting any of them checks the *sum* of all four against MAX_TOTAL_FEE_BPS before accepting the change, so it's impossible to end up with a configuration that exceeds 10% even through a sequence of individually-valid updates.

OmniTokenomicsEngine.solsolidity
uint256 total = uint256(_buybackBurnFeeBps)
    + _holderRewardFeeBps
    + _topBlastProtectionFeeBps
    + creatorFeeBps;

if (total > MAX_TOTAL_FEE_BPS) revert FeeTooHigh(total, MAX_TOTAL_FEE_BPS);

Note

This cap is enforced identically whether the fee split is being configured by the core owner (buyback/holder/TopBlast) or by setCreatorRoyalty (the creator-fee share) — there's exactly one combined ceiling, not four independent ones.