Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, the ARK Scan team focused on enhancing multipayment functionality, improving performance, and updating design elements, while the ARK Vault team delivered a mix of general fixes and new features. Meanwhile, the Mainsail team concentrated on optimizing multipayment handling and block processing to further strengthen overall performance.
Development Activity Summary (August 15 – August 22, 2025)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from August 15, 2025, to August 22, 2025.
| Project | Commits | Authors |
|---|---|---|
| ARK Connect | 0 | 0 |
| ARK Scan | 15 | 1 |
| ARK SDKs & Docs | 0 | 0 |
| ARK Vault | 90 | 4 |
| Mainsail | 17 | 2 |
During this period, the team maintained strong productivity and engagement, delivering 122 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 concentrated on enhancing multipayment functionality, optimizing performance, and updating design elements. Key tasks completed included:
- Refactored wallet transaction processing to bypass multipayment-specific logic when multipayments are not present, boosting performance and reducing unnecessary queries that previously slowed down the transaction page.
- Improved transaction handling by querying the multipayment recipients table directly, eliminating extra queries and speeding up transaction page load times.
- Updated the “Copy” icon color to grey to align with ARK Vault styling.
- Adjusted the light mode badge so the From and To text now uses
gray-700. - Refined the “No results” message with better line height and added spacing between placeholder text, enhancing readability and creating a cleaner layout.
- Updated the Contract badge styling to match the Unvote tag, featuring a grey background and border.
- Revised filtering logic so “Validator Update” transactions now appear under the Validator filter instead of Other, ensuring accurate categorization and clarity when filtering.
- Enhanced the validator-monitor page with Inertia implementation and optimizations to lower resource usage, improving overall performance.
- Formatted the transaction count on the
/transactionspage to use standard number formatting (e.g., 183,853) for improved readability and consistency across the app.
Next week, we plan to continue refining design elements and implementing additional optimizations to achieve faster loading times.
ARK Vault Weekly Report
This week, we worked on general fixes as well as new features. Work completed includes:
- Implemented design updates for the Select Sender modal, ensuring it matches the latest specifications. The component now shows fiat amounts only on mainnet and applies the updated styling across all reused instances, including the Receive flow.
- Implemented caching for notifications by storing fetched notification transactions in local storage, keyed by profile ID to avoid mixing data. Cached notifications are now shown instantly on reloads or errors, and updated when new transactions are fetched. Unit tests were updated to cover this behavior.
- Implemented handling for insufficient gas errors in transactions by checking if no other error is present and if the gas used is within ~95% of the set gas limit. When detected, Vault now shows “insufficient gas” as the failure reason in transaction details, mirroring ARK Scan’s approach.
- Moved transaction details from the modal to the side panel, so clicking a transaction in the table now opens its details in the side panel for a more consistent user experience.
- Implemented design updates for the Select Recipient modal on mobile, aligning it with the latest specifications and ensuring consistency with the updated Select Sender flow.
- Updated notification logic to support multiple addresses, enabling notifications to be fetched and displayed across all tracked addresses.
- Applied minor UI adjustments to the Select Sender modal: made the entire row clickable, updated tooltips, and fixed hover and selected row colors.
- Improved multi-address view by automatically switching to single view when only one address remains, replacing the “Multiple Addresses (1)” display.
- Implemented Mainsail profile migration for settings, converting imported settings to the new format during profile import.
- Fixed wallet alias consistency by ensuring address names display uniformly in the recipient search modal for transactions, with updated unit tests to cover this behavior.
- Fixed transaction status handling in transaction details to properly reflect failed transactions. Pending transactions now update to show contract failures immediately instead of displaying incorrect confirmations, without requiring a page refresh.
- Implemented Mainsail profile migration for contacts by converting them to the new format during import.
- Modified Address Name behavior on mobile by adding a top offset to the edit modal and opening it in the sidebar as an additional screen, preventing accidental closure of sidebar.
Next week, we’ll continue improving Mainsail integration and work on further design updates to enhance user experience.
Mainsail Weekly Report
This week, we worked on multipayment and block processing optimizations. Key work included:
- Updated package dependencies to the latest versions.
- Upgraded TypeScript and set the target to ES2023.
- Synced multipayments to the Postgres database.
- Improved block processing performance by using Node workers to parallelize transaction deserialization.
- Reran tests on the main and develop branches after merges to publish Codecov reports.
- Increased unit test coverage for blockchain-utils.
Next week, our focus will be on further improving test coverage and implementing API enhancements based on feedback from the Vault and Scan teams.
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.
