ARK Development Report - October 24, 2025

This week's development report highlights the ongoing efforts of the ARK development team across several key projects. The ARK Scan team continued its Inertia migration and implemented general improvements. The ARK Vault team advanced the Ledger migration feature, while the Mainsail team focused on database enhancements, performance optimizations, and updates to logging and P2P functionality to bolster reliability.

Development Activity Summary (October 17 – October 24, 2025)

The development team demonstrated strong productivity between October 17, 2025, and October 24, 2025, with a total of 94 merged commits across all projects. This figure may vary weekly due to internal sprint focuses, evolving objectives, and task complexity.

ARK Scan Weekly Report

The ARK Scan team continued progress on the Inertia migration and implemented several general development improvements. Key updates include:

• •
  Updated the .nvmrc file to use Node.js version 22, replacing the outdated version 12 reference to align with the project’s current environment and avoid nvm-related issues.
• •
  Integrated the typescript-transformer package to automatically generate TypeScript definitions from data objects, removing the need for manual type creation and ensuring consistent typing throughout the codebase.
• •
  Added an Inertia-powered option to vote for a validator directly from ARK Scan when viewing a validator’s address, streamlining and simplifying the voting process.
• •
  Replaced remaining manual types with Laravel-generated Spatie Data Objects that automatically convert to TypeScript. Introduced resources/inertia/global.d.ts to define shared PageProps, improving type reuse and consistency across current and future Inertia pages.

Next week, the team will continue the Inertia migration, address reported issues, and implement further general improvements.

ARK Vault Weekly Report

This week's development for ARK Vault was primarily concentrated on the Ledger migration feature. Notable work completed includes:

• •
  Implemented Ledger connection handling for the migration flow, requiring users to connect their Ledger device before starting migration. The side panel now opens with a “Connect your Ledger” prompt, consistent with the existing Ledger import experience.
• •
  Added support for 1:1 Ledger migration, enabling users to migrate a single address directly. After selecting an address, transaction details are displayed for review, sent to the connected Ledger for approval, and upon confirmation, the migrated address is added to the portfolio while the old one is removed. If a transaction is rejected, users can retry or cancel the process.
• •
  Implemented address verification through message signing, allowing users to confirm ownership of a target address before migration. This supports both successful and failed verifications, with the ability to send messages to the Ledger for signing and validate them on Vault’s side.
• •
  Added functionality to display migratable Ledger addresses after device connection, scanning the first five and highlighting those with funds. Users can scan more if needed and select which addresses to migrate, including performing single-address migrations that guide the following flow steps.
• •
  Adjusted form button styling to correctly use dim mode colors, replacing the incorrect dark mode appearance for improved visual consistency.

In the coming week, the team will finalize the Ledger migration flow while continuing with general improvements and design updates.

Mainsail Weekly Report

This week's Mainsail development focused on database improvements, optimizations, and updates to logging and P2P functionality. Accomplishments include:

• •
  Reconstructed EVM storage to store objects instead of serialized data, with compression applied. This change improves restore times and reduces database size by approximately 40%.
• •
  Preserved error context in EVM-related errors for clearer debugging and tracing.
• •
  Updated inversify to the latest version and replaced constructor usage with the @postConstruct decorator in the InstanceManager for improved lifecycle management.
• •
  Reformatted logs so that all entries align consistently in-line regardless of log level, improving readability.
• •
  Implemented a new WorkerLogger class and removed worker logic from logger-pino, separating concerns for cleaner architecture.
• •
  Added support for log contexts such as p2p, evm, consensus, and tx-pool, displaying context information in log output. Initial color differentiation for each context was introduced to make logs easier to scan.
• •
  Removed the critical and emergency log levels. The current log levels are now: alert, debug, error, info, notice, and warn.
• •
  Removed the isValidLevel method from the logger interface to simplify and declutter the codebase.
• •
  Implemented P2P statistics logging, recording average, median, minimum, and maximum latencies each round, along with totals for peers, banned peers, and peers pinged in the last round.

Next week, the team will continue working on P2P improvements and optimizations, as well as expanding unit test coverage for a more robust codebase.

Feedback & Feature Requests

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

Quick access links to GitHub issues pages:

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

Stay Updated

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