Welcome to our latest Weekly Development Report, where we highlight ongoing progress across our ecosystem. This week, the ARK Scan team focused on internal testing and evaluation, validating recent upgrades while identifying opportunities for performance improvements and UX refinements. The ARK SDKs and Documentation team improved consistency by standardizing naming conventions across documentation and SDKs, creating a more unified developer experience. The ARK Vault team delivered a range of bug fixes, UI enhancements, and testing improvements to strengthen reliability and polish the overall user interface. Meanwhile, the Mainsail team simplified the codebase and improved security by migrating to native BigInt, updating dependencies, and expanding API capabilities for more flexible token data access.
Development Activity Summary (April 24 – May 01, 2026)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from April 24, 2026, to May 01, 2026.
| Project | Commits | Authors |
|---|---|---|
| ARK Connect | 0 | 0 |
| ARK Scan | 0 | 0 |
| ARK SDKs & Docs | 16 | 1 |
| ARK Vault | 55 | 2 |
| Mainsail | 49 | 3 |
During this period, the team maintained strong productivity and engagement, delivering 120 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, our efforts were centered on continued internal testing and evaluation of ARK Scan rather than active code changes. We focused on thoroughly reviewing the app to identify potential performance optimizations and areas for improvement. This included validating recent upgrades and fixes, observing real-world usage scenarios, and noting opportunities to further refine the user experience and interface consistency.
These internal testing cycles are helping us ensure that the system remains stable, intuitive, and ready for broader usage, while also guiding future development priorities based on observed behavior and feedback.
Next week, we’ll continue focusing on performance optimizations and will address any issues reported on the public testnet. We’ll also keep working on general codebase cleanup to improve readability, maintainability, and long-term scalability.
ARK SDKs & Documentation Site Weekly Report
This week we focused on improving consistency and clarity across our SDKs and documentation by standardizing some naming conventions.
On the ARK documentation site, we updated references in both the TypeScript and Python sections, renaming ArkClient to simply Client. This change helps streamline the developer experience by removing redundant naming and making the API feel more intuitive and aligned across different languages. It also ensures that examples and guides remain clear and easy to follow for new and existing developers.
In the Python and TypeScript Client SDKs, we applied the same renaming by replacing ArkClient with Client throughout the package. This brings the implementations in line with the updated documentation and establishes a more consistent interface for developers integrating with the SDK.
While this is largely a structural and naming-focused change, it plays an important role in maintaining a clean and cohesive ecosystem across our tooling and documentation.
Next week, we’ll continue improving the documentation site and SDKs, while also addressing any reported issues to further enhance the developer experience.
ARK Vault Weekly Report
This week we focused on improving ARK Vault through a combination of targeted bug fixes, UI refinements, and increased test stability, with a strong emphasis on consistency and overall user experience.
On the token functionality side, we resolved an issue with incorrect balance formatting in the token deletion modal. Previously, balances could appear as extremely small values due to decimals (such as 18 decimal places) not being handled correctly. This has now been fixed, so users see accurate and human-readable values when reviewing token balances before deletion. We also addressed a gap in token transfer visibility: while newly added (whitelisted) tokens were correctly displayed in the token overview, their transfers were not appearing in the transfers tab. This was resolved by ensuring whitelisted tokens are properly included in transfer queries, along with introducing the correct query parameter handling. As part of this improvement, we also updated the empty state messaging in the transfers view to more clearly communicate when no transfers are found for the selected tokens.
We implemented a wide range of UI and UX improvements across the application to ensure a more consistent and polished interface. This included aligning hover states across side panel controls (such as Full Screen, Minimise, and Close) with modal behavior, restoring missing hover states on primary action buttons, and ensuring consistent hover color transitions for portfolio header actions like Add Token, Import, and Create. On mobile, we added a missing icon to the token page header and corrected asset icon sizing in the token selection flow to maintain visual consistency. We also refined interaction details such as hover states for token action buttons (Manage, Save, Cancel), improved typography for transaction inputs to ensure readability across screen sizes, and adjusted spacing within forms—for example, reducing excess padding in the token selection form to create a more balanced layout.
On the validation and transaction side, we fixed an issue affecting multi-payment transactions, ensuring that validation behaves correctly even when switching between different tokens. This helps prevent incorrect input handling and improves reliability when constructing more complex transactions.
Testing was another major focus this week. We fixed and re-enabled end-to-end tests across multiple domains, including voting, transactions, contacts, dashboard, profile, and messaging. This restores confidence in key user flows and ensures broader coverage across the application. We also addressed flaky behavior in the Amount Label component tests, improving overall test reliability and reducing intermittent failures.
Next week, we’ll continue focusing on testing and stability, address any issues reported during testnet usage, and further refine the user experience based on feedback from both the internal team and the wider community.
Mainsail Weekly Report
This week, we focused on simplifying the codebase, improving security, and expanding API capabilities within Mainsail.
One of the most significant changes was the complete removal of the custom BigNumber class from the utils package. All parts of the codebase that previously relied on BigNumber have now been migrated to use native BigInt. This is an important step toward reducing complexity and improving performance, as BigInt is natively supported by the runtime and integrates more efficiently with features such as inter-process communication. It also helps standardize numeric handling across the project and aligns with our broader effort to move away from legacy abstractions.
We also updated the protobufjs dependency to its latest version. This update addresses a known security vulnerability, ensuring that serialization and data handling remain secure and up to date with current best practices.
On the API side, we introduced support for filtering tokens using a tokenAddress query parameter in the /wallets/{id}/tokens endpoint. This enhancement provides more flexibility for clients, allowing them to request and work with a more targeted subset of token data, which can be especially useful for integrations and performance-sensitive use cases.
In addition, we continued strengthening code reliability by working on unit tests, helping ensure that recent changes—particularly around numeric handling and API behavior—are properly validated and less prone to regressions.
Next week, we’ll continue expanding test coverage, monitor the impact of the BigInt migration, and address any issues reported by the community as usage of the updated testnet continues.
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.
