ARK Development Report - February 27, 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 resolving reported UI bugs uncovered during internal testing and wrapping up remaining Inertia migration tasks. On the SDK side, we fixed an issue in the TypeScript Crypto token utilities to ensure greater accuracy when handling large values. The ARK Vault team continued refining the ERC-20 Token feature and addressing feedback from internal testing, while the Mainsail team introduced a new feature, expanded test coverage, and delivered several API improvements as part of ongoing platform improvements.

#Development Activity Summary (February 20 – February 27, 2026)

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

During this period, the team maintained strong productivity and engagement, delivering 141 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 primarily on resolving reported UI bugs from internal testing and completing remaining Inertia migration tasks. Work included:

• Added a “Token Holdings” entry to the Address Details page, with the View link navigating directly to the Tokens tab.
• Compacted token amounts using abbreviated formatting on the overview and token transfers pages to prevent UI overflow, added tooltips for full-value visibility, and ensured approval amounts in Transaction Details are correctly formatted.
• Corrected the Top Accounts page meta title by removing the unintended {{name}} placeholder.
• Removed the unused ForgingStatsViewModel, cleaned up related references, and simplified the forging stats implementation.
• Migrated the Transaction View Model to Inertia, expanded and updated unit tests (including introducing Jest for migrated logic), resolved failing browser tests, and removed unused TransactionViewModel methods to streamline the implementation.
• Eliminated the unused RoundViewModel, cleaned up references, and simplified related round-handling logic.
• Updated the Token Transfers table skeleton to include two placeholders for the “Addressing” column and removed the redundant Symbol column to improve loading state consistency.
• Fixed token transfer amount rendering on the Transaction Detail page to correctly handle extremely large numbers without rounding, ensuring values such as 123,456,789,123,456,789,123,456,789.9876543219876543 display exactly as decoded from the payload.
• Migrated the WalletViewModel to Inertia, removed legacy view model methods, and updated related tests to ensure consistent wallet data rendering.
• Migrated the BlockViewModel to Inertia, updated search result handling, removed legacy logic, and ensured block data displays correctly.
• Enhanced token displays by adding tooltips that show the full token ticker whenever it is truncated, ensuring complete visibility across Scan.

Next week, we’ll continue making general improvements and address any additional issues reported by the internal testing team.

#ARK SDKs & Docs Weekly Report

This week, we addressed an issue in the token utilities to improve accuracy when handling large values in the TypeScript Crypto package.

We fixed a problem where formatUnits did not return a BigNumber, which could lead to inconsistencies when working with very large token amounts. In certain cases, sending large values resulted in a different amount being displayed during the review step.

With this fix, large amounts such as 123456789123456789123456789.9876543219876543, are now handled and displayed consistently, ensuring the value entered matches the value shown before confirmation.

#ARK Vault Weekly Report

This week, we continued refining the ERC-20 Token feature and resolving issues identified by the internal testing team. Work included:

• Further improved validator name truncation in the portfolio so names use available space efficiently across all screen sizes without unnecessary shortening.
• Added identifiers for approve, revoke, and batchTransfer methods to ensure default contract methods from known contracts are properly recognized and displayed in Vault, replacing raw signature hashes with human-readable names where applicable.
• Improved the token sending overview UI to properly wrap very large amounts, ensuring full visibility without breaking the layout.
• Corrected transaction direction detection in the token transfer table by incorporating wallet metadata, preventing outgoing transactions from being incorrectly labeled as “Received.”
• Resolved token symbol overflow in the Transfers table so long symbols are truncated or wrapped appropriately to preserve table layout.
• Addressed floating-point precision issues in the token transfer review step, ensuring amounts are displayed accurately before submission.
• Updated the wallet header “viewing” indicator in the portfolio to correctly reflect selected addresses:
  • After deleting an address in Multi View, the header now shows the remaining single address instead of “Multiple Addresses (1).”
  • When only one address is selected in Multi View, it now displays the individual address as in Single View, removing the misleading “Multiple Addresses (1)” label.
• Added a warning image to the confirmation modal in dim mode to ensure proper styling and visual clarity in dark-themed interfaces.
• Improved Transaction Detail handling for unknown types by removing the default “bytecode” section and displaying only the method hash in the action section, avoiding confusion with contract deployment defaults.
• Refactored Wallet and WalletToken classes to use BigNumber for balances instead of JavaScript numbers, resolving incorrect balance displays in the send form and issues with sending maximum amounts. Updated comparisons and related tests to ensure correct behavior across all transfer scenarios, including Ledger wallets.
• Simplified voting logic by removing unnecessary stake amount handling and cleaning up related unit tests, streamlining the vote flow implementation.

Next week, we’ll continue addressing reported issues from internal testing and implement further refinements and enhancements to the ERC-20 Token feature.

#Mainsail Weekly Report

This week, we introduced a new feature, expanded test coverage, and delivered several API improvements. Work included:

• Added validation to check trailing bytes during block deserialization to ensure payload integrity.
• Implemented functional tests for v3 legacy restore to strengthen backward compatibility coverage.
• Updated api-sync listeners to use a recursive setTimeout loop instead of setInterval, improving control over execution flow and preventing overlapping runs.
• Extended the /transactions API to include transferred tokens in responses.
• Implemented a token whitelist feature.

Next week, we’ll continue writing unit tests, deliver further improvements to the crypto packages, and expand token-related API enhancements, particularly around whitelist and approval functionality.

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