ARK Development Report - January 30, 2026

Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, the ARK Scan team continued progressing with additional Inertia migrations and fixes, while further polishing the codebase and resolving several issues across the application. The ARK Vault team kept advancing the Token feature integration, with a focus on performance improvements and addressing additional UI-related issues. Meanwhile, the Mainsail team concentrated on enhancing API support for the ERC-20 Token feature, expanding unit test coverage, and making multiple code quality and readability improvements across the platform.

#Development Activity Summary (January 23 – January 30, 2026)

Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from January 23, 2026, to January 30, 2026.

During this period, the team maintained strong productivity and engagement, delivering 126 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 continued with additional Inertia migrations and fixes, while also polishing the codebase and resolving several other issues across the application. Work completed includes:

• Eliminated unused authentication templates and related functionality (templates, middleware, service providers, config entries, and an API route), as the Explorer does not require authentication.
• Switched JSON request handling to Axios instead of the previous fetch implementation, fixing compatible wallets form submission issues and preventing erroneous 429 responses.
• Improved Inertia navigation behavior by preserving scroll position when changing theme or price ticker, so scrolling now only occurs on page changes or pagination.
• Resolved an error on the Validators → Missed Blocks tab that was breaking the page, ensuring the tab loads correctly without console issues.
• Extended loading state placeholders to table headers (including the “showing results” area) and the wallet voters table, and updated the blocks page to display “Showing 0 results” while loading to prevent layout shifts.
• Stabilized the Transactions table on the Block Detail page by using pageHandlerProvider, preventing errors during transaction record loading.
• Added a clarification note on the Statistics page indicating that displayed data only includes records after the snapshot.
• Restored the active-page underline in the Inertia navbar for the “Home” entry, reintroducing the correct visual indicator.
• Updated the UI to disable fiat conversions in areas where exchange rates are unavailable, ensuring values like Total Reward on blocks no longer show incorrect fiat data.
• Corrected filter handling in Inertia tables, fixing the “Others” filter so selecting and deselecting options now updates rows reliably without inconsistent behavior.
• Standardized table header heights (including those with “Showing x results”) so pages like Wallet → Voters and Validators → Missed Blocks have consistent sizing regardless of buttons.
• Migrated the /exchanges page to Inertia, enabling SPA-like navigation and consistent behavior with other Inertia-based pages.
• Refactored polling and broadcasting logic so pages using Reverb rely on events instead of polling, while non-Reverb pages continue polling; missing event handling was also added to the new Blocks page for consistent real-time updates.
• Restored CTA arrows on the “Manage Your ARK” section of the Inertia home page to match the intended design.
• Smoothed theme switch animations to improve transitions between Light and Dark modes, fixing visual glitches during rapid updates in the Validator Monitor.

Next week, we’ll continue addressing remaining Inertia migration tasks, apply related fixes, and resolve any additional reported issues.

#ARK Vault Weekly Report

This week, we continued integrating the Token feature, focusing on performance improvements and resolving additional issues across the UI. Work completed includes:

• Reduced redundant token sync requests by refactoring the sync logic to store fetched tokens in the profile, enabling immediate reuse across the UI and improving performance when opening transfer panels or rendering token selectors.
• Introduced a token transfers table that displays ERC20 Transfer events via the /tokens/transfers endpoint, supporting multiple events per transaction, identifying incoming vs. outgoing transfers, and falling back to unknown function signatures when needed—mirroring regular transaction behavior.
• Adjusted validator banner spacing to add proper padding so it no longer touches the “Sender” section, resulting in a cleaner layout.
• Updated the “Send Tokens” action on the token details page to open the token transfer side panel, allowing transfers to be initiated directly from the overview modal.
• Corrected token transfer labeling on the portfolio page by displaying these entries as “Transfer” instead of “Contract Deployment” in both the transactions table and overview modals.
• Temporarily disabled the multi-payment toggle in the token transfer flow, preventing confusion until the feature is supported.
• Removed the dotted separator below the balance in the portfolio page header to better match the updated design.
• Fixed the validator transaction side panel to support changing the selected address, ensuring consistent behavior across all transaction types.
• Improved the token transfers table by displaying the token symbol in the Amount column, storing token metadata in transaction classes, and updating unit tests accordingly.
• Cleaned up deprecated navigation-blocking components on Settings pages while preserving warnings for unsaved changes when navigating away.

Next week, we’ll continue working on the Token feature, implement the Atomic Wallet import functionality, and address any newly reported issues.

#Mainsail Weekly Report

This week, we focused on API improvements for the ERC-20 Token feature, expanded unit test coverage, and made several code quality and readability enhancements. Work completed includes:

• Introduced a Container inside the Application instead of passing it through constructors, improving overall code clarity and structure.
• Consolidated shared container logic by extracting common methods from Cli.Application and Kernel.Application into Container.Application, reducing duplication and centralizing container-related responsibilities.
• Simplified the ServiceProvider by making it a non-abstract class and removing unused features such as aliases and maintenance mode.
• Enhanced token lookup behavior in the Public API so lookups are performed even when the target wallet does not exist.
• Extended the Public API to support querying tokens by name, improving discoverability and flexibility.
• Added unit tests for index.ts files across all packages to ensure consistent coverage of public exports.
• Increased unit test coverage across several core packages, including:
  • bootstrap
  • consensus-storage
  • constants
  • state
  • crypto-wif

Next week, we’ll continue working on ERC-20 improvements and further expand unit test coverage to strengthen overall code quality.

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