> For the complete documentation index, see [llms.txt](https://wiki.rally.io/rally-io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.rally.io/rally-io/101/tbc/faqs.md). # Token Bonding Curve (TBC) FAQs ## **Can new creators choose which curve they want to be on?** A. Based on the performance and feedback from creators, Rally will default to the V2 TBC for new creators although the V1 TBC is available for any creator who would like to opt in to that design. ## **Can Coins change curves?** A. There are several technical reasons why this is currently not possible but the most important considerations to creators and Coin holders is that changing curves would not update the amount of Coins any holder has. For example, a holder that had $100 USD worth of X Coin when migrated over to the V2 TBC would see that drop down to $20 USD worth of X Coin. This would obviously be a very drastic change and could lead to a lot of confusion and frustration that should be avoided. ## **Are any future changes happening to the V2 TBC design?** A. Yes - Rally continues to collect feedback from creators, Coin holders, and community members that may mean changes to the TBC design in the future. The features Rally is working on pertain to giving creators more launch and Coin economy controls which do not have to do with the TBC design. --- # 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://wiki.rally.io/rally-io/101/tbc/faqs.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.