> For the complete documentation index, see [llms.txt](https://docs.rektgames.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rektgames.io/whitepaper/additional-info/roadmap-and-completed-milestones.md). # Roadmap & Completed Milestones Completed milestones 2021 – 2023: * ~~Assembled a qualified team~~ * ~~Established identity for the product~~ * ~~R\&D for game development~~ * ~~Design the system architecture, including node structure, smart contracts, and data flow~~ * ~~Developed game assets~~ * ~~Analyze existing solutions to choose the appropriate blockchain type (public, private, consortium) based on use case requirements.~~ * ~~Design the system architecture, including node structure, smart contracts, and data flow.~~ * ~~Create a prototype to validate design concepts and test assumptions.~~ * ~~Develop the blockchain infrastructure including Backend, Frontend and Blockchain.~~ * ~~Commenced the game development process~~ * ~~Secured funding for the project~~ * ~~Reached out to advisors~~ H1 2024: * ~~Focus on game development and optimize game performance~~ * ~~Expand asset availability for integration~~ * ~~Initiate Marketing Campaign~~ * ~~Conduct internal testing and bug fixing~~ * ~~REKT Games Protocols Development and testing~~ * ~~Development of Backend infrastructure~~ * ~~Partnership with Gaming and social media influencers~~ * Initiate Marketing campaign and community building * Polish game development (ongoing) H2 2024: * Conduct Alpha testing * Develop the foundation for creator economy * Initiate private sale of Tokens * Conduct ICO on different launchpads * Conduct Beta testing * Implement NFT integration system for 3rd party NFTs * Backend Infrastructure Deployment on AWS * Smart Contracts Audit (Certik) * Chat Service Development * Smart Contracts Deployment on Polygon Chain * Implement smart contracts * Perform unit testing, integration testing, and system testing. * Integrate the blockchain solution with existing business processes and systems. * Platform Launch V1 Long Term * Develop “contribution system” (aka Staking) * Integrate new in-house developed games within the platform * Develop a precise, clear, and transparent due diligence process to ensure third-party games quality * Organize game Jams * Implement monitoring tools to track performance and detect issues. * Target new gaming platforms such as mobile, console, cloud gaming, etc... * Integrate immersive experiences through extended reality technology * Integrate different engines into the ecosystem * Forge partnerships with clothing brands interested in web3 and NFTs * Implement referral and loyalty programs * Explore additional revenue streams, such as in-game advertising, sponsorships, and cross-promotions * Develop premium games with a traditional price tag * Collaborate with external developers to integrate their games into the launchpad * Expand our games with additional game modes --- # 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://docs.rektgames.io/whitepaper/additional-info/roadmap-and-completed-milestones.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.