ARK Development Report - September 5, 2025

Development Activity Summary

This report details the development efforts of the ARK Scan, ARK Vault, and Mainsail teams for the period of August 29 to September 5, 2025. The development team maintained strong productivity, delivering a total of 107 merged commits across all projects. Commit counts and project-specific data may vary based on internal sprint focuses, evolving objectives, and task complexity.

ARK Scan Weekly Report

The ARK Scan team focused on improving user experience by making failed transaction feedback clearer and more actionable. They also integrated Simple Analytics for enhanced insights into user behavior.

Key Updates:

• •
  Updated queries to directly utilize the `decodedError` column in the transactions table for failed transactions, eliminating the need for manual decoding of receipts. This change provides more readable error messages. For execution reverted errors, a gas usage check is performed: cases near the limit display "Out of gas," while others show a general "Error encountered during contract execution" message.
• •
  Integrated Simple Analytics to track visitor counts and page popularity, including event tracking for key interactions like exports and modals. This tracking is limited to generic usage data, ensuring no user-specific information is collected.

The team will continue to focus on overall performance improvements and address reported issues in the upcoming week.

ARK Vault Weekly Report

This week, the ARK Vault team enhanced the side panel by integrating additional flows and delivered improvements to Ledger support.

Key Updates:

• •
  Improved transaction handling for Ledger accounts by detecting when the device is not connected or the Mainsail app is not open. Users are now prompted within the transaction flow to resolve these issues, leading to a smoother user experience and fewer 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 the page no longer removes the imported Ledger address, ensuring accurate transaction history.
• •
  Corrected the header colors for the Select Sender and Select Recipient modals.
• •
  Fixed multipayment transaction classification when the sender is also a recipient. This ensures that only the sender's own line is treated as a "Return" (if applicable), while other recipients correctly display the incoming amount.
• •
  Moved the Vote/Unvote flow from pages to the side panel to align with the updated transaction flow design, improving usability and allowing for better reuse of side panel logic.
• •
  Updated voting logic to handle vote swaps as a single vote transaction, preventing double-signing prompts on Ledger wallets and simplifying 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.
• •
  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()`. The transaction ABI encoder was also moved 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.

In the next week, the team will continue refining the side panel, begin work on new features, and address any arising issues.

Mainsail Weekly Report

The Mainsail team concentrated on bug fixes and continued API enhancements during this period.

Key Updates:

• •
  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 the addition of 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 require rebuilding after version changes.

Next week, the team will focus on preparing a new version for the public testnet, expanding test coverage, and implementing further API improvements.

Feedback and Feature Requests

Users are encouraged to provide feedback or request features for the open-source products. This can be done via the contact pages for the specific product or by opening an issue on GitHub.

GitHub Issues:

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

Stay Updated

Follow ARK Ecosystem on X (Formerly Twitter) and check the blog regularly for updates on new releases and development progress. Weekly development reports provide insights into the team's activities and their journey towards a decentralized future.