ARK Development Report - September 5, 2025

Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, the ARK Scan team improved failed transaction feedback to make errors clearer and more actionable, while also integrating Simple Analytics for better insights. The ARK Vault team enhanced the side panel by integrating additional flows and delivered improvements to Ledger support. Meanwhile, the Mainsail team concentrated on bug fixes and continued refining the API with further enhancements.

#Development Activity Summary (August 29 – September 5, 2025)

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

During this period, the team maintained strong productivity and engagement, delivering 107 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 improved the feedback on failed transactions to make errors clearer and more actionable, and we also integrated Simple Analytics. Work done included:

• Updated queries to reflect the removal of the receipts table, now using the corresponding column directly in the transactions table instead.
• Updated transaction details to use the new decodedError column for failed transactions instead of decoding receipts manually. Errors are now displayed in a more readable format. If the error is execution reverted, an additional gas usage check is performed: near-limit cases show “Out of gas”, while others display the general “Error encountered during contract execution” message.
• Integrated Simple Analytics to track visitor counts and page popularity on Scan. Added event tracking for key interactions such as exports, legacy addresses, and other modals. Tracking is limited to generic usage data only, ensuring no user-specific data is collected.

Next week, we’ll continue improving overall performance and address any reported issues.

#ARK Vault Weekly Report

This week, we focused on improving the side panel by integrating more flows into it, along with enhancements to the Ledger. Work done included:

• Improved transaction handling for Ledger accounts by detecting when the device is not connected or the Mainsail app is not open. Instead of failing immediately, the user is now prompted within the transaction flow to resolve the issue. This ensures smoother UX and prevents unnecessary transaction errors.
• Fixed an issue where the transaction table displayed data from the wrong address after importing a Ledger account. The table now correctly syncs with the selected Ledger profile, and refreshing no longer removes the imported Ledger address. This ensures accurate transaction history and consistent profile behavior.
• Corrected the header colors for the Select Sender and Select Recipient modals.
• Fixed multipayment transaction classification when the sender is also a recipient, preventing all recipients from being labeled as “Return.” Now only the sender’s own line is treated as a return (if applicable), while other recipients correctly show as incoming with the proper received amount.
• Moved the Vote/Unvote flow from pages to the side panel, aligning it with the updated transaction flow design. This makes the experience consistent with other transactions, improves usability, and allows for better reuse of side panel logic.
• Updated voting logic so that vote swaps are now handled as a single vote transaction rather than including both unvotes and votes. This prevents double-signing prompts on Ledger wallets and simplifies the flow by only including the new voting address.
• Added “Back” and “Retry” buttons to the Ledger import error page, allowing users to retry or navigate back when an error occurs. The handleRetry method was refactored to support different retry logic based on the Ledger step, improving error recovery and user experience.
• Implemented profile import migration to convert existing .wwe files for compatibility with the Mainsail version of Vault.
• Added a FeeService to the Network for streamlined fee handling via network.fees(). Also moved the transaction ABI encoder into a standalone TransactionEncoder class for better encapsulation and reuse in gas estimations.
• Refactored username and validator transactions by moving registration, resignation, and update flows into the side panel, unifying the transaction experience.
• Updated the Devnet manifest configuration to use the correct nethash value, ensuring proper network identification and connectivity.

Next week, we’ll continue refining the side panel, begin work on new features coming into Vault, and address any issues that arise.

#Mainsail Weekly Report

This week, our focus was on bug fixes and continued API enhancements. The work completed includes:

• Updated node sync status determination to use the median (90th percentile).
• Added pagination support for the /unconfirmed endpoint in the transaction pool API.
• Strengthened RLP validation to prevent adding extra fields or bytes to serialized transactions.
• Improved transaction pool handling by resetting sender state when no transactions remain after a block commit.
• Fixed the Mainsail update process by adding support for the --allow-build flag, enabling automatic execution of post-install build scripts for packages that need rebuilding after version changes.

Next week, we will focus on preparing a new version for the public testnet that incorporates all recent updates. We will also continue expanding test coverage and implementing further API improvements.

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