> For the complete documentation index, see [llms.txt](https://programmable.market/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://programmable.market/docs/developers/machine-readable/fee-versions.md). # Fees by contract version Use a coin's launch source and recorded configuration to identify its fee rules. Existing contracts retain their settings when the website or module catalog changes. Rates below apply only to the relevant contract and pool; an external trade route can include additional fees. The [Fees and revenue](/docs/launch/economics.md) guide explains the current builder and the platform's revenue policy. ## Foundation The active Foundation releases on Ethereum and Robinhood charge 30 bps (0.3%) for Programmable on each buy and sell through its pool. Creator fees are additional. Both are calculated on the gross quote amount, and fees accrue in the quote asset. For ETH-funded launches with a WETH quote, the ledger asset is WETH. Retained fee100 Foundation releases keep their immutable 100 bps (1%) rate. They are no longer selected for new launches. Identify the exact release before calculating fees. Modules can receive an allocation of the creator fee recorded at launch. That allocation does not reduce the platform fee. Foundation's initial pool has a 0% LP fee. Use the creator rate recorded for the trade's direction. Some releases support different buy and sell rates; earlier ones use a shared rate. The current website control selects one shared rate from 0% to 10% in whole percentage points. ## Earlier Native and Engine coins | Version | Without eligible modules | With eligible modules | | ------------------------------------- | ------------------------ | ------------------------------------------------------- | | Native V2 and Engine V1 quote trading | 0.10% to Programmable | 0.10% to Programmable and 0.20% total to module authors | | Native V1 | 0.20% to Programmable | 0.10% to Programmable and 0.10% total to module authors | Creator and pool fees are additional. Author rewards are divided equally between distinct eligible module families. Repeated instances do not create more shares. Escrow deposits, settlement requests and refunds do not generate trading fees. ## Custom launches New Ethereum and Robinhood approvals require a 30 bps (0.3%) platform share collected by the pool on each buy and sell. The Ethereum Native30 V3 reference uses the gross native ETH leg, rounds up per trade and accrues fully backed PoolManager native claims. `claimPlatform()` always pays `0xD88539d3c4C460136a733A3Fd60cf6BF269079da`, regardless of its caller. Exact runtime and trade-accrual proof lets the website recognize that fee and avoid adding a second routing fee. Source, bytecode and trade evidence must agree. Existing Native100 contracts retain 100 bps (1%). Neither changing documentation nor upgrading the website changes those immutable contracts. Earlier Robinhood Native20 charges 20 bps (0.20%) on the gross native ETH amount of each successful buy or sell through its bound pool. Creator and pool fees are separate. For a gross amount of 1 ETH, Programmable earns 0.002 ETH. Native20's rate is not a universal rule for custom contracts. Use the fee configuration and verified fee path of the exact launch and pool. A configured policy or a launch stamp alone does not establish that a fee is enforced. A creator fee of 0% produces no creator earnings from that trade. ## Ethereum launches New Custom Launches on Ethereum Mainnet and Robinhood use a **0.3% (30 bps)** Programmable platform fee. In parts per million, the rate is **3,000 / 1,000,000**. Project and LP fees are separate. Confirm the deployed contract's assessment base, fee asset, accounting mode, recipient, accrual and claim path before presenting the fee as enforced or collected. A launch stamp alone does not certify fee behavior. Earlier Classic contracts retain their 0.10% included share. A 1% Classic fee leaves 0.90% for creator rewards. Retained fee-certified Custom API profiles specify an exact 0.10% share; their versioned formats and deployed contracts remain unchanged. These older rates are not the current Ethereum Custom Hook launch policy. [Classic on Ethereum](/docs/developers/machine-readable/fee-versions/classic.md) describes its deployed contracts, liquidity and recipient rules. ## Accounting Fees accrue before they are claimed. A claim withdraws an existing balance and must not be counted again as revenue. Keep creator fees, module rewards, LP-position proceeds and platform fees separate. Gas, liquidity deposits, escrow and refunds do not count as platform trading revenue. The Dune dashboard uses **Custom Launches** for confirmed launches, **Custom Creator Rewards** for creator fees and **Custom Protocol Revenue** for Programmable's fees. Each query identifies the contracts and transactions it covers. Earned fees are distinct from completed buybacks and burns. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://programmable.market/docs/developers/machine-readable/fee-versions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.