Protocol
Fees and royalties
The swap fee, how it splits between creator and protocol, the creator tax, and how creators claim.
View as MarkdownTrading generates a swap fee. The creator keeps most of it, the protocol keeps a share, and a creator may also have set a separate tax at launch.
| Split | Share |
|---|---|
| Swap fee | 0% of the trade (0 bps, from Hook.swapFeeBps()) |
| Creator royalty | 90% of that swap fee |
| Protocol share | 10% of that swap fee (1000 bps, from Hook.protocolFeeShareBps()), paid to the Treasury |
| Creator tax | Separate from the split above and goes to the creator in full. Set per launch, ceiling 10%. Most launches set 0. |
The split is settled at claim time rather than at swap time, so the hook holds the live value and the numbers above are what is deployed today.
How creators claim their royalty
From the coin's page on the app, which calls Hook.claimFees(poolId, minOut). Two things are worth knowing:
- The claim is not permissionless. Only the pool's creator or one of the hook's operators may call it.
- A pool accrues fees in both currencies, and token-denominated fees are sold into the base asset inside the claim. That sale is what
minOutbounds, which is why a claim can revert withSlippageExceeded.
A creator can hand the payout over without moving the coin: transferCreator for an immediate transfer, or proposeCreatorTransfer and executeCreatorTransfer for a two-step one.
What the protocol share funds
It is paid to the Treasury contract listed under Contract addresses, which is where every protocol-side fee accrues. See also the fees page.