> For the complete documentation index, see [llms.txt](https://docs.pyreplay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pyreplay.com/development/bi-weekly-dev-updates/09-14-2024.md).
# 09/14/2024
We've successfully launched the first testnet version of Pyreplay, which will remain open until September 18th to gather user feedback and monitor platform stability. I'm thrilled to announce that we've completed the full development cycle, integrating the Frontend, Backend, embedding a Unity WebGL game, and deploying the necessary smart contracts on the Alephium ecosystem.
**Key changes to the reward structure:**
Initially, 20% of collected fees were to be redistributed to all NFT holders. This has been increased to 50%, while the 20% rakeback from entry fees has been removed to simplify calculations and provide greater benefits to players who hold more than 3 NFTs.
The redistribution structure may evolve based on fee collection. Weekly redistribution of dust amounts (since fees are split by 777, the number of NFTs) isn't feasible on Alephium. I'm currently exploring alternatives, such as raffles, to make these smaller amounts more meaningful. Any changes will be put to a community vote before implementation.
**What's next:**
After the testnet phase, we'll freeze the code, apply bug fixes for Battleship, and launch a soft version on the Alephium mainnet in October 2024. This will be similar but with a reduced number of lobbies and bets. Once this version has been stable for a month, we will introduce high-roller lobbies.\
\
**Future:**
* Smart contracts will be enabled for Bomberducks
* Development of Pong or Rock Paper Scissors based on community votes
Smart contract for Battleship
Claim page mockup
---
# 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.pyreplay.com/development/bi-weekly-dev-updates/09-14-2024.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.