# V2 Launchdate We are actively working on the development of HORSY V2, and it represents much more than a simple update — it’s a full rebuild of the game based on real user feedback and lessons learned during V1 and the Genesis mint. Over the past months, we’ve gathered insights from the community and identified areas for improvement across both the frontend and backend. As a result, we’ve made the decision to completely rewrite the current codebase to ensure better performance, improved UX, and long-term scalability. HORSY V2 will also introduce several exciting new features, including: * WalletConnect support for broader wallet compatibility * A live chat system so players can talk and engage while placing bets * A cleaner, faster, and more interactive interface Our primary focus is on delivering a stable and high-quality product, not rushing to meet arbitrary deadlines. While our internal goal is to launch V2 late June, we want to be transparent: this date is subject to change depending on development progress and testing outcomes. We believe a short delay is a fair tradeoff for a better and smoother experience. We’ll continue to keep the community updated as we move through development milestones. Your patience and support are deeply appreciated — and we can’t wait to show you what’s next. --- # 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://horsy-on-hl.gitbook.io/horsy-docs/basics/markdown/v2-launchdate.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.