Fee claims

View and claim creator, platform, and referral fee balances.

Swap fees remain available until they are claimed. One inactive recipient cannot block swaps, launches, or anyone else’s claim.

Fee claims

The connected wallet’s Profile page groups available balances by paired asset, including ETH, MON, BNB, OKB, USDC, USDG, supported Coinbase crypto majors, and supported Stock Tokens. Its Claim action always pays the recorded recipient.

Contract option	Who may start it	Destination
claimFor on a current fee contract, or the equivalent function on the fee contract recorded for an earlier launch	Anyone	Always the recorded recipient
claimTo	The balance owner through a direct contract interaction	An address chosen by that owner

Claims pay the same paired asset used by the launch market. A USDC market pays USDC fees, a USDG market pays USDG fees, an ETH market pays ETH fees, an OKB market pays native OKB fees, a crypto-major market pays its selected asset, such as a Coinbase wrapped token or Arc cirBTC, and a stock-paired market pays its selected Stock Token.

Profile overview

The connected Profile page groups:

• claimable hook-fee balances by asset;
• referral activity and attributed trades;
• the wallet’s launches and supported management tools.

Creator and referral earnings are claimed from Profile > Fees. Profile > Referrals shows attributed trade counts, hook-fee volume, and recent referral activity; it is not the claimable-balance view.

Wallet Activity shows indexed claim transactions. Profile views may briefly sync after confirmation; the contracts remain authoritative.

Currency handling

Native currency

The app claims native ETH (Base/Robinhood), BNB (BSC), MON (Monad), or OKB (X Layer) directly to the destination.

Token pair

The app claims the exact ERC-20 used by that launch pool. This can be USDC, USDG, cirBTC, another supported crypto quote, or a supported Stock Token. Developers should use the pool’s recorded quote address and can verify current assets in Production contracts and Stock-paired launches.

On X Layer, fees and claims use the pool’s paired currency: native OKB, USDC, xETH or a wrapped stock token. USDC uses 6 decimals; the other catalog quotes use 18. Native OKB pays transaction gas. Claims from an existing pool always retain that pool’s recorded currency, even if its quote is later removed from new creation.

Developers can find the exact read and claim functions in Functions and events.