7th Aug 2026
5 min read

ARK Development Report - August 07, 2026

Welcome to this week’s Weekly Development Report, highlighting continued efforts in simplification, consistency, and system reliability across the ecosystem. The ARK Scan team focused on streamlining user interaction by simplifying the contact flow and unifying formatting tools to improve development efficiency. The ARK SDKs and Documentation team delivered substantial progress in both the Go Client and Crypto SDKs, aligning them closely with Mainsail through improved data models, safer handling of large values, expanded API support, and enhanced consistency across the ecosystem. The ARK Vault team continued refining the user interface by standardizing dropdown components across key areas, improving usability and reducing complexity. Meanwhile, the Mainsail team strengthened P2P synchronization, enhanced consensus robustness, and continued cleaning up core components, resulting in better network stability and maintainability.

Development Activity Summary (July 31 – August 07, 2026)

Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from July 31, 2026, to August 07, 2026.

Project Commits Authors
ARK Connect 0 0
ARK Scan 7 1
ARK SDKs & Docs 36 2
ARK Vault 11 1
Mainsail 40 3

In total, 94 commits were merged across all projects this week. As always, commit counts fluctuate with sprint focus and task complexity.

ARK Scan Weekly Report

This week focused on simplifying user interaction and improving development workflow consistency.

We updated the contact page by removing the form-based approach in favor of a direct email contact method. This reduces maintenance overhead and provides a simpler, more reliable way for users to get in touch.

On the tooling side, we streamlined formatting workflows by removing Rustywind and standardizing on Prettier as the single formatting solution. This avoids conflicts and repetitive formatting loops between tools. Additionally, we configured Prettier to ignore resources/views/vendor/, as this directory contains published vendor components (such as pagination views) that should not be reformatted.

Next week we will continue improving ARK Scan by refining the UI and performance, addressing any reported issues, and making incremental enhancements to maintain a clean and efficient codebase.

ARK SDKs & Documentation Site Weekly Report

This week focused on significant improvements to both the Go Client SDK and Go Crypto SDK, aligning them more closely with Mainsail while improving correctness, consistency, and overall developer experience.

In the Go Client SDK, we replaced all Delegate references with Validator, bringing terminology in line with Mainsail. A major refactor addressed Wei-scale overflows by introducing a BigInt wrapper around *big.Int, ensuring large values such as balances, fees, gas, and rewards are handled safely.

We also reshaped response models to reflect Mainsail’s actual API structure:

  • Wallets now use a nested attributes object
  • Transactions follow an EVM-style format (hash, value, gas, gasPrice, receipt)
  • Blocks were flattened and aligned (id → hash, height → number)
  • Additional updates across Node, Peer, Commit, Blockchain, and related services

API signatures were updated to use string-based identifiers (hashes) instead of numeric IDs, and several inconsistencies were resolved, including incorrect response mappings and routing issues for unconfirmed transactions.

We expanded coverage by implementing new Mainsail endpoints, including tokens, receipts, and EVM-related services, and removed legacy Core transaction type remnants. Additional cleanup included defining proper transaction request shapes, updating dependencies, and removing outdated comments.

In the Go Crypto SDK, we introduced legacy address handling, added support for using a passphrase in validator registration/update flows, and implemented missing methods to align functionality with other SDKs. These updates were supported with additional unit tests to ensure reliability.

Next week we will focus on integrating these Go SDK changes into the documentation site, ensuring all new features, APIs, and breaking changes are clearly documented. We will also continue refining both SDKs, improving test coverage, addressing edge cases, and enhancing overall developer usability and consistency across the ecosystem.

ARK Vault Weekly Report

This week focused on improving UI consistency and simplifying component usage across key areas of the application.

We expanded the adoption of the simplified dropdown component across both the portfolio and profile domains. In the portfolio domain, this included updates to the welcome screen (profile row options), settings sidebar on smaller screens, and contact row options. In the profile domain, the same simplified dropdown was implemented across the welcome page, contacts page, settings menu (on smaller screens), and vote filter controls.

These changes help standardize interaction patterns, reduce component complexity, and ensure a more consistent user experience across different sections of the application.

Next week we will continue refining the UI and user experience, addressing any inconsistencies or edge cases, and resolving issues identified during testing. We will also focus on further component cleanup and performance improvements to keep the interface responsive and maintainable.

Mainsail Weekly Report

This week focused on improving P2P reliability, strengthening consensus handling, and continuing cleanup across core components.

We resolved several block download issues in P2P, ensuring the correct block range is requested during retries, purging pending jobs once blocks are applied, and skipping already applied blocks instead of incorrectly banning peers. These changes significantly improve synchronization stability and peer interaction.

In the consensus layer, we added safeguards to skip blocks that have already been committed concurrently, preventing duplicate processing. We also addressed an edge case where the system could get stuck if a peer returned an empty proposal, improving overall robustness.

We performed cleanup work on the block downloader, removing unused code to simplify maintenance and reduce complexity.

Additional improvements include:

  • Support for presigned validator registrations in the genesis block generator
  • Updated exported function signatures in evm-contracts for better consistency
  • Added support for pnpm 11, keeping tooling up to date

Next week we will continue improving P2P networking, refining EVM compatibility, and expanding test coverage to ensure stability and performance across the system.

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.

Share:

Get in Touch!

Whether you want to learn more about ARK Ecosystem, want to apply for developer bounty, become our partner or just want to say Hello, get in touch and we will get back to you.



An Ecosystem of Developers

Join us on our journey to create the future of Web3.