13th Jun 2025
5 min read

ARK Development Report - June 13, 2025

Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, we continued making progress on the MetaMask integration for the ARK Connect demo website. The development also advanced on the PHP Crypto package for Mainsail, with a focus on expanding test suite coverage. The ARK Vault team introduced a new Dim Theme and increased test coverage across the application. Meanwhile, the Mainsail team has been working diligently to prepare for the upcoming internal Devnet launch, including Snapshot V3 preparations, new API additions, and other foundational improvements.

Development Activity Summary (June 6 – June 13, 2025)

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

Project Commits Authors
ARK Connect 25 1
ARK Scan 0 0
ARK SDKs & Docs 10 1
ARK Vault 39 3
Mainsail 33 2

During this period, the team maintained strong productivity and engagement, delivering 107 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 have continued working on the MetaMask integration into the ARK Connect Demo website. Work done included:

  • Added the initial scaffolding for MetaMask integration, featuring a MetaMask button with multiple UI states to reflect connection status and user interaction flow.
  • Replaced the ethers package with the viem library to handle MetaMask connection and chain addition. A custom hook was introduced to unify and manage both ARK Connect and MetaMask through a shared interface, streamlining integration and interaction.
  • Implemented data retrieval features, including a disconnect action, UI handling for chain changes, and balance display by fetching data from the Mainsail API.
  • Updated the transactions table to align with the latest Mainsail API changes, ensuring correct data mapping and presentation.
  • Enabled support for sending transfers through MetaMask, allowing users to initiate transactions directly from their MetaMask wallet.

Next week we’ll continue working on the MetaMask integration into the ARK Connect Demo site.

ARK SDKs & Docs Weekly Report

This week we have been working on the PHP Crypto package for Mainsail. Expanded test suite coverage for the PHP Crypto package to support Mainsail, including tests for ABI encoder/decoder, binary buffer, binary hex reader/writer, transaction builder, transaction types, RLP encoder/decoder, and both unsigned and signed binary integer readers/writers. There have also been adjustments made to the PHP, Python and TypeScript SDKs in advance of an incoming Mainsail change that affects Validator Registrations.

Next week, we’ll continue improving the PHP Crypto coverage and implement any additional updates to the SDKs as needed.

ARK Vault Weekly Report

This week we’ve been working on a new feature: Dim Theme, which is already in use on ARK Scan. We also focused on increasing test coverage across the application. Work completed this week included:

  • Implemented a new Dim Theme based on design specifications. This involved initial configuration and theme logic, following the approach used in ARK Scan. The dim theme shares the dark class but introduces a dim-hover modifier in the Tailwind plugin to prevent styling conflicts. Key updates include:
    • Adjusted background and minor danger color styles within the dark palette.
    • Added dim theme support for:
      • Buttons (primary & secondary)
      • Link component
      • Theme Icon (via an optional prop)
      • Navbar, Navbar dropdown, and Navbar button
      • Welcome page and Dashboard onboarding page, including updated icons and images
      • Icons used within the ThemeIcon component
      • Skeleton Loader, Table wrapper, Table row (hover), Label, and Table header (focused on base styles, with page-specific tweaks to follow)
      • Dim-specific images in the Image component
    • Refactored the use-theme hook to support dim mode and persist user preference in profile configurations.
    • Added theme toggle functionality to the config panel.
    • Updated unit tests and snapshots to reflect theme-related changes.
  • Increased test coverage to improve reliability and maintainability. Specifically, tests were added for:
    • src/domains/transaction/validations
    • src/domains/transaction/utils
    • src/utils
    • src/app/libs/helpers
    • src/domains/transaction/hooks
    • src/app/lib/profiles/helpers
    • src/app/lib/mainsail/helpers This work enhances confidence in the app’s stability and supports future development by reducing the likelihood of regressions.

Next week we’ll continue expanding test coverage, addressing any reported issues, and making further improvements to the dim theme and the application overall.

Mainsail Weekly Report

Missed the news? We’ve published our latest update blog post on Mainsail. You can read it here.

We’ve been working hard over the past week to prepare for the internal Devnet launch. Here’s a summary of the key updates:

  • Made API database columns case-insensitive. Users can now query addresses and other fields regardless of casing, while results are still returned in their original format.
  • Removed the legacy SupplyCalculator. During database restore, supply is now calculated as the sum of all account balances, including wallets and contracts.
  • Removed all legacy usage of VendorField, as it is incompatible with Ethereum transaction types.
  • Fixed account lookup logic when accounts are missing from the historical data of recent blocks. If not found in temporary history, the system now falls back to the account database.
  • Refactored the block verifier into separate block verification handlers. All block checks are now centralized in the block processor, rather than being scattered across the codebase.
  • Added support for a validator registration fee in the consensus contract. A fee of 250 ARK is now collected when a new validator registers, and it is refunded upon resignation. Existing validators are unaffected and will not receive a refund upon resignation.

Looking ahead to next week, our focus will shift fully to V3 Devnet Snapshot testing on the internal network. We will also review and implement support for legacy transactions to ensure broader client compatibility.

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:

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.

Share:

Get in Touch!

Whether you want to learn more about ARK Ecosystem, want to apply for developer bounty, become our partner or just want to say Hello, get in touch and we will get back to you.



An Ecosystem of Developers

Join us on our journey to create the future of Web3.