ARK Development Report - July 4, 2025

Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, we rolled out several updates to the ARK Connect extension, while the ARK Scan team introduced a new feature to display legacy ARK addresses. The PHP Crypto package dependencies were updated to resolve Composer warnings and improve package management stability. Meanwhile, the ARK Vault team finalized the Dim Theme and added an option for it in the settings page. The Mainsail team addressed multiple API-related issues and released a new version for the internal testnet based on the V3 devnet snapshot.

#Development Activity Summary (June 27 – July 4, 2025)

Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from June 27, 2025, to July 4, 2025.

During this period, the team maintained strong productivity and engagement, delivering 147 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 Connect Weekly Report

This week, we made several updates to the extension, including:

• Enhanced the fee input components to support both gas price and gas limit, along with other improvements to optimize fee handling.
• Refactored the transfer transaction sending logic, introducing minor adjustments to improve consistency and maintainability.
• Aligned with recent PSDK changes to display the locked fee during validator registration, and fixed dark mode styling issues for the radio button component.

Next week, we’ll continue refining the extension and make additional updates to the Demo site as needed.

#ARK Scan Weekly Report

This week, we focused on adding a new feature for displaying legacy ARK addresses, along with several other improvements. Work completed includes:

• Added support for displaying a wallet’s legacy ARK base58 address, linking to a legacy version of the explorer for viewing historical transactions. The address is shown similarly to the public key option and uses the existing explorer URL format from the network configuration.
• Refactored vote transaction handling to improve performance by fetching all voted-for wallets in a single query per page, instead of individually per transaction. This significantly improves transaction table load times.
• Improved missed blocks pagination by adding prefetching logic for next and previous pages. This enhances perceived speed by loading adjacent pages in the background, making navigation feel more responsive.
• Updated the annual statistics calculation to include multipayment amounts correctly using MultipaymentTotalAmountScope. Also fixed an issue where multipayment values were being double-counted in both total and recipient amounts within AveragesAggregate.
• Removed usage of the deprecated blocks.amount column after its removal in the latest Mainsail release. Adjusted all affected areas, including the blocks page, validator blocks page, and related statistics, to ensure compatibility and prevent errors.
• Resolved Composer warnings by updating dependencies and configuration to eliminate install-time issues and deprecation notices. Also addressed security vulnerability warnings by updating the impacted foundation dependency.

Next week, we’ll continue working on optimizations and address any reported issues from internal testing.

#ARK SDKs & Docs Weekly Report

This week, we updated the PHP Crypto package dependencies to resolve Composer warnings and enhance the stability of package management. Additionally, we merged the develop branch into master to consolidate the latest changes and released version 1.9.0 for use in other projects.

Next week, we’ll address additional issues and improvements to the SDKs and ensure the documentation site is updated to reflect those changes.

#ARK Vault Weekly Report

This week, we finalized the Dim Theme and added an option for it on the settings page. We also focused on fixes and general UI improvements. Work completed includes:

• Refactored the validator registration flow to hide the registration option if the address is already registered as a validator. Improved UI handling for partial validators (core delegates without BLS keys), displaying the resignation option when appropriate.
• Added support for a Dim Theme alongside Light and Dark modes. This included updating settings to allow theme selection, handling dim-specific images, and defining a dim color palette. Implementation followed the approach used in ARK Scan, using TailwindCSS for consistent styling across Vault.
• Fixed a bug where importing profiles with core delegates lacking BLS keys caused a black screen in Mainsail. The import process now handles these cases correctly, including scenarios with second signatures and encryption.
• Added Dim Theme support to the PWA banner, Ledger import and scan steps, disabled portfolio header button, and create profile component, ensuring consistent styling across the UI.
• Refactored the votes page to show validator usernames when available, falling back to addresses when usernames are missing for better clarity.
• Fixed a responsiveness issue in the transaction table where columns would overflow the container on screen widths between 1024px and 1278px.
• Refactored QR code handling to ignore coin references, resolving compatibility issues with Mainsail on the Receive page.
• Fixed a dark mode issue where the Welcome page background briefly flashed in light mode before switching, ensuring correct rendering from the start.
• Implemented support for validators registered before the locked fee was introduced by using the new validatorFee attribute. Updated transaction details, tables, and related views to reflect this correctly.
• Updated the transaction filter design to match the latest UI specifications for improved visual consistency.
• Adjusted sidepanel background styling in dim mode to align with the design system.
• Fixed Dim Theme configuration in base CSS by defining the theme as a variant in the Tailwind config instead of using a plugin. This enables proper use of dim: and dim-hover: prefixes. Also updated select dropdown styles for full dim mode support.
• Fixed alignment in the validators table so that entries match their respective column headers.
• Adjusted height and width of the sign message buttons in the desktop sidepanel view for better layout consistency.
• Refactored the transactions page to support the Dim Theme by updating components like dropdown icon helpers, input counters, wallet vote inputs, message transaction components, input fee components, and various form/review step components.
• Fixed dark mode colors for the radio button in the select address component to ensure proper visibility and consistent styling.
• Increased test coverage for the app/lib directory and removed outdated version notification code from the Electron implementation.

Next week, we’ll focus on resolving any issues related to the newly introduced Dim Theme, along with further improvements and Mainsail EVM compatibility work.

#Mainsail Weekly Report

This week, we addressed several API-related issues and released a new version for the internal testnet based on the V3 devnet snapshot. Work completed includes:

• Updated the publish workflow to use the latest Rust toolchain, resolving issues caused by an incompatible Rust version.
• Removed the timestamp field from the transaction interface. The API response still includes a timestamp, which matches the block’s timestamp.
• Released version 0.0.1-evm.21 for the internal testnet.

Next week, we’ll focus on removing unused API endpoints and resolving issues in the api-development branch.

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