*Welcome to this week’s Weekly Development Report, highlighting continued progress across the ecosystem. The ARK Connect team streamlined market data handling by standardizing on CoinGecko, removing unnecessary provider complexity, and improving the demo application to better reflect real-world SDK usage. The ARK Vault team expanded Ledger support across a wide range of transaction types, refined migration flows, and delivered multiple UX and stability improvements to enhance overall reliability. Meanwhile, the Mainsail team focused on security hardening, improved Ethereum compatibility, and strengthened API and network resilience, while continuing to expand test coverage across critical components.
Development Activity Summary (July 10 – July 17, 2026)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from July 10, 2026, to July 17, 2026.
| Project | Commits | Authors |
|---|---|---|
| ARK Connect | 16 | 2 |
| ARK Scan | 0 | 0 |
| ARK SDKs & Docs | 0 | 0 |
| ARK Vault | 61 | 4 |
| Mainsail | 58 | 2 |
In total, 135 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 market data integration by removing reliance on external services that are no longer viable without authentication.
We removed CryptoCompare as a market data provider following changes that now require an API key for usage. In its place, we standardized on CoinGecko’s free API for retrieving pricing data. This reduces external dependencies, simplifies configuration, and ensures continued access to reliable market data.
This change also helps streamline the codebase by eliminating fallback logic and redundant provider handling, making the pricing layer more maintainable and predictable.
On the ARK Connect Demo app, we fixed the multipayment transaction listing, ensuring transactions are correctly identified and display the number of recipients. Support for handling token amounts was improved by introducing the typescript-crypto dependency, allowing proper formatting of large values (e.g., 1e18). For very small amounts, values below the display threshold are now shown as “< 0.01” to match the behavior seen in ARK Scan.
We also refactored the demo application to use the ark-connect SDK instead of directly interacting with window.arkconnect. This ensures the demo reflects real-world usage and serves as a proper reference implementation. The demo now exercises core SDK functionality such as connecting, signing transactions, voting, and handling events within a browser environment.
Next week we will continue improving the Mainsail integration, focusing on refining data handling, improving reliability in external API interactions, and identifying any remaining areas of complexity that can be simplified. We’ll also monitor for any issues related to the new pricing provider and optimize caching and request handling where needed.
ARK Vault Weekly Report
This week we focused on improving Ledger support, refining transaction flows, and addressing several UX and migration-related issues.
We expanded Ledger transaction support by implementing signing for approve and batch transfer transactions, as well as improving overall Ledger handling across multiple transaction types. This includes transfers (standard, multipayment, and token), registrations (username, validator, contract deployment), and voting. These changes ensure more consistent and reliable hardware wallet interactions across the application.
We also introduced updates to the asset selector, aligning it with the latest design and improving usability. Enhancements include displaying remaining balances in multiple mode, clearing recipients when switching modes to prevent overspending, disabling the selector when necessary, and fixing issues where duplicate labels caused incorrect selections.
Several UX fixes were applied, including correcting layout issues in the batch transfer confirmation screen on mobile and ensuring that the migration completion flow no longer shows a misleading “Stop the Migration?” confirmation once the process is finished.
In the migration flow, we improved accuracy and clarity by filtering out wallets with dust balances and limiting scanned addresses to only those relevant for migration (excluding account index addresses that do not require migration).
We also resolved multiple runtime issues, including errors triggered in newer Chrome versions due to lifecycle cleanup in useEffect, and navigation-related errors caused by window.scrollTo.
Finally, we fixed broken E2E transaction tests affected by recent refactors, restoring test reliability and coverage for transaction-related flows.
We also released ARK Vault v1.20.0, which addresses stability and restores market data functionality, ensuring price information is available again. In addition, an issue affecting the voting flow for users on Chrome v150+ was resolved. There have also been several other improvements, including caching price requests to reduce rate limit errors, UI fixes for the server status and settings dropdowns, and other stability improvements.
No action is required, as the updates have already been deployed to ARK Vault App .
Full release notes are available on the GitHub Releases page .
Next week we will continue improving stability and polishing transaction flows, with a focus on edge cases in Ledger interactions and migration scenarios. We’ll also address any new issues identified during testing, refine mobile UX where needed, and continue enhancing overall reliability and user experience.
Mainsail Weekly Report
This week we focused on strengthening security, improving Ethereum compatibility, and expanding test coverage across key components.
In the EVM package, we introduced several security hardening measures and fixes. This includes removing unused or obsolete logic such as the genesis-info timestamp and legacy cold-wallet merge handling in preverify_transaction. We also added bindings coverage tests to ensure better reliability at the interface level.
We improved Ethereum compatibility within the crypto-transaction module by encoding r and s signature values as minimal integers, aligning with standard Ethereum hashing expectations. Additionally, stricter validation was introduced in the deserializer to reject non-canonical RLP integers and out-of-range signature values, improving correctness and security.
For the api-evm, we enhanced resilience against request amplification by processing JSON-RPC batch requests in controlled chunks. Batch sizes are now capped and execution concurrency is bounded, preventing excessive resource usage under heavy or malicious loads.
We continued expanding test coverage across the codebase, adding both unit and integration tests for the api-http package, as well as improving coverage and fixing issues within the api-sync module.
In the api-database, we added validation for attribute keys used in JSONB path lookups, reducing the risk of malformed or unsafe queries.
Within P2P, we improved network robustness by ensuring that broadcasting continues to other peers even if one peer is throttled, preventing unnecessary delays in message propagation.
Next week, we will continue expanding unit test coverage across the remaining modules and further harden critical components. We’ll also focus on performance tuning, identifying edge cases under load, and refining network and API resilience to ensure consistent behavior in real-world conditions.
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 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.
