Fees accrue in escrow, not in your wallet
When a Pons token's creator tax is collected on a trade, it doesn't land directly in the creator's wallet. It accrues in a dedicated fee escrow contract, tracked per quote asset, until the creator actively claims it.
Claiming is one transaction per asset
The escrow exposes two claim functions: claim() for native ETH, and claimToken(asset) for any other quote asset. There's no batch-claim function in the interface Pons documents - each asset a creator wants to withdraw needs its own separate claim transaction.
This matters most for a token that trades against more than one quote asset over its life: a creator collecting fees denominated in several different assets needs to send a claim call for each one individually, not a single sweep-everything transaction.
Practical implications
- Fees sitting unclaimed in escrow don't expire, but they also aren't earning anything - there's no reason to delay claiming beyond gas-cost convenience.
- If your token pairs against multiple quote assets, track which assets have accrued fees rather than assuming one claim covers everything.
- Claiming is a normal transaction with normal gas costs - factor it in alongside your other ongoing token-management overhead.
FAQ
- Do unclaimed fees expire? No - they remain claimable in escrow indefinitely, but they also don't accrue any additional yield while sitting there.
- Can I claim fees in multiple assets in one transaction? No - claim() covers native ETH and claimToken(asset) covers one specific asset per call; there's no batch-claim function.
- Who can claim a token's creator fees? Whoever the token's creatorFeeRecipient address is set to at launch - claim transactions are sent from that address.
Coordinate your launch with TokenBundle.
Prepare wallets, review allocations and manage network-specific launch execution from one workspace.
Open Robinhood workspace