21st Feb 2025
6 min read

ARK Development Report - February 21, 2025

Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, the ARK Scan team continued testing the latest Mainsail EVM implementation, ensuring stability and performance. We also made progress on expanding the documentation on our docs site while refining various client and crypto packages. Meanwhile, the ARK Vault team focused on enhancing the UI to accommodate Mainsail updates, and the Mainsail team worked on improving RPC functionality and test scripts.

Weekly Development Summary

Below is a breakdown of total commits and contributing authors by project, highlighting development activity from February 14th 2025, through February 21st, 2025.

Project Commits Authors
ARK Connect 0 0
ARK Scan 10 2
ARK SDKs & Docs 145 4
ARK Vault 224 4
Mainsail 18 2

During this period, the team maintained strong productivity and engagement, delivering a total of 397 commits across all projects.

It’s important to note that weekly commit counts and project-specific data may vary depending on the focus of internal sprints, evolving objectives, and the complexity of tasks undertaken.

ARK Scan Weekly Report

This week, we continued testing our implementation for Mainsail EVM and worked on several tasks:

  • Updated the ARK Vault promo image to reflect the upcoming changes for Mainsail EVM.
  • Fixed an issue where Multipayment amounts were not included in the historical average calculation.
  • Updated PHP dependencies to the latest versions.

Next week, we’ll continue testing, addressing reported issues, and working on additional tasks.

ARK SDKs & Docs Weekly Report

Work continued on the updated documentation site and various packages. The work completed includes:

  • Platform SDK:
    • Removed Network and Cryptoasset options from Contacts, as Mainsail addresses remain the same across networks. Only the name and address are now required to add or edit a contact.
    • Fixed recipient, payment, and amount data for signed & confirmed transactions. Added a payments() method in the signed transaction class for consistency and refactored decode-function-data.ts to support multiple cases.
    • Removed obsolete settings that are not needed for Mainsail.
    • Removed multisignature-related tests, except for falsy assertions regarding multisignature or second signatures, which remain valid.
    • Converted network fees from wei to gwei and make use chainId for network configuration to match Mainsail’s latest changes.
    • Mainsail test improvements and adjustments to coverage.
  • Documentation Site:
    • Added transaction API endpoints for the PHP client package.
    • Added EVM API endpoints for the PHP client package.
    • Implemented an SDK language switcher for mobile view.
  • Python Crypto & Client Packages:
    • Added unit converters (formatUnits and parseUnits).
    • Implemented support for argumentDecoder.
    • Support for RLP encoding (a method for serializing objects) was added.
    • Added support for username transactions.
  • PHP Crypto & Client Packages:
    • Added transaction API endpoint support to the client package.

Next week, we’ll continue improving all supported packages and expanding the documentation site with additional content.

ARK Vault Weekly Report

Work continued on updating and improving UI elements for the Mainsail EVM changes, along with fixing reported issues. Work done this week included:

  • Removed the network selection step from the send transfer form, as it is now obsolete.
  • Refactored the resigned label and applied the solid variant to adjust its colors.
  • Adjusted padding in the mobile view for the Other settings to match designs.
  • Fixed various issues with transaction sending, including:
    • Using the active network from the navbar for validator registration/resignation.
    • Fixing the disabled continue button for validator resignation when the page loads without wallets.
    • Implementing various UI improvements.
  • Added the text-nowrap class to table headers to prevent header text from breaking into multiple lines.
  • Removed wrapping from the method column in tables.
  • Enabled the 3-dot menu for the multi-address view and ensured only applicable addresses could access transaction forms by disabling ineligible senders in the ‘Select Sender’ modal, with a tooltip indicating unavailable transaction types.
  • Renamed the Value column to Amount and removed the logic behind toggling this title name.
  • Removed duplicate addresses from the receive funds and sender modals.
  • Removed Network from the contact form and related types, refactored the Create and Update contact modals, and updated the contacts table by removing the Cryptoasset column on both mobile and desktop.
  • Properly centered the profile creation page.
  • Moved address creation to the side panel flow for consistency, and adjusted UI and logic to match the new design.
  • Adjusted the formula for address truncation to handle long truncated aliases, short aliases, and cases with no aliases, fixing the alignment issue when an alias was fetched.
  • Adjusted transaction tables to display a single value per address—prioritizing local name, on-chain username, or address—while adding a tooltip for the full address, a copy button, and ensuring consistency for contracts, mobile, and multi-address views.
  • Reworded the tooltip for multiple recipient transactions.
  • Made use of the transaction’s decoded data attribute to show recipients and their amounts in the transaction details for multipayments.
  • Refactored the navbar skeleton to match the new redesign for both mobile and desktop versions.
  • Made the side panel ignore outside clicks on toasts.
  • Updated the Create Address UI to match design changes, including mnemonic list and skeleton updates, tweaks to the Copy & Download section, moving the Use Wallet Encryption step to step 2, and other minor adjustments.
  • Adjusted the transaction’s empty state (when no transactions exist) on the portfolio page.
  • Updated dependencies to the latest release of Platform SDK.

Next week, our goal will remain the same: continue working on UI improvements for Mainsail EVM and fixing any reported issues.

Mainsail Weekly Report

This week, we published a blog post detailing the progress made in recent weeks, along with a video showcasing the MetaMask proof-of-concept (PoC) integration with Mainsail EVM. You can check it out here.

In addition to that, we continued refining our RPC implementation and test scripts. Key improvements include:

  • Enhanced RPC error response handling for calls to non-existent methods.
  • Fixed a GitHub workflow regression introduced by the recent pnpm 10 upgrade.
  • Removed the now-obsolete nonce verifier from the block processor.
  • Updated various transaction test scripts to align with recent changes.

Looking ahead to next week, our focus will be on implementing a logs bloom filter and adding historical data support for methods with default parameters, ensuring full compatibility with MetaMask.

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.