How to read the fees
One basis point is 0.01%. A fee of 10 bps is 0.10% of the stated basis. The basis and charge treatment matter as much as the number.
Classic includes the Programmable share inside the fee selected for that launch. Standard Custom uses a separate 10 bps policy on a verified official market path. Template fees are a different product path and are not stacked with another unnamed template charge.
Launch fee policies
Each row describes one fee path. The exact release, contract and template version determine which path applies to a launch.
| Path | Total or selected fee | Split | Treatment |
|---|---|---|---|
| Classic | selected separately for buys and sells from 100 to 1,000 bps | 10 bps (0.10%) to Programmable. The remainder becomes creator rewards. | included in the selected buy or sell fee |
| Standard Custom | 10 bps (0.10%) | 10 bps (0.10%) to Programmable. Project economics are defined by the release. | added to the project hook fee |
| Public template | 20 bps (0.20%) | 10 bps (0.10%) to the template creator and 10 bps (0.10%) to Programmable. | one 20 bps public template fee |
| Partner template | 20 bps (0.20%) | 15 bps (0.15%) to the partner and 5 bps (0.05%) to Programmable. | included in one 20 bps partner template fee |
The policy describes the split; the matching release and public record determine whether a particular launch, template or recipient can use it. Public template intake is controlled by the repository instructions. This policy page is not an execution receipt.
Creator earnings
Classic creator rewards are the selected swap fee minus the 10 bps Programmable share. Public template creators receive 10 bps from official launches that use their exact template version. Partner templates use a separate 15 bps partner share and 5 bps Programmable share.
Earnings depend on actual qualifying activity. A review, listing or template publication does not promise trading volume or a fixed payment.
Protocol revenue
The published protocol allocation assigns 80% of attributable net protocol revenue to V4 buybacks and 20% to the treasury. V4 purchases go to the protocol revenue wallet. They are not burns.
The exact processor and activation record determine when this allocation is used; the current deployment record may bind a different processor until this policy is activated. No separate keeper share is described by this policy.
Boundaries
- Attributable net revenue means the amount that belongs to Programmable after creator and partner liabilities are separated.
- Revenue processing applies only to verified supported sources. A new fee source requires its own activated source profile.
- Eligible revenue is evaluated in cycles with a minimum interval of 24 hours. Thresholds, finality, provider health or safety gates can delay execution.
- Fee and revenue documentation does not promise token value, volume, holder yield or future purchases.
Technical integrators should use the versioned machine contracts in the developer repository rather than parsing this page.
Developer contracts — opens GitHub in a new tab