7th Mar 2025
6 min read

ARK Development Report - March 7, 2025

*Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, the ARK Scan team advanced the Mainsail EVM with further refinements through additional testing, while ARK Docs and SDK made significant headway by updating the documentation site, adding fresh content, and refining the SDKs. The ARK Vault team focused on improving the user interface, progressing Mainsail EVM support, and resolving reported issues, ensuring a smoother experience with enhanced UI elements and bug fixes. For Mainsail EVM, we added historical data support for methods with default parameters for MetaMask integration and other improvements.

Development Activity Summary (Feb 28 – March 7, 2025)

Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from February 21, 2025, to February 28, 2025.

Project Commits Authors
ARK Connect 0 0
ARK Scan 1 1
ARK SDKs & Docs 43 4
ARK Vault 24 4
Mainsail 18 2

During this period, the team maintained strong productivity and engagement, delivering 86 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, our team made further progress on the Mainsail EVM, refining the implementation through additional testing. A key fix involved correcting fee displays in the UI, which were previously inflated due to a change from gwei to wei. We’ve now adjusted for this, ensuring fees are shown accurately across the interface.

Looking ahead, we’ll continue testing and refining the implementation, addressing any identified issues or bugs, and advancing additional tasks to support ongoing Mainsail EVM updates.

ARK SDKs and Documentation Weekly Report

This week, we made further progress on the new documentation site, adding fresh content, updating existing documentation, and refining SDKs. The tasks completed include:

  • Documentation Site:
    • Updated Python and PHP devnet to testnet references.
    • Updated Python number handling to int.
    • Added documentation for support of the multipayment transactions for Python package.
    • Added docs for Python’s support of the username transactions.
  • Platform SDK:
    • Added additional options in wallet identity sync to enable callers to pass custom HTTP request parameters, such as TTL, to ARK Vault’s custom HTTP client, optimizing caching at the request level and reducing the need for complex state management in React.
    • Fixed an issue where importing addresses on Mainsail triggered unintended requests to the ARK mainnet, ensuring that only existing networks are queried.
    • Refactored address import to prevent unnecessary forced network sync, allowing callers to invoke wallet.synchronizer() only when needed.
    • Added a way to get on-chain usernames for addresses using evmCall.
    • Removed news package as its no longer needed for Mainsail.
    • Made changes for correct type definitions for IProfile#sync.
  • TypeScript Crypto Package:
    • Set up the initial TypeScript package.
    • Added support for Mainsail networks.
    • Added unit conversion functionality.
    • Added support for address generation and Ether dependencies.
    • Added public key class implementation.
    • Added private key class implementation and signCompact method based on the Python implementation.
    • Added WIF class implementation.
    • Added transaction utilities implementation.
  • Python Crypto Package:
    • Refactored Transaction Type & Builder constructors to require the data argument, enabled declaring empty builder instances, and removed the payload argument from Types.
  • PHP Crypto Package:
    • Made transaction parameters required and non-optional.

Next week, our focus remains on the documentation site improvements and updating packages to align with the changes in Mainsail EVM.

ARK Vault Weekly Report

This week, we made significant progress in improving the overall user interface, progressing with Mainsail EVM support, and addressing reported issues. Our efforts focused on improving UI elements, refining EVM integration, and resolving bugs to ensure a smoother experience. The work completed includes:

  • Added known wallets handling to the alias hook, prioritizing ARK-defined lists to highlight real exchanges and mark potential fraudulent addresses, enhancing user protection.
  • Fixed an issue in the send form where the address could appear twice due to field disabling, ensuring proper input handling.
  • Updated the Side Panel to use known names or usernames where applicable, ensuring consistency in address naming.
  • Fixed the “Copy Transaction” tooltip, replacing it with the correct “Copy Address” tooltip.
  • Updated PSDK dependency to the latest version released.
  • Fixed a scrolling issue on the create profile page for mobile, ensuring users can access the ToS checkbox and enable the “Create” button.
  • Added an onboarding tooltip when multiple addresses are added to a vault profile, guiding users to the “Multiple Addresses” section for consistency with the address side panel tooltip.
  • Fixed the “Import” and “Create” buttons on the mobile “Welcome” page, ensuring they function correctly and prevent users from getting stuck.
  • Implemented recipient alias caching to reduce network workload by storing query results for recipient aliases.
  • Fixed the logo display on the select profile page and corrected the logo UI on the welcome page.
  • Refactored address alias logic to improve address alias handling, with a toggle allowing users to prioritize on-chain usernames or local address names for better customization.
  • Refactored to remove the @ardenthq/sdk-ledger dependency, moving it into the vault instead.
  • Increased background blur when the side panel is open to align with the design.
  • Refactored toast message positioning to the bottom left for improved UI consistency.
  • Temporarily disabled Ledger dependencies to address current issues.
  • Refactored address import to sync profiles only on the active network, preventing unnecessary requests to the ARK mainnet when it’s not an active option in the wallet.
  • Updated validator resignation tests to work with the Mainsail network, ensuring proper functionality.
  • Fixed an issue in the transfer form where selecting “Advanced Fees” caused automatic loss of focus on the “Gas Price” or “Gas Limit” fields when entering custom gas settings.
  • Fixed address alias usage by setting the local name as the initial alias once fetched, resolving synchronization errors, and ensuring the alias displays in the transaction details modal as expected.
  • Updated validator registration tests to work with the Mainsail network, ensuring proper functionality.
  • Refactored to restore the Ledger service, resolving browser issues caused by Buffer references and preparing for easier adjustments by handling Ledger interactions directly within Vault.
  • Performed initial tests with the Ethereum Ledger app to interact with Mainsail through Ledger hardware.

Next week, we’ll focus on completing the remaining tasks for Mainsail support and compatibility, tackling reported issues, refining the user interface, and beginning more extensive internal testing to ensure everything runs smoothly.

Mainsail Weekly Report

This week, we focused on enhancing MetaMask support and making other improvements. The work completed includes:

  • Added historical data support for full MetaMask compatibility.
  • Moved kernel utilities from the kernel package to the utils package and removed related re-exports to improve package decoupling.
  • Improved the transaction sender script.
  • Upgraded EVM to use Rust Edition 2024.

Next week, we will work on adding support for a genesis height offset to ensure a continuous chain after import. Additionally, we will rename fields to align with Ethereum’s naming conventions.

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.