Welcome to our latest Weekly Development Report, where we highlight ongoing progress across our ecosystem. This week, the ARK Connect team kicked off modernization efforts by upgrading styling systems, aligning dependencies, and preparing the application for Mainsail compatibility. The ARK Scan team focused on refining mobile responsiveness and layout consistency to deliver a cleaner and more polished user experience. The ARK Docs & SDKs team expanded SDK capabilities with legacy wallet support while keeping tooling up to date and improving cross-environment reliability. The ARK Vault team enhanced transaction usability, aligned with updated SDK standards, and removed outdated multisignature functionality. Meanwhile, the Mainsail team improved performance and maintainability through build optimizations, API enhancements, and continued cleanup of legacy code.
Development Activity Summary (May 08 – May 15, 2026)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from May 08, 2026, to May 15, 2026.
| Project | Commits | Authors |
|---|---|---|
| ARK Connect | 52 | 2 |
| ARK Scan | 11 | 1 |
| ARK SDKs & Docs | 16 | 3 |
| ARK Vault | 63 | 3 |
| Mainsail | 33 | 2 |
During this period, the team maintained strong productivity and engagement, delivering 175 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 began the initial modernization work on ARK Connect to prepare the project for compatibility with Mainsail and align it with more recent ecosystem changes.
As part of this effort, we carried out a major frontend refactor by upgrading Tailwind CSS from v3.4 to v4. This is a significant update, as Tailwind v4 introduces a new architecture where configuration is defined directly in CSS using @theme blocks, replacing the traditional JavaScript config file. During the migration, we updated existing utilities, removed deprecated patterns, and adjusted styling to align with the new approach, resulting in a more modern and maintainable styling system.
In parallel, we started a broader dependency update across the project. This included consolidating various package upgrades into a single effort to ensure libraries remain current outside of those covered by dedicated upgrade tasks. Keeping dependencies up to date helps improve security, performance, and long-term maintainability.
We also began aligning ARK Connect with the latest Platform SDK changes by porting over remaining updates from the shared SDK layer used in Vault. This helps maintain consistency between applications and reduces divergence, making it easier to evolve and maintain both projects moving forward.
Additionally, we improved how large numeric values are handled throughout the application. Previously, there were several instances where BigNumber values were converted into native numbers, which could lead to precision issues. We refactored this logic so BigNumber values can flow through the system more consistently and be handled appropriately at later stages, improving accuracy and reducing the risk of data loss.
Next week, we’ll continue progressing the ARK Connect modernization work, further align the application with ongoing ecosystem and SDK updates, and continue preparing the project for Mainsail compatibility.
ARK Scan Weekly Report
This week we focused on refining the mobile experience and improving layout consistency across key views in ARK Scan.
One of the fixes addressed an issue in the wallet transaction table on smaller screens. When viewing an address on mobile (640px and below), the transaction fee was being displayed twice, once in its dedicated column and again under the amount. This duplication has now been removed, ensuring that the fee is shown only where expected, resulting in a cleaner and less confusing transaction overview.
We also improved the tab navigation layout on mobile devices. Previously, the tab background did not span the full width of the screen, which made the interface feel slightly constrained. This has been adjusted so that tabs now take up the full available width on smaller screens, creating a more polished and consistent visual experience.
In addition, we fixed a layout inconsistency on the address details page. When viewing non-validator addresses, the overview and validator information sections could appear misaligned, with uneven heights between the two panels. This has now been corrected so that both sections align properly, and the validator information box stretches to fill the available space, resulting in a more balanced and structured layout.
Next week, we’ll continue focusing on UI consistency and responsiveness, while also addressing any reported issues and working on further optimizations across the application.
ARK Docs & SDKs Weekly Report
This week, we focused on extending SDK capabilities and improving compatibility with legacy wallet scenarios while also keeping the codebase up to date with modern tooling.
In the TypeScript Crypto SDK, we introduced support for generating legacy addresses. This functionality enables compatibility with addresses created under previous network formats, which is particularly important when working with historical data or migrating users into the newer Mainsail ecosystem.
Building on that, we exposed a new LegacyAddress class to better support interactions with cold wallets originating from Core snapshots. These wallets may not yet have an associated public key on the network, meaning their balances are not accessible through standard API endpoints and can return a 404. To address this, the SDK now supports making dedicated requests to the api/legacy/cold-wallets endpoint, allowing applications like Vault to retrieve balances and enable transactions from these accounts. This ensures a smoother experience for users importing older wallets into the new system.
We also resolved an issue related to “invalid BytesLike” errors encountered during testing. This was caused by mismatches in expected binary formats, and has been fixed by standardizing the use of Uint8Array instead of Buffer instances. This improves compatibility and ensures more stable behavior across environments, particularly in unit tests.
In parallel, we updated the Crypto SDK to Node 24 and refreshed its JavaScript dependencies, keeping the package aligned with the latest runtime and ecosystem improvements.
For the TypeScript Client SDK, we implemented support for interacting with the legacy/cold-wallets endpoints, along with corresponding unit tests. This complements the changes in the Crypto SDK and ensures that client applications can fully leverage the new legacy wallet handling capabilities. We also updated this package to Node 24 and refreshed its dependencies to maintain consistency across SDKs.
Next week, we’ll continue refining features, expand test coverage, and address any issues that arise as these legacy compatibility improvements are integrated into downstream applications.
ARK Vault Weekly Report
This week, we focused on improving usability in transaction flows, aligning the codebase with recent SDK changes, and removing outdated functionality.
One of the key additions was a small but useful enhancement to the send transaction flow. We introduced a contract address hint that displays a shortened version of the selected contract address (e.g., showing the ending of the address). This provides users with additional context when sending token transfers, helping them verify they are interacting with the correct contract without overwhelming the interface with long addresses.
We also fixed an issue in the sender address dropdown within transaction forms. Previously, when hovering over an address, the tooltip displaying the full value could become hidden or clipped, making it difficult to read. This has now been resolved so that tooltips are fully visible and behave consistently, improving usability when working with multiple or similar-looking addresses.
On the codebase side, we refactored all remaining usages of ArkClient to the new Client naming, aligning Vault with the updated TypeScript Client SDK. This helps maintain consistency across the ecosystem and ensures the application uses the latest standardized interfaces.
Finally, we removed support for multisignature registration within the application. Since multisignature functionality is no longer supported in Core, keeping this feature would only add unnecessary complexity and potential confusion. Disabling it simplifies the user experience and keeps Vault aligned with the current capabilities of the network.
Next week, we’ll continue refining transaction flows, address any issues identified through testing and feedback, and further improve overall usability across the application.
Mainsail Weekly Report
This week, we focused on improving performance, simplifying the codebase, and enhancing API capabilities within Mainsail.
A key improvement was introducing support for separate builds for TypeScript and Rust packages. This change significantly improves local development performance, particularly during full TypeScript rebuilds, by allowing parts of the system to be built independently. It also serves as preparation for the upcoming TypeScript 7 release, ensuring the project is ready to adopt future improvements with minimal friction.
We also continued cleaning up legacy functionality by completely removing all remaining multisignature-related code. Since this feature is no longer used or supported, removing it reduces unnecessary complexity and helps streamline the codebase, making it easier to maintain and reason about.
On the API side, we added support for a blacklist query parameter on the /tokens endpoint. This enhancement allows clients to explicitly exclude certain tokens from responses, providing more flexibility and control when working with token data.
Performance improvements were also made in transaction processing. We introduced batch-based fetching of transactions from the transaction-pool worker process. Instead of retrieving transactions individually, the system now loads them in batches until a block is full or the transaction pool is empty. This results in more efficient processing and better overall throughput.
In addition, we updated dependencies across all packages, including the root package, to their latest versions. This helps ensure better security, stability, and compatibility with the broader ecosystem. We also removed unused code from the utils package, further improving build performance and reducing overall codebase size.
Next week, we’ll focus on expanding unit test coverage and resolving any issues that arise as these improvements are exercised through continued development and testing.
Other Updates
This week, we also released ARK Core v3.12.0. This update continues the groundwork for upcoming improvements and future releases, including preparations for Mainsail integration.
You can view the full changelog here: ARK Core v3.12.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.
