Launch once. Route forever.
Every token launched here receives its own ownerless fee vault. The Pons fee is fixed at 3%, and every collected fee is permanently assigned: 70% burns the launched token, 25% buys and burns $BURN, and 5% funds that project's operations.
The launch contract.
The launch form creates the Pons token and a dedicated immutable vault in one transaction. The creator can add a logo, description, website, X, Telegram, an optional dev buy, and a project operations wallet. There is no payment note, X Money recipient, or editable fee control.
- 3%
The token's Pons creator fee is fixed at 300 basis points. Pons's own protocol-level fee mechanics remain upstream.
- 70%
Buys the project's token on its active Pons curve or graduated pool and sends every token received to 0x0000…dEaD.
- 25%
Buys the native fomoFurnace token, $BURN, through its live Pons / Uniswap route and burns it.
- 5%
Goes to the project's operations recipient. That address is selected at launch and immutable inside that token's vault.
Pre-bond and post-bond.
The same vault follows the token through all three Pons lifecycle phases. Graduation does not replace the fee recipient or end buyback-and-burn execution.
The vault sweeps curve-denominated fee balances into escrow, claims the resulting ETH, and executes the fixed split. Project-token burns buy directly from the active curve.
If a final curve buy triggers graduation and returns unspent ETH, that refund remains in the 70% project-burn lane. It is retried against the newly created pool instead of leaking to operations.
After graduation, both project-token burns and $BURN burns use quote-protected V4 swaps. The worker detects the phase on-chain for every cycle.
Post-graduation hook fees can be token-denominated. Only Pons's designated feeSweepOperator can convert those protected hook balances into ETH. Once Pons credits that ETH to escrow, the vault claims and splits it normally. If the operator is delayed, value stays pending upstream and execution resumes when the credit appears; the launchpad cannot bypass that Pons permission.
One new thesis, one cycle.
Every launched token is registered into the CA-specific thesis ledger automatically. The browser extension already scans every enabled token independently; the worker never reuses $BURN's count for another token.
- Register
The launch event records the token and vault, then authenticates the token into the thesis collector with its current count as the baseline.
- Count
The extension collects each registered token's Fomo feed and holdings separately. Unknown token addresses fail closed with zero theses instead of falling back to another token.
- Trigger
The first new unique thesis after the baseline opens one collection cycle for that token. Historical theses cannot trigger a fresh launch.
- Secure
The thesis stays pending until a non-zero fee claim is secured inside the vault. Once secured, each split lane retries failed quotes or delayed pool availability independently without requiring another thesis.
What a project cannot change.
Each vault has no owner, proxy, upgrade path, arbitrary-call function, rescue function, fee setter, route setter, or recipient setter. Its launch token, operations wallet, Pons stack, $BURN token, dead address, executor, and 70/25/5 accounting are constructor-bound.
The launchpad and every vault are ownerless contracts. No fomoFurnace operator can rewrite a project's split after launch.
Launches accept only the current Pons launch fee plus the requested dev buy. Fee collection rejects mismatched claims or retained ETH.
Every buyback requires a non-zero minimum output and a deadline no more than ten minutes ahead.
The optional dev buy executes in the launch transaction and returns the purchased tokens to the launching wallet; a failed minimum output reverts the launch.
Pons's owner can propose a creator-fee-recipient override and execute it after its 72-hour delay. That power belongs to Pons, not this launchpad, and cannot be disabled by our vault.
Local construction using the recorded arguments reproduces the deployed runtime byte-for-byte. Runtime hash: 0x6cd8…138a3.
The original $BURN executor.
The launchpad is separate from the existing ownerless executor for fomoFurnace itself. Every successful claim through that contract remains atomic: 95% buys $BURN for the dead address and 5% funds its fixed operations wallet.
- Claim
The fixed executor asks the contract to claim an exact amount credited by the Pons V2 fee escrow.
- 95%
The contract sends exactly 9,500 basis points through the fixed Pons / Uniswap V4 route to buy FURNACE.
- Burn
Every token received by that buy is transferred directly to 0x0000…dEaD.
- 5%
The remaining 500 basis points, including rounding remainder, goes to the fixed operations wallet that pays execution gas.
What cannot change.
The values below are constants or constructor immutables in the deployed bytecode. Deploying another contract cannot modify this one.
There is no fee-setting function and no path that bypasses the split.
FURNACE and the canonical dead address are permanently pinned.
Factory, escrow, hook, router, pool fee, and tick spacing are fixed.
The only caller and the operations recipient are fixed to the same accessible wallet.
No owner, proxy, upgrade hook, executor setter, recipient setter, or route setter exists.
No arbitrary call, rescue function, or withdrawal function can redirect claimed value.
Execution safeguards.
Every execution requires exact accounting of the requested claim, a protected quote, and a short deadline. Reentrancy, partial settlement, retained claim ETH, and unauthorized callers are rejected.
The amount reported by escrow and the ETH actually received must both match the requested claim.
Minimum token output must be non-zero, and the final received amount must meet it.
The supplied execution deadline cannot be expired or more than ten minutes ahead.
The post-execution ETH balance must equal the balance that existed before the claim.
Verify every address.
These are the live deployment and fixed infrastructure endpoints. Follow them to inspect the contracts, token, Pons stack, and operational boundaries directly.
- Launchpad contract
- 0x75b39E0351E43Ab490d1A1cD528D5D5E4356f286
- Executor contract
- 0x7982c7c79A89584bd481Cc7D4eD68bBa62D4A072
- FURNACE token
- 0xD0dF90E65e8eC70660A57a95e93145cF3e9D2b56
- Pons V2 factory
- 0x7eD598BcEf8bd9Edd8C97A195C6d13f40801EC7e
- Universal Router
- 0x8876789976dEcBfCbBbe364623C63652db8C0904
- Pons fee sweep operator
- 0x49BbF2b70955Fb3a106e084D4BFDa92d334573d2
- Pons locker (not a buyback wallet)
- 0x267444d099b10fb5ed7c3cc7b7c767adca574952
- Executor / operations wallet
- 0xB97f45C6eBAA4691e512ab42e646464A59DB425F
- Dead address
- 0x000000000000000000000000000000000000dEaD