ARK Development Report - September 26, 2025

Development Activity Summary (September 19 – September 26, 2025)

The development team has been actively working on several key projects, with a total of 115 merged commits across all projects during the period of September 19, 2025, to September 26, 2025. The 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

The ARK Scan team addressed validator status issues and enhanced deeplinks support. Key improvements include:

• •
  Validators without a BLS key are now correctly identified as dormant, resolving an issue where they were incorrectly displayed as active. The active, standby, and dormant states are now consistently reflected on the address details page.
• •
  The deeplink for voting has been updated to consistently use `publicKey=` instead of `validator=`. This change ensures compatibility even when a validator has no registered username, simplifying handling and guaranteeing valid URIs.
• •
  Dusk tests have been set up, and a missed warning was fixed. This ensures that testing functions correctly with Inertia, as React generates pages via the DOM, and allows the monitor PR tests to be included in workflows.

Future work will involve continued enhancement of tests, overall performance improvements, and addressing any reported issues.

ARK Vault Weekly Report

This week's efforts on ARK Vault focused on developing pending transactions and HD wallet features, alongside general fixes and app improvements. Completed tasks include:

• •
  Pending transactions are now fetched from the `/transactions/unconfirmed` endpoint via the `pending-transactions.service`. A new `Pending Transactions DTO` has been added to manage transaction types and properties, and query parameters for filtering by recipient and sender have been implemented.
• •
  The HD wallet option has been incorporated into the wallet creation flow, with logic to appropriately show or hide this option.
• •
  A general HD wallet creation flow has been added, enabling users to create HD wallets in a manner similar to the regular address creation process, ensuring a consistent and complete workflow for HD wallet management.
• •
  The `TimeAgo` component for pending transactions has been fixed to update correctly. This ensures that the "Time Ago" column for each row accurately reflects the elapsed time, even when no new transactions are added.
• •
  Account name functionality has been added for HD wallets during the import flow, allowing users to assign and view names for imported HD wallet accounts.
• •
  The create wallet flow has been updated to prevent application crashes when exiting the mnemonic generation step. This resolves a `TypeError` that occurred due to accessing undefined properties.
• •
  The HD wallet flow has been updated to display a guiding message for users to use the import option when adding additional addresses.
• •
  The periodic fetching of unconfirmed transactions has been moved from the component level to the profile job handler. This reduction in multiple API requests caused by component re-renders ensures consistent caching and handling of unconfirmed transactions across the portfolio page.
• •
  Transaction signing for HD wallets now supports the encryption password option, enabling secure signing for encrypted HD wallet addresses.
• •
  HD wallet addresses in the portfolio are now highlighted with a dedicated label, visible in both mobile and desktop views, as well as in the side panel. Label styles have been refactored to include outline, primary, and neutral variants for consistent presentation.
• •
  The side panels for validator and username resignations have been updated to align with the latest designs, including a modern variation for the wallet selector. New unit tests have been added to ensure these changes do not introduce regressions.
• •
  All instances of "wallet" in the UI have been replaced with "address," and corresponding translation keys and content have been updated. Unused translations have been removed, and implementations, unit tests, and snapshots have been updated for codebase consistency.
• •
  The address alias generation for HD wallets has been corrected to use the proper index. Aliases now correctly reflect "Address #counter" instead of the previously incorrect "Address #counter+1," ensuring accurate and consistent labeling for generated addresses.
• •
  HD wallet-related classes, methods, files, and variables have been renamed to adhere to BIP-44 naming conventions, enhancing clarity and consistency across the codebase.
• •
  The profile transactions view has been optimized to prevent multiple unnecessary renders, improving performance and ensuring smoother updates when transaction data changes.
• •
  Link styling has been removed from the address row on the vote page, improving visual consistency and reducing confusion by presenting the row as standard text rather than a clickable link.

Upcoming work will focus on further progress with the HD Wallet implementation, enhancing Ledger hardware support, and addressing any other reported issues.

Mainsail Weekly Report

A new version of Mainsail EVM, v0.0.1-rc.6, has been released for the public testnet. This update introduces several improvements:

• •
  The transaction pool API now supports filtering by the `from` and `to` fields.
• •
  Networking includes NTP time offset logging for enhanced synchronization visibility.
• •
  Consensus logs have been updated with a new format displaying height, round, and hash.
• •
  The `lint.sh` script has been removed.
• •
  A new `db:drop` command has been added to the API.
• •
  Syncing now utilizes less memory, leading to improved overall efficiency.
• •
  Consensus log formatting has been improved to use `toLocaleString` with English format (en-US) outputs.

Further improvements have been made to other aspects of Mainsail:

• •
  Support for re-processing downloaded blocks in consensus has been added. This addresses edge cases in block processing that are not directly caused by consensus failures but by invalid node time settings. Blocks that were previously rejected because they appeared to be from the future due to unsynchronized node clocks are now reprocessed and accepted later.
• •
  NTP sync is now enabled by default in the `install.sh` script.
• •
  `getCommitBytes` has been introduced, utilizing a single database call in the EVM package to enhance performance.
• •
  Functional consensus tests have been restored, and GitHub workflows for these tests are now enabled.
• •
  The network generator has been extended to produce tests for functional consensus.
• •
  Support for reading usernames from snapshots during database restore has been added.

Next week's focus will be on improving unit testing and increasing test coverage.

Feedback & Feature Requests

Users of our open-source products are encouraged to provide feedback or request features. Please 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