> 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-4.md). # Week 4 * ARC Reactor User Guides page - complete * ARC Reactor New UI - 70% complete * On-going discussions with two large procurement management and supply chain logistics conglomerates over utilising Reactor Technology and ARC Programming Language * Onboarding of closed-beta participants ongoing - commence testing 01 Feb * ARC Focus on grant opportunities for development * ARC Focus on incubator opportunities for business development * Ongoing graphics production for multiple campaigns * Swaps 2.0 UI mock-ups are being revamped and updated - multiple additions * Finalizing feedback portal for the beta-testers * High level strategy meeting on DeFi Ecosystem 2.0 * Reduction in farm staking APY from: 20.5% --> 14% -- SSS 22% --> 17% -- ARC/WETH (reducing emission rates for utility token) * NFT Marketplace to be temporarily shutdown to reduce back end costs and revamp * Continuing research on 'All of Crypto in 3 Clicks' --- # 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-4.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.