Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, the ARK Scan team finalized the Network Map feature and focused on improving the overall codebase through targeted optimizations and cleanup efforts. On the documentation side, we expanded API coverage, improved consistency across developer resources, and updated the Python client to return properly type-hinted responses. The ARK Vault team concentrated on strengthening reliability and overall quality by expanding and refining test coverage across key areas of the application. Meanwhile, the Mainsail team worked on improving stability and performance, with particular focus on the EVM layer.
Development Activity Summary (April 03 – April 10, 2026)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from April 03, 2026, to April 10, 2026.
| Project | Commits | Authors |
|---|---|---|
| ARK Connect | 0 | 0 |
| ARK Scan | 12 | 2 |
| ARK SDKs & Docs | 16 | 1 |
| ARK Vault | 24 | 2 |
| Mainsail | 38 | 2 |
During this period, the team maintained strong productivity and engagement, delivering 90 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 finalized the Network Map feature and focused on improving the overall codebase through targeted optimizations and cleanup efforts. As part of this work, we removed outdated Cloudflare IPFS links to ensure the codebase remains current and free of unused references. We also reintroduced the official Analyzer dependency, replacing the previously used fork now that upstream maintenance has resumed, helping us stay aligned with the original package.
In addition, we improved navigation by adding the Network Map under the Resources section in the navbar and routing it to /network-map, making the peers visualization easier to discover. We streamlined transaction handling by adopting the TransactionTypeIdentifier from the TypeScript crypto SDK instead of relying on a local model, reducing duplication and improving consistency across the app. Lastly, we rewrote the vote report from Bash to PHP, making it more maintainable and better integrated with the existing codebase.
Next week, we’ll continue addressing reported issues while working on further optimizations and legacy code cleanup.
ARK SDKs & Documentation Weekly Report
This week, we focused on improving our Documentation site by expanding API coverage and ensuring consistency across developer resources. We added all token-related endpoints to the public API documentation, complete with detailed descriptions and practical examples to make integration easier for developers. Additionally, we updated all Python SDK examples to use the new query dictionary pattern instead of kwargs, aligning the documentation with the recently refactored Python client and promoting a more consistent usage approach.
We also made progress on the Python client by updating endpoints to return properly typehinted responses. While query parameters were already defined using TypedDicts, this update extends type safety to actual response structures, bringing the Python client closer in line with the TypeScript SDK and improving the overall developer experience.
Next week, we’ll continue enhancing developer tooling and documentation, while supporting ongoing improvements and addressing any emerging issues across the platform.
ARK Vault Weekly Report
This week, we have been focused on strengthening the overall reliability and quality of the ARK Vault app by expanding and refining our test coverage across key areas of the platform. We added coverage for the exchange, wallets, and profile domains, while achieving full coverage for both the dashboard domain and core libraries. In addition, we continued to increase coverage across shared libraries and resolved a timeout overflow warning issue to improve stability. On the development side, we also introduced helpful mnemonic validation tips to enhance user experience and security during wallet setup and recovery.
Next week, we’ll continue to work on test coverage as well as address any of the reported issues.
Mainsail Weekly Report
This week, we focused on improving the stability and performance of Mainsail, particularly within the EVM layer. We implemented the missing block_hash functionality in the underlying EVM database, ensuring more complete and reliable block data handling. We also fixed an issue in the receipt event parsing logic where a premature loop exit (using break instead of continue) could lead to incomplete processing.
Performance optimizations were another key area of work. We improved state root calculation by eliminating unnecessary object cloning, and enhanced overall hash computation during commit operations by reducing memory allocations and avoiding redundant recalculations. In addition, we increased unit test coverage across the EVM package to strengthen reliability, and prepared our CI pipelines and scripts for compatibility with Node 24 LTS.
Next week, we’ll continue expanding test coverage and begin preparations for the upcoming testnet upgrade.
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.
