Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. Over the past week, we began adding MetaMask support to the ARK Connect demo website to showcase the Mainsail integration with existing EVM tools. We updated the documentation site for the ethCall function to support passing the request body as a parameter. The ARK Vault team focused on strengthening the test suite, delivering several updates and fixes related to Ledger support and the Side Panel. Meanwhile, on the Mainsail front, efforts continued around refining contracts and preparing for the upcoming Core snapshot.
Development Activity Summary (May 30 – June 6, 2025)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from May 30, 2025, to June 6, 2025.
During this period, the team maintained strong productivity and engagement, delivering 74 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 started adding MetaMask support to the ARK Connect demo website to showcase the Mainsail integration with existing EVM tools. This included:
Adjusting the demo endpoints to make use of the Mainsail APIs.
Adjust the fee input to handle gas price + gas limit to match Mainsail’s fee setup.
Added a MetaMask install and connect button to the welcome page.
Implemented MetaMask connection by prompting the user to add the Mainsail network to MetaMask if it does not exist yet and subsequently connect through it.
Next week, we plan to continue the MetaMask addition by implementing data retrieval and transaction signing.
ARK SDKs and Docs Weekly Report
This week, we made adjustments to the documentation site for the ethCall function to support passing the request body as a parameter. This update improves compatibility with a broader range of EVM call methods, not just eth_call, providing greater flexibility and extensibility in how EVM methods can be used. The documentation has been updated accordingly for both the PHP and Python SDKs to reflect this change.
Next week, we plan to continue refining the documentation site and will update any related packages if necessary.
ARK Vault Weekly Report
This week, we focused on improving the test suite and made several updates and fixes related to Ledger support and the Side Panel. Our work included:
The following unit test suites have been updated: LedgerConnectionStep, LedgerScanStep, LedgerTabs.Cancel, LedgerTabs.Keyboard, and LedgerTabs. These updates have contributed to a significant improvement in the overall test coverage for the portfolio branch, with an increase of over 75 across all criteria. Additionally, the test command has been updated to remove the exclusions for these tests from the workflow, ensuring they are now fully integrated into the automated testing process.
Fixed the tooltip positioning for input warnings by moving the right padding from the icon to a parent container that also wraps the tooltip. This ensures the error tooltip is now correctly aligned and appears centered with the input warning icon for improved UI consistency.
Enabled tests for the app/lib directory by including it in the testing workflow. Adjusted code coverage thresholds based on the existing test cases migrated from PSDK to reflect current coverage accurately.
Moved the message signing functionality to the side panel, supporting both regular and Ledger addresses. This improves UI consistency and streamlines the signing flow within the app.
Updated react, react-dom, and related type packages to version 19.x. Removed unused dependencies (jsdom and react-test-renderer). Made several test adjustments to align with the React 19 API, including updates to user event handling. Deprecated forwardRef usage in favor of using ref as a regular prop in all applicable components, in line with React 19 changes.
Fixed an issue where the Ledger hardware device was not signing transactions due to missing #transport property on the LedgerService. The root cause was multiple instances being created via profile.ledger() or wallet.ledger(), leading to loss of the established transport connection. This update ensures a single shared LedgerService instance is used across services, maintaining the transport state and enabling successful transaction signing.
Fixed an infinite rendering issue on the vote transaction page where the fee component was re-fetching fees every second, causing constant UI refreshes. The re-fetch interval has been reduced to 30 seconds, and serialized data is now used to prevent unnecessary re-renders and infinite loops.
Next week, we plan to continue expanding test coverage and will further develop updates for both the Side Panel and Ledger support, aiming to improve performance, usability, and reliability.
Mainsail Weekly Report
This week, we have been working on contract improvements as well as preparing for the Core snapshot. The work completed included:
Improvements to the consensus contract. We renamed “active validators” to “round validators” and adopted the following naming structure:
Registered validators: All validators that are registered, including those that have resigned.
Round validators: The top N validators with the highest vote balance, participating in the consensus.
Resigned validators: Validators that have resigned from the consensus.
Active validators: Round validators who have not resigned and have a valid BLS public key.
Inactive validators: Validators who are either resigned or lack a valid BLS public key.
Prepared an initial version of the system to collect fees during validator registration.
Added support for exporting from a remote database, along with various other enhancements.
In the upcoming week, we will focus on implementing the validator fee logic in the consensus contract, Core V3 Devnet snapshot testing, and improving overall 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.
