Welcome to our latest Weekly Development Report, where we highlight continued progress across our ecosystem. This week, the ARK Scan team improved internal data handling by adopting modern request patterns, while enhancing token UI consistency and expanding transaction visibility. The ARK SDKs and Documentation team broadened developer accessibility by adding new language examples and modernizing the documentation stack. The ARK Vault team focused on refining token workflows, improving UI consistency, and strengthening reliability through expanded end-to-end testing. Meanwhile, the Mainsail team advanced code reliability and maintainability by increasing test coverage, upgrading tooling, and further modularizing the codebase.
Development Activity Summary (May 01 – May 08, 2026)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from May 01, 2026, to May 08, 2026.
| Project | Commits | Authors |
|---|---|---|
| ARK Connect | 0 | 0 |
| ARK Scan | 22 | 2 |
| ARK SDKs & Docs | 8 | 1 |
| ARK Vault | 41 | 2 |
| Mainsail | 22 | 1 |
During this period, the team maintained strong productivity and engagement, delivering 93 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 Scan Weekly Report
This week, we focused on improving ARK Scan by modernizing internal data handling, enhancing token-related UI, and expanding transaction visibility.
A key refactor involved migrating from Axios to the native fetch-based approach using Inertia v3’s useHttp utilities. This change aligns the codebase with the latest Inertia patterns, reduces reliance on external libraries, and simplifies how HTTP requests are handled across the application. As a result, the data-fetching layer is now more consistent and easier to maintain moving forward.
On the UI side, we improved how token transfer amounts are displayed. Token symbols are now consistently capitalized across the interface, ensuring a more uniform and professional appearance. In addition, we introduced tooltips for token transfer amounts, allowing users to view the full, precise value along with the token symbol. This is particularly useful in cases where values are truncated or formatted for readability, giving users access to the exact underlying data when needed.
We also expanded functionality on the Transaction Detail page by adding support for displaying token transfers related to contract deployments. Previously, these transactions did not show associated token movements, even though they effectively performed minting operations. This has now been addressed by integrating a token transfer display similar to the existing transfer components, with correct handling of recipients to ensure the data accurately reflects what is shown on the Token Transfers summary page.
Next week, we’ll continue focusing on testing and stability, address any reported issues, and further optimize the application to improve performance and maintainability.
ARK SDKs & Documentation Site Weekly Report
This week, we focused on improving the documentation site by expanding usage examples, modernizing dependencies, and aligning the frontend stack with the latest standards.
One of the key additions was the introduction of Java examples in the crypto documentation. By including Java alongside existing examples, we’re making the documentation more accessible to a broader range of developers and ensuring that common cryptographic operations are clearly demonstrated across multiple languages. This helps improve onboarding and provides more practical guidance for developers working in different ecosystems.
We also updated the documentation site to Node 24 and refreshed the JavaScript dependencies. This ensures the project remains up to date with current tooling, benefits from performance and security improvements, and stays aligned with the rest of the ecosystem.
In addition, we migrated the frontend styling to Tailwind v4. This upgrade brings a more modern and streamlined styling workflow, improves maintainability, and keeps the documentation site consistent with the latest UI standards used across related projects.
Next week, we’ll continue enhancing the documentation by expanding examples, refining content, and addressing any reported issues to further improve the developer experience.
ARK Vault Weekly Report
This week, we focused on enhancing ARK Vault through a combination of functional improvements, UI refinements, and expanded test coverage, with particular attention on token-related workflows and overall interface consistency.
A key improvement was the implementation of token refresh functionality. Users can now reliably refresh token data, ensuring that balances and token information stay up to date after actions such as adding or interacting with tokens. As part of this, we also refined the visual feedback by adjusting the refresh icon styling, making the interaction clearer and more intuitive.
We addressed several UI issues across the application to improve consistency and usability. This included fixing divider inconsistencies in various modals to ensure a cleaner and more structured layout. We also resolved a balance overflow issue in the token deletion modal, where large values could previously break the layout. In addition, we refined hover states within the send transfer form, making interactions feel more consistent with the rest of the interface.
On the form and interaction side, we introduced a redesigned asset dropdown in the send flow. This update improves the usability and visual clarity of token selection, aligning it with the latest design standards used throughout the application. We also improved transaction amount tooltips so that they now always display the full, untruncated value, even when the on-screen representation is shortened for readability—bringing this behavior in line with the token transfers view.
Testing was another major focus this week. We fixed and re-enabled end-to-end tests for the portfolio and settings domains, restoring confidence in these critical areas of the application. In addition, we introduced new E2E tests for the tokens domain, helping ensure that token-related functionality is thoroughly validated and less prone to regressions as development continues.
As part of ongoing preparations for future updates and Mainsail compatibility, we also disabled the multisignature registration feature to align the application with upcoming architectural changes.
Next week, we’ll continue focusing on stability and usability improvements, address any issues identified through testing and user feedback, and further refine token-related workflows across the application.
Mainsail Weekly Report
This week, we focused on improving code reliability, modernizing tooling, and further modularizing the Mainsail codebase.
A significant part of the work was dedicated to increasing unit test coverage across several core packages, including crypto-validation, blockchain-utils, and evm-state. Strengthening test coverage in these areas helps ensure the correctness of critical logic related to validation, blockchain operations, and state management. This not only reduces the risk of regressions but also provides a more solid foundation for future development.
We also updated the project to use pnpm version 11.0.0 and aligned related environment variables within our Dockerfiles. These updates help standardize the development and build environments, improve dependency management performance, and ensure consistency across local and containerized setups.
In addition, we continued improving the structure of the codebase by extracting forging-related logic into a dedicated @mainsail/forger package. This separation makes the code more modular and easier to maintain, while also allowing forging functionality to evolve more independently from the rest of the system.
Next week, we’ll continue focusing on expanding unit test coverage and addressing any issues that arise, particularly as more components are exercised through ongoing development and testing.
Other Updates
This week, we have also released a new version of ARK Core v3.11.0. This update is part of the ongoing groundwork for upcoming improvements and future releases, including preparations related to Mainsail.
The full changelog for this release is available here: ARK Core v3.11.0 Changelog
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.
