> For the complete documentation index, see [llms.txt](https://arc-3.gitbook.io/arc-newsletter/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://arc-3.gitbook.io/arc-newsletter/week-25.md). # Week 25 * We've just pushed an update to the ARC dApp specifically for mobile users interacting with the **WalletConnect** integration. The update patches an issue where user balances would not populate nor allow the swapping of tokens, even if the wallet had valid funds. This is a major technical fix and changes most of the logic that originally caused the issue * NFT Marketplace has undergone more stability fixes to ensure it can support all functionality and this process is ongoing. Good headway is being made in this area * An issue with JWT that affected the dApp and Marketplace has been rectified * Weekly AMA's on Wednesday at 1900 UTC will continue in order to give the community a platform to voice opinions and discuss any ongoing issues or concerns they may have * We will be hiding areas of the website that have not been completed and ensure that we focus our efforts to finalise products before moving onto the next part of the roadmap * Roadmap will be discussed and finalised over the next few weeks with a consideration taken to ensure we don't overstretch --- # 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://arc-3.gitbook.io/arc-newsletter/week-25.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.