> 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-47.md). # Week 47 * Working on website updates and changes * Revision and continual improvement to the ARC pitch deck * Working on a video explaining what exactly the Reactor Compiler is (and why we're working so hard on it) * Working on general marketing material for some exciting announcements we have coming up * Fix dApp on multiple chain network Optimism/Polygon / BNB/ Ethereum * Connect to trust wallet on mobile view * Bug Fix Load token balance * Bug Fix Swaps on mobile browser * Discussions with L1 foundations advancing, grants & resources in progress * Influencer partnerships developed, AMA recording this week. * Decks, modelling & workflow documentation complete * L1 Foundation interview finalised, pending release * Swaps Update to include Optimism/BNB Chain & Polygon Swaps --- # 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-47.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.