ARK Development Report - February 13, 2026

Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, the ARK Scan team focused on performance improvements across the application, continued expanding ERC-20 token support, and resolved several reported issues. On the SDK side, token transaction handling in the TypeScript Crypto package was improved through the introduction of a clearer and more reliable transaction type identifier for token-related transactions. The ARK Vault team also continued expanding ERC-20 token support, addressed reported token-related issues, and delivered several general improvements. Meanwhile, the Mainsail team increased overall test coverage by adding new unit tests and strengthening E2E coverage.

#Development Activity Summary (February 06 – February 13, 2026)

Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from February 06, 2026, to February 13, 2026.

During this period, the team maintained strong productivity and engagement, delivering 168 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 focused on performance improvements across the app, continued expanding ERC-20 token support, and resolved several issues. Work included:

• Improved overall performance by removing N+1 queries and relying on the state table to retrieve the latest block height.
• Corrected token transfer display to show the proper ERC20 token symbol instead of the native token.
• Added support for displaying ERC20 approve transaction details in the Explorer, including the approved amount (or “unlimited” if max value), the approved token, and the contract receiving the approval.
• Added a token transfer table to the Address Details page, displaying all ERC20 token transfers related to the selected address.
• Implemented a token transfer list table that displays ERC20 Transfer events similarly to the transactions table, with each transfer event shown as its own row even when multiple events belong to the same transaction.
• Resolved request buildup on the Compatible Wallets page by removing unintended repeated polling, preventing multiple requests from triggering every few seconds during navigation.
• Resolved a 404 affecting pages that load transactions by handling incorrectly indexed token transfer transactions more safely, ensuring transactions with an invalid recipient (used instead of the token contract address) no longer break queries or page loading.
• Updated browser tests for the Transaction Detail page and adjusted tests for the Transaction List to ensure correct behavior.
• Fixed transaction export functionality so transactions can now be successfully exported from the Explorer.
• Improved transaction recipient handling:
  • Updated the “To” field under Addressing in transaction details to show the contract address instead of the recipient username, ensuring the URL matches the actual wallet.
  • Fixed Explorer UI breakage caused by multipayment transactions, restoring proper page rendering.

Next week, we will continue expanding ERC-20 token support and deliver additional performance improvements across the app.

#ARK SDKs & Docs Weekly Report

This week, we improved token transaction handling in the TypeScript Crypto package by implementing a clearer and more reliable transaction type identifier for token-related transactions.

As part of this work, we also simplified the logic responsible for extracting the identifier. The previous implementation was difficult to read and debug, so this refactor makes the codebase easier to maintain while keeping token transaction detection consistent.

#ARK Vault Weekly Report

This week, we continued expanding ERC-20 token support, addressed reported token-related issues, and delivered several general improvements. Work included:

• Improved token selection persistence in the send transfer form: clicking the Send button now prefills the selected token, and navigating between review and form steps no longer clears the chosen token.
• Resolved token transfer issues by ensuring the correct number of decimal places is used when sending tokens, preventing accidental sending in wei/gwei, and fixed cases where the token transaction form incorrectly reported “insufficient balance,” likely due to delayed token data retrieval.
• Reduced redundant transaction checks by passing the confirmed transaction from the parent component to the side panel, removing extra useConfirmedTransaction calls in TransactionSuccessful and TransactionDetails to streamline the sending flow and avoid unnecessary requests.
• Updated a meta tag to remove a deprecation warning and ensure proper HTML standards compliance.
• Corrected token table row checkbox positioning in Manage mode to restore proper alignment and usability.
• Improved validator name display in the portfolio to avoid unnecessary truncation on large screens, ensuring full names are shown when there is enough space.
• Fixed the portfolio header bottom section to properly handle all states, including combinations of addresses with or without tokens and votes, ensuring consistent display across scenarios.
• Resolved an undefined ref error on the profile page, preventing the console error from appearing in DevTools when navigating to token-support features.
• Fixed the Tokens page in “Multiple Address” view so tokens are consistently listed, ensuring the table works correctly when multiple addresses are selected.
• Refactored token display to better handle long values:
  • Token name is truncated to 20 characters and symbol to 5 characters with an … suffix.
  • Token balances are displayed in a compact format with letter abbreviations (K, M, T) and 2 decimals.
  • Changes apply to the token overview table and token selection dropdown, while the token details side panel continues to show full values.

Next week, we’ll continue addressing any ERC-20 token feature issues as well as any other reported items.

#Mainsail Weekly Report

This week, our team focused on increasing test coverage by adding unit tests and strengthening E2E coverage, while also delivering a few improvements across crypto-related packages. Work included:

• Increased unit test coverage for crypto message functionality.
• Improved E2E tests by adding real ERC20 contract transactions.
• Fixed API sync behavior and updated restore/sync flows to ensure data is consistent.
• Refactored the crypto-block package by removing the data and header properties and moving them to the block root.
• Improved additional interfaces related to the crypto block and removed duplicated code.

Next week, we’ll continue increasing coverage by adding more unit tests, database sync tests, and further improvements to the crypto packages.

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