Welcome to our latest Weekly Development Report, where we highlight ongoing progress across our ecosystem. ARK Connect added side panel support this week, along with cleaner interaction flows that make the extension easier to use in more places. ARK Vault spent the week on foundations: the team upgraded its development stack, fixed several UI issues, and added a good deal of new test coverage. Mainsail shipped performance and storage optimizations and made builds more reliable, and unit test coverage on the core components kept growing.
Development Activity Summary (May 29 – June 05, 2026)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from May 29, 2026, to June 05, 2026.
| Project | Commits | Authors |
|---|---|---|
| ARK Connect | 18 | 2 |
| ARK Scan | 0 | 0 |
| ARK SDKs & Docs | 0 | 0 |
| ARK Vault | 74 | 2 |
| Mainsail | 16 | 2 |
During this period, the team maintained strong productivity and engagement, delivering 108 merged commits across all projects.
It’s important to note that weekly commit counts and project-specific data may fluctuate based on the focus of internal sprints, evolving objectives, and the complexity of tasks undertaken.
ARK Connect Weekly Report
This week, we focused on enhancing the extension experience by introducing browser-side panel support, improving usability, and refining transaction-related UI behavior.
A major highlight is the addition of side panel support, allowing ARK Connect to run in the browser’s side panel instead of being limited to the pop-up. This provides more vertical space and a more persistent interface. We also introduced a setting that lets users switch between pop-up and side panel modes, with the pop-up remaining the default for now.
To support this new layout, we improved responsiveness across the extension so it adapts smoothly to both narrower pop-up views and wider side panel dimensions. We also fixed issues related to the panel toggle state to ensure it accurately reflects the current mode in settings and behaves consistently when switching between views.
On the UI side, we fixed an issue where duplicate transaction hashes were displayed in transaction details. We also improved navigation by reordering the Transactions and Tokens tabs, making Transactions the default view and placing it first for a more intuitive user experience.
Overall, these changes significantly improve flexibility, usability, and consistency across the extension.
Next week, we’ll continue refining the side panel experience, proceed with ongoing Mainsail integration work, and address any issues identified during internal testing.
ARK Vault Weekly Report
This week, we focused on modernizing the development stack, improving UI behavior, and significantly expanding test coverage across ARK Vault.
A major part of the work involved upgrading dependencies, including large-scale updates to ESLint (v10), Vite (v8), TailwindCSS, Vitest, and multiple related plugins. These updates ensure the project stays aligned with the latest tooling, improves performance, and benefits from ongoing ecosystem improvements. As part of this effort, we also removed several unused or deprecated packages, such as jest-styled-components and some Vite plugins, helping reduce complexity and keep the codebase lean. Additionally, we introduced @eslint/compat to maintain compatibility with older plugins during the transition.
On the UI side, we improved the default asset selection logic by ensuring ARK is preselected when no other tokens are available, providing a smoother user experience. We also refined the token details view by introducing a new WalletAddress component alongside a MiddleTruncation utility, enabling more accurate and responsive address display. These changes simplify the component structure and resolve layout issues such as spacing between the contract address and the copy button.
Testing was another key focus this week. We increased coverage across several critical areas, including ledger migration, wallet import flow, notifications, portfolio components, and address side panels. We also raised coverage thresholds within the portfolio domain and fixed flaky application tests to improve CI reliability.
Overall, these changes result in a more modern, maintainable, and well-tested codebase with improved user experience.
Next week, we’ll continue progressing with major dependency upgrades, further expand and stabilize test coverage, and begin incrementally refactoring shared UI components (such as migrating remaining address usages to the new WalletAddress component), while addressing any issues identified during testing and development.
Mainsail Weekly Report
This week, we focused on improving performance, storage efficiency, and building reliability across Mainsail, while continuing to expand unit test coverage.
A key fix was implemented in the api-sync package, resolving an issue where validator rounds were being reset after each batch during restore. This ensures more stable and consistent synchronization behavior.
On the build and distribution side, we removed support for musl-based builds due to unmaintained Docker images from napi. We also fixed issues in the release workflow by properly including optional platform-specific dependencies (such as @mainsail/evm-linux-x64-gnu), ensuring smoother and more predictable builds across environments.
Performance and storage optimizations were another major focus. We implemented conditional compression in the EVM layer, skipping compression for values that do not benefit from it (such as short values or transaction hashes). This results in improved performance while also reducing unnecessary disk usage.
We also improved how transactions are stored in EVM storage by updating the transaction key format. The new approach enables proper numerical ordering instead of lexicographical sorting, unlocking more efficient range scans. Building on this, we added support for reading commits from EVM storage in batches, with configurable limits based on block height or maximum byte size, further improving performance and scalability.
Finally, we continued strengthening test coverage. Both the transaction-pool-broadcaster and evm service packages have now reached 100% unit test coverage, increasing confidence in these critical components.
Next week, we’ll extend unit test coverage to the remaining packages and keep optimizing the storage and synchronization flows. We’re also adding a post-install script to make EVM package builds more reliable on non-GNU systems, and we’ll clean up anything that’s surfaced from the recent changes.
Feedback & Feature Requests
If you are using our open-source products and would like to provide feedback or request a feature, please feel free to contact us via the contact pages for the specific product you are using or open an issue on GitHub.
Quick access links to GitHub issues pages:
Follow on Twitter (X)
Follow us on X (Formerly Twitter) and keep checking the blog to stay up-to-date on all of our new releases. We post a weekly development report so you can easily see what we’ve been up to and follow along our journey towards making your decentralized future a reality.
