> For the complete documentation index, see [llms.txt](https://basedinc.gitbook.io/basedbid/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://basedinc.gitbook.io/basedbid/explainers/launch-explainers/fee-builder.md). # Fee Builder
Depending on the network and DEX you launch on, this system may be referred to as **v4, Infinity, Burn & Earn, or Lock & Earn**. On basedbid, it all runs through the same underlying architecture described below
Fee Architecture * **LP Fees** are standard fees earned from your liquidity position. When collected, you receive **50% in native token** and **50% in project token** * **Fee Builder** is basebid's custom hook, sitting on top of LP fees and capturing a programmable fee directly at the swap. **No token sells. No thresholds. No red candles****.** You choose where it goes: **holder rewards, buybacks, liquidity, or any custom wallet** (marketing, KOLs, team, partners). No limits

Add Fees to Your PoolAdd Fees to Your Flash Token

Fully Modular You can add, remove, or reconfigure fee destinations anytime after launch, no redeployment needed. Start with rewards, add buybacks later, swap out a wallet. **Your token evolves without relaunching**

Editing your Pool's DEX FeesEditing your Flash Token's Fees

Built-In Optional Protections * **Tiered Fees:** * **Dynamic Fees:** **Auto-adjust** based on volatility * **Anti-snipe/Anti-MEV:** **Bot protection** at the pool level * **Cooldowns:** **Enforced gaps between transactions** with penalty fees

Add Protection to your Pools on a DEXAdd Advanced Protection to your Flash Tokens

Example **Example: $VAULT** $VAULT launches on basebid with **2% LP fees** and the **Fee Builder enabled at 5%**, configured as follows: * 2% to **holder rewards** * 1% to **automatic buybacks** * 1% to **liquidity** * 1% to a **marketing wallet** On a day with **$100,000 in trading volume**, $VAULT generates **$5,000 in hook fees**. $2,000 goes to holders, $1,000 buys back tokens automatically, $1,000 deepens liquidity, $1,000 goes to marketing and $2,000 goes to the creator. in **All from swaps, nothing sold** $VAULT also launches with all pool protections active: * **Dynamic fees** set to Medium (2x multiplier), triggered per swap, with a 10 minute decay period * **Snipe protection** active for the first 10 minutes post-launch, capping any single buy at 0.1% of supply * **Cooldown protection** enforcing a 10 second gap between buys, with a 1% penalty fee for wallets that try to bypass it * **MEV protection** enabled, blocking front-running and sandwich attacks Three months after launch, the team decides to remove the marketing wallet and redirect that 1% to increase **holder rewards** to 3%. **No relaunch. No migration. One config change** and the token is running a new strategy the same day. On that same $100,000 volume day, holders now earn **$3,000 instead of $2,000**

How to Set up the Fee Builder on a PoolHow to Set up the Fee Builder on a Flash Token

--- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://basedinc.gitbook.io/basedbid/explainers/launch-explainers/fee-builder.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.