> For the complete documentation index, see [llms.txt](https://degen-lp.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://degen-lp.gitbook.io/documentation/welcome/development-timeline.md). # Development Timeline ## Phase 1: Concept development and market research This phase involved gathering information about the market and potential users to ensure that the project was viable. The goal was to identify the needs of the target market and to define the problem that the project aimed to solve. Dates: 24/1-3/2 2023 Status: Completed ## Phase 2: Planning and design This phase involved creating a detailed plan for the project, including a product development document, user experience design, and wireframes. This phase also involved identifying the technical requirements for the project, such as hardware and software. Dates: 3/2-17/2 2023 Status: Completed ## Phase 3a: Development (Raffle Style Lottery) This phase involved the actual development of the raffle-style lottery platform, including the implementation of the blockchain infrastructure, smart contract development, web3 development, web development, and mobile development. Dates: 17/2-3/3 2023 Status: Completed ## Phase 4a: Testing and QA (Raffle Style Lottery) This phase will involve testing the platform to ensure that it is functioning correctly and that it meets the requirements set out in the planning and design phase. Also involves deploying on FTM testnet and mainnet. Dates: 3/3 - 22/3 2023 Status: Completed ## Phase 3b: Development (Fair Dice Game) Realizing the need for a more dynamic and engaging gaming experience, the team decided to pivot and develop a fair dice game alongside the raffle-style lottery. This phase involves planning, designing, and developing the dice game. Dates: \[Start Date] - \[End Date] Status: In Progress ## Phase 4b: Testing and QA (Fair Dice Game) This phase will involve testing the dice game to ensure its correct functioning and meeting the requirements set out in the planning and design phase. It also involves deploying on FTM testnet and mainnet. Dates: \[Start Date] - \[End Date] Status: TBC ## Phase 5: Soft and Official Launch In this phase, both the dice game and the raffle-style game will be soft-launched to test their functionalities and gather user feedback. The dice game will be launched first, followed by the NFT sale once there is sufficient interest from potential participants. This comprehensive launch strategy aims to ensure a smooth and successful rollout of the platform's features. Dates: \[Start Date] - \[End Date] Status: TBC ## Phase 6: NFT Sale This phase involves us hosting our NFT sale. It will be held after the official launch of DLP. More details to follow. Dates: \[Start Date] - \[End Date] Status: TBC ## Phase 7: Cross Chain Degen LP This phase involves the enablement of a compatible chain on DLP. More details to follow. Dates: \[Start Date] - \[End Date] Status: TBC --- # 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://degen-lp.gitbook.io/documentation/welcome/development-timeline.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.