ARK Development Report - August 15, 2025

Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, in ARK Connect, we removed the unused ‘memo’ field from extension pages and components to align with Mainsail changes, while the ARK Scan team streamlined the app by consolidating multiple tabbed components into a single, more efficient structure. On the documentation side, we focused on improving clarity and accuracy. The ARK Vault team introduced new features such as pending transactions, along with general design updates and fixes. Meanwhile, the Mainsail team refined the API based on feedback and implemented performance improvements to further optimize the platform.

#Development Activity Summary (August 8 – August 15, 2025)

Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from August 8, 2025, to August 15, 2025.

During this period, the team maintained strong productivity and engagement, delivering 79 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 removed the memo field from extension pages and components, as it is no longer used in Mainsail.

Next week, we will continue addressing Mainsail changes and resolving any issues reported by our internal team.

#ARK Scan Weekly Report

This week, we refactored parts of the app by consolidating multiple tabbed components into a single component.

We also updated app/Http/Livewire/Validators/Tabs.php to handle filters, fixing navigation errors when using the browser’s back button. We are also working on an Inertia implementation of the Validator Monitor to reduce its resource requirement over prolonged use.

Additionally, we merged mainsail-develop into the mainsail branch.

Next week, we will keep working on reported issues and continue optimizing for faster loading times and lower resource usage.

#ARK SDKs & Docs Weekly Report

This week, we focused on improving the clarity and accuracy of our documentation. Specifically, we updated the example for configuring the validator public key, ensuring that developers have a more precise and easy-to-follow reference.

These changes aim to reduce setup confusion and help both new and experienced developers implement the configuration correctly.

Next week, we will continue addressing any issues reported by the community. In addition, we plan to further enhance the Mainsail documentation by adding more detailed explanations, refining existing examples, and expanding general documentation.

#ARK Vault Weekly Report

This week, we have worked on introducing new features like pending transactions as well as general design updates and fixes. Work done included:

• Added support for pending transactions with a new hourglass icon, adjusted transaction ID layout, created a use-pending-transactions hook for local storage management, and refactored use-profile-transactions to merge pending and confirmed transactions. All transaction forms now store newly created transactions in local storage until confirmed.
• Aligned detail titles in review steps for consistent text placement across pages.
• Updated the wallet label in the import success step to display the correct wallet name.
• Refactored the Votes table to show a tooltip when wallet balance is 0 and updated AddressRowMobile to disable the Vote button when Ledger is unsupported, matching AddressRow behavior.
• Fixed the image shake on the Ledger connection step by hiding the scrollbar and ensuring the section takes full height.
• Added the missing illustration for the Ledger import step in dim mode.
• Adjusted multipayment display to show “Multiple (1)” for a single recipient, linking to the explorer for consistency.
• Introduced tooltips for buttons disabled due to 0 balance with consistent text: “Disabled due to insufficient balance,” including vote transactions.
• Restored default password input behavior for the mnemonic field by rolling back previous custom input changes.
• Refactored API interactions to route all HTTP requests through centralized library services, improving maintainability and consistency.
• Corrected alignment of delete address buttons in the addresses side panel.
• Updated the UpdateWalletName modal to match the latest designs, replacing “Wallet Name” with “Address Name” and ensuring proper layout across breakpoints.
• Removed the JSON profile import feature along with all related tests, fixtures, and supporting code.
• Added padding in the “Remove Password” section of Settings for better visual alignment.
• Refined profile job handling to run synchronizers only for the active profile.
• Enabled browser “Back” button support for sidepanels; step-based sidepanels like ImportAddressSidepanel now handle actions based on the current step using onBack and hasSteps props.
• Implemented Mainsail profile migration for wallets, converting old addresses to the new format during import.
• Fixed table filtering logic so the “other” filter correctly includes all transaction types not covered by other options.
• Refined mobile navigation to hide the bottom bar on transaction flow screens.
• Adjusted wallet deletion alert on mobile to remove extra white space under the message.
• Updated semantic HTML on the Welcome page and introduced StyledRouterLink for styled internal links, with corresponding unit tests and snapshots updated.
• Improved Send All logic to handle cases where the amount plus fee exceeds the address balance, automatically adjusting single recipient transfers and showing an error for multiple recipients. Unit tests were added.
• Stabilized profile and message tests by mocking the delay function to remove timing issues from setTimeout.

Next week, we’ll continue to improve based on the feedback from the community as well as internal testing.

#Mainsail Weekly Report

This week, we refined the API based on feedback and worked on performance improvements. Work completed includes:

• Write multi-payments to the Postgres database to improve API efficiency
• Allow filtering of unconfirmed transactions by sender or recipient.
• Replaced keccak256 usages with native implementations where possible for better performance.
• Added an explicit Assert type to resolve TypeScript complaints.
• Updated the pino logger dependency.
• Updated EVM dependencies.

Next week, our primary focus will be on continued testing and addressing any issues reported by the internal team and the community. We’ll also work on further API enhancements.

#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:

• Mainsail
• ARK Connect (Extension)
• ARK Connect (Demo)
• ARK Scan
• ARK Vault

#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.