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 Mainsail compatibility issues. At the same time, progress continued on the TypeScript client and the introduction of Vault Crypto—a lighter, purpose-built SDK tailored for ARK Vault. The ARK Vault team pushed forward with Mainsail EVM integration and began replacing the existing PSDK package with the newly introduced Vault Crypto. Meanwhile, the Mainsail team concentrated on general improvements and bug fixes.
Development Activity Summary (April 25 – May 2, 2025)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from April 25, 2025, to May 2, 2025.
During this period, the team maintained strong productivity and engagement, delivering 88 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 on resolving reported Mainsail compatibility issues. The work completed includes:
Corrected missed or incorrect block height values to ensure accurate chronological ordering and consistent block data across multiple days.
Updated transaction fee handling to support new decimal formats, addressing issues where total and average fees used an incorrect number of decimals.
Added support for incoming multipayments, ensuring they are properly recognized and displayed alongside other incoming transactions for each address.
Adjusted the application to work with the breaking changes in database columns and API responses for the newly released Mainsail version.
Next week, our focus will shift to addressing any additional compatibility issues or bugs reported by the team.
ARK SDKs and Docs Weekly Report
This week, we made progress on the TypeScript client and introduced a new SDK - Vault Crypto. As we began integrating the Platform SDK (PSDK) into ARK Vault, we ran into compatibility issues with some of the cryptographic libraries when building with Vite, the tool used by ARK Vault. To address this, we developed Vault Crypto as a standalone package to isolate and manage these dependencies. This allows us to build these cryptographic components through Webpack, ensuring they work in a browser environment. Work done this week includes:
TypeScript Client Package:
Updated ethCall to accept a single PayloadData object instead of an array. This change resolves API issues caused by nested parameters.
Added contracts endpoint to the API, enabling contract-related requests directly from the client.
Vault Crypto Package:
Implemented cryptographic methods** using modern libraries and testing tools:
Replaced micro-bip39 with @scure/bip39.
Switched from crypto-js to @noble/hashes/pbkdf2 for PBKDF2 operations.
All adapted tests now pass using Jest.
Exported classes and types, fully replacing @ardenthq/sdk-cryptography with arkvault-crypto. Verified functionality remains consistent, especially around profile encryption.
Removed the @ardenthq/sdk-cryptography dependency entirely.
Added a Webpack config to ensure browser-compatible builds that run successfully in a web environment.
Implemented BLS key verification..
Most updates to the Platform, Python, PHP, and TypeScript SDKs are now in place. Next week, we’ll focus on resolving reported issues and continuing development on arkvault-crypto to ensure full integration within ARK Vault. Additionally, we’ll be expanding content on the documentation site.
ARK Vault Weekly Report
This week, we continued working on the Mainsail EVM integration and began integrating the new, leaner Vault Crypto package to replace the existing PSDK package. Work completed includes:
Moved away from external PSDK dependencies by integrating them directly into ARK Vault, streamlining the solution for Mainsail and EVM networks, and removing unnecessary multi-coin complexity.
Replaced all instances of @ardenthq/sdk-cryptography with the arkvault-crypto package.
Set the single address view as the default display mode for the addresses side panel.
Refactored the DateTime class from lib/intl to integrate the timezone plugin from dayjs, enabling the display of transaction timestamps in the user’s local timezone.
Updated hosts in networks/mainsail.devnet and networks/mainsail.mainnet to adjust for transaction sending.
Fixed the “Sign Message” button hover state by moving the class names applied to the div wrapper into the button’s class name container within the Clipboard button variant.
Fixed transaction fetching parameters for both the dashboard page and transaction export, ensuring accurate data retrieval.
Restored the validation for minimum and maximum gas limits and gas prices.
Fixed the issue with multipayment transactions failing due to insufficient gas limits by making sure it increases with every added recipient.
Made adjustments to Vault for compatibility with the next Mainsail release, including updates to transaction API attributes to align with the new version.
Refactored the custom servers table and added a custom server form to support three endpoints, enhancing the server management interface.
Integrated typescript-client by replacing the custom Request implementation across all Mainsail coin API calls, including fees, transactions, and EVM calls.
Moved maximum length validation for usernames to the custom validation rules section, ensuring that usernames longer than 20 characters are correctly flagged and not treated as false positives.
Implemented state reset for side panel consumers after the component is unmounted, ensuring that the state is cleared following the close transition.
Renamed all instances of “delegate(s)” to “validator(s)” across the lib packages and React components. This includes renaming delegate.service to validator.service, updating related types, methods, interfaces, constants, API endpoints (e.g., /delegates to /validators), and refactoring component names and logic to align with the new terminology, along with minor type adjustments to prevent TypeScript errors.
Next week we’ll keep working on making Vault Crypto package integration changes and updates as well as other Mainsail EVM related improvements as well as UI updates.
Mainsail Weekly Report
This week, we focused on general improvements and bug fixes. Highlights include:
Enabled the EVM API by default.
Configured snapshot writing to the config directory during new network generation.
Updated Docker configuration to support the latest release.
Fixed CI workflows for external contributors.
Added end-to-end tests for transactions and the Public API.
Next week, we’ll be working on V3 BLS key registration in ARK Core and improving test coverage.
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 - https://github.com/ArkEcosystem/mainsail/issues
ARK Connect (Extension) - https://github.com/ArdentHQ/arkconnect-extension/issues
ARK Connect (Demo) - https://github.com/ArdentHQ/arkconnect-demo/issues
ARK Scan - https://github.com/ArdentHQ/arkscan/issues
ARK Vault - https://github.com/ArdentHQ/arkvault/issues
Follow on Twitter (X)
Follow us on X (https://x.com/ArkEcosystem) 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.