# Fees & Affiliate Links ## Fees ### Buy (2% Fee, taken in ETH) of this 2%... * 12.5% to creator * 12.5% to owner * 12.5% to protocol * 12.5% to provider (this is the affiliate fee so you can earn eth from anyone you refer, also third parties can build their own frontend to earn this fee) * 50% to eth reserves (bonding curve shift, increases ETH reserves in bonding curve, which increases floor price, market price, and borrowing power) ### Sell (2% fee, taken in WFT) of this 2%... * 12.5% to creator * 12.5% to owner * 12.5% to protocol (tokens are locked and borrowed against so never sold back to circulation, increases floor price) * 12.5% to provider (this is the affiliate fee so you can earn eth from anyone you refer, also third parties can build their own frontend to earn this fee) * 50% burned (bonding curve shift, decreases WFT reserves in bonding curve, which increases floor price, market price, and borrowing power) ## Affiliate Links Early access to the WaveFront UI will be limited to early beta testers in our Discord and distributed via affiliate codes. Each user will then be able to generate an affiliate code to invite friends. 12.5% of the fees produced from users via an affiliate code go back to the affiliate in perpetuity. We believe that our profit distribution will be our new strategy for marketing! The enforcement of the affiliate link and access codes will bring a great stream of profit for our community and whoever tries to run marketing for us. We grow together with the community bootstrap launch, enforcing profit share for access links, this strategy is new to the space. --- # Agent Instructions: 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: ``` GET https://gum-ball.gitbook.io/wavefront-culture-markets/fees-and-affiliate-links.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.