> For the complete documentation index, see [llms.txt](https://go-whitepaper.stepn.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://go-whitepaper.stepn.com/others/change-log.md). # Change Log \ \&#xNAN;*23rd May 2024* 1. Release of STEPN GO Whitepaper 2. Release of STEPN GO Website *20th August 2024* 1. Add Haus Rule: A Host can share Energy up to the Host's Daily Energy cap to the Guest. *5th September 2024* 1. Update GGT Contract detail. *30th October 2024* 1. Update Trial Sneaker information. 2. The Gift/Buddy System is replaced by the Gift Bag System. 3. Change Sneaker transaction cost to 6 Energy. *28th April 2025* 1. Balance the chances in cross-quality minting. 2. Balance the Energy gained from burning Sneakers of Uncommon quality and above. 3. Balance the cost on Raw Stone upgrade. 4. Selling Raw Stone stack changed to maximum 10 per bundle. 5. Balance the Gem attribute. 5th May 2025 1. Balance the chance of Raw Stone cutting. 2. Rephrase STRONG FEET description to be more accurate. 4th June 2025 1. Updated the GGT burning address. 26th May 1. Added Challenge Capsules page. --- # 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://go-whitepaper.stepn.com/others/change-log.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.