Welcome to this week’s Weekly Development Report, highlighting continued progress in simplifying architecture, improving developer experience, and strengthening core protocol behavior. The ARK Connect team focused on reducing legacy PSDK complexity, streamlining pricing integration, and simplifying transaction and network layers to better align with a Mainsail-only design. The ARK SDKs and Documentation team improved accessibility by consolidating ARK Connect SDK documentation into the central docs platform, making it easier for developers to find and use. The ARK Vault team enhanced Ledger workflows, introduced retry mechanisms for smoother migrations, and delivered multiple UI and usability improvements across the application. Meanwhile, the Mainsail team strengthened consensus integrity, simplified legacy transaction handling, and improved configuration flexibility, laying a more robust foundation for network operations and future development.
Development Activity Summary (July 17 – July 24, 2026)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from July 17, 2026, to July 24, 2026.
| Project | Commits | Authors |
|---|---|---|
| ARK Connect | 11 | 1 |
| ARK Scan | 0 | 0 |
| ARK SDKs & Docs | 2 | 1 |
| ARK Vault | 45 | 3 |
| Mainsail | 44 | 2 |
In total, 102 commits were merged across all projects this week. As always, commit counts fluctuate with sprint focus and task complexity.
ARK Connect Weekly Report
This week we focused on simplifying the architecture, removing legacy PSDK abstractions, and improving pricing integration across both the extension and demo application.
In the ARK Connect Extension, we removed CryptoCompare as a pricing provider due to new API key requirements and replaced it with CoinGecko’s free API. This simplifies external dependencies and ensures continued access to pricing data without additional configuration. We also fixed an issue where reliance on CryptoCompare could cause the extension to hang under certain conditions.
We continued reducing complexity inherited from the PSDK by collapsing the double transaction DTO layer into a single viewmodel. Previously, transaction data passed through multiple layers that largely duplicated functionality. This refactor removes unnecessary indirection, reduces code size, and makes transaction handling and display logic easier to follow.
We also began simplifying the network layer by moving away from the multi-coin manifest abstraction toward a Mainsail-only configuration. Since the extension only supports Mainsail (and compatible EVM chains), much of the generic abstraction was unused. This change lays the groundwork for a leaner and more maintainable network configuration.
Further cleanup work included reviewing the profile export/import pipeline, identifying parts that are no longer relevant to the extension (such as password-based exports), and preparing them for removal or simplification. We also evaluated the validator syncer, which currently includes both parallel and serial implementations, with the goal of removing unused strategies once confirmed.
In the ARK Connect Demo App, we updated pricing integration to use the new ARK pricing service instead of CoinGecko. This aligns the demo with the broader ecosystem and provides a more consistent source of market data.
Next week we will continue improving Mainsail integration, focusing on completing the network layer simplification and removing remaining legacy abstractions. We’ll also address any issues uncovered during testing, refine transaction and profile handling, and further align both the extension and demo app with shared services such as pricing and SDK usage.
ARK SDKs & Documentation Site Weekly Report
This week we focused on improving documentation accessibility by adding ARK Connect SDK pages to the documentation site. The existing SDK documentation was migrated from the repository into the central docs platform, ensuring everything is consolidated in one place and easier to navigate. This also allows the SDK to link directly to a dedicated, up-to-date documentation resource.
Next week we will continue refining the documentation site, improving structure and clarity, and expanding coverage across SDKs and related tooling.
ARK Vault Weekly Report
This week focused on improving Ledger-related workflows, refining UI components, and addressing usability issues across the application.
We started by cleaning up Ledger model restrictions, removing outdated limitations and unused components. This simplifies the Ledger integration layer and makes it easier to maintain and extend going forward.
On the UI side, we fixed several issues in the transaction history export modal, where dropdowns for Date Range and Delimiter were not displaying correctly. We also improved the calendar layout by shortening weekday labels to better fit within the available space.
We introduced a new feature in the migration flow by adding a retry mechanism for Ledger approvals. If a transaction fails to appear on the Ledger device, users are no longer forced to restart the entire migration process. Instead, they can retry sending the transaction directly from the approval screen, significantly improving recovery and overall user experience.
Ledger support was further extended by adding signing capabilities for resignation transaction types, including username and validator resignations. This ensures broader transaction coverage when using Ledger devices.
We also implemented the new calendar design, aligning it with updated UI standards and improving consistency across the application. Additionally, we fixed a layout issue at 768px where transaction amounts and addresses could overflow in the side panel.
Next week we will continue improving the Ledger migration experience, focusing on stability, edge cases, and overall UX polish. We’ll address any issues identified during internal testing, refine error handling and recovery flows, and ensure Ledger interactions are as seamless as possible. Additional work will include minor UI/UX improvements and continued cleanup of legacy components to keep the codebase lean and maintainable.
Mainsail Weekly Report
This week focused on strengthening consensus integrity, simplifying legacy components, and improving configuration flexibility.
We updated the legacy snapshot import process to stop carrying over BLS keys. Imported validators are now registered as dormant and must submit their own Proof-of-Possession (PoP) verified BLS keys via updateValidator to become active, while genesis validators form the initial active set.
In the consensus contract, several important fixes and improvements were made. We now reject scenarios with insufficient active validators instead of padding round slots, preventing duplicate slots that could stall rounds or allow vote replay. We also repaired voter-list head removal in _unvote, removed validator shuffling, and replaced clamp logic with a simpler min approach. Additionally, we introduced an explicit maximum for roundValidators in the crypto-config milestone schema.
We enhanced tooling by adding support for a secrets file in the configuration generator, allowing explicit definition of genesis and validator mnemonics when generating network configurations.
Finally, we removed the obsolete @mainsail/transactions package. Its TransactionHandler abstraction was no longer needed, and the processor, forger, and transaction pool now interact directly with the EVM and transaction verifier, simplifying the transaction pipeline.
Next week we will focus on expanding unit test coverage, continuing performance and reliability improvements, and refining consensus and validator flows. Additional work will include further cleanup of legacy code paths and improving developer tooling and configuration workflows.
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 issue pages:
Follow Us on X
Follow us on X and keep an eye on the blog to stay up to date with everything we ship. We publish a development report every week so you can follow along as the ecosystem grows.
