Welcome to our latest Weekly Development Report, where we highlight ongoing progress across our ecosystem. This week’s development focused on simplification, consistency, and performance across the ecosystem. ARK Connect reduced legacy complexity and aligned modules with current Mainsail requirements, improving maintainability. ARK Scan standardized workflows and integrated shared AI conventions to support future tooling. Work on the TypeScript Crypto package expanded cryptographic features and validator flows. ARK Vault streamlined dependency management with a controlled update cycle. Meanwhile, Mainsail delivered key performance gains, simplified architecture, and improved concurrency, with test coverage progressing across key packages.
Development Activity Summary (June 12 – June 19, 2026)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from June 12, 2026, to June 19, 2026.
| Project | Commits | Authors |
|---|---|---|
| ARK Connect | 16 | 2 |
| ARK Scan | 12 | 1 |
| ARK SDKs & Docs | 37 | 2 |
| ARK Vault | 5 | 1 |
| Mainsail | 35 | 2 |
In total, 105 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 codebase, reducing unused complexity, and aligning internal modules with current Mainsail requirements.
A major refactor was carried out in the profiles layer. We replaced the existing implementation with a minimal profile module, removing a significant amount of unused and redundant code that was originally inherited from the PSDK. This included eliminating duplicate functionality, cleaning up unnecessary exports, and removing tsdoc comments that were not relevant for the extension. At the same time, we ensured that all core functionality, such as password handling, encryption, locking, and unlocking, remains intact. Code formatting was also standardized, where it had previously been ignored.
We also updated the Mainsail PSDK-related files within the project. Similar to the profiles refactor, this involved removing unused code, reducing duplication, and applying consistent formatting. These changes help streamline the integration layer and make future updates easier to manage.
Next week, we will continue refining the Mainsail integration to ensure full compatibility, further simplify and modernize internal modules, and address any issues identified during testing. We’ll also continue improving code quality and maintainability across the extension.
ARK Scan Weekly Report
This week we focused on standardizing workflows and preparing the codebase for upcoming AI-driven tooling and shared development conventions.
We updated the dependency management workflow to run on a monthly schedule. This helps reduce noise from frequent updates while still keeping dependencies reasonably up to date and maintainable.
We also integrated the ArdentHQ AI conventions across the project. Using the @ardenthq/airc CLI, we added shared guidelines for core, PHP, and JavaScript directly into the repository. This setup introduces a centralized .claude/ardenthq/ configuration and extends the existing CLAUDE.md with managed imports, while keeping prior Laravel Boost configurations intact.
As part of this integration, we ensured that convention files are automatically kept in sync by adding a post-update-cmd hook to composer.json. This guarantees consistency across environments whenever dependencies are updated. Additionally, CLAUDE.local.md is now ignored to allow for local, non-versioned overrides.
This work lays the foundation for more consistent development practices and smoother adoption of upcoming AI-assisted tooling across the project.
Next week, we will monitor the integration and address any issues that arise, continue with general optimizations where needed, and ensure the new conventions are properly adopted across the codebase.
ARK SDKs & Documentation Site Weekly Report
This week, we focused on expanding capabilities within the PHP Crypto package and aligning SDK functionality with recent protocol updates.
We introduced legacy address handling, ensuring compatibility with older address formats and improving interoperability across different network states and historical data.
We also added support for batch transfers by implementing a dedicated builder, enabling the creation of multipayment transactions directly within the PHP SDK. This aligns with similar functionality introduced in other SDKs and provides developers with more flexibility when constructing transactions.
A key addition this week was the implementation of BLS key derivation. This includes the ability to derive BLS keys from a passphrase and generate proofs of possession, which are now required for validator operations. The implementation is fully covered with unit tests to ensure correctness and reliability.
In line with these changes, we refactored validator registration and update flows to use a passphrase instead of a public key. This ensures consistency with the updated signing requirements and improves the overall developer experience.
On the maintenance side, we integrated ArdentHQ AI conventions into the repository, establishing a shared structure for development guidelines and preparing the project for future AI-assisted tooling.
Next week, we will continue improving SDK functionality and consistency across languages, expand documentation to cover newly introduced features, and further enhance test coverage. We will also address any issues identified during usage and continue refining the developer experience.
ARK Vault Weekly Report
This week, we focused on improving maintainability and reducing unnecessary overhead in dependency management.
We updated the dependency update workflow to run on a monthly schedule instead of more frequently. This helps reduce noise from constant dependency updates while still ensuring the project remains up to date and secure. It also allows for more controlled upgrades, making it easier to identify potential issues and maintain stability across releases.
Next week, we will continue with dependency upgrades where needed, monitor for any issues introduced by recent changes, and focus on ongoing improvements to stability, performance, and test coverage across the application.
Mainsail Weekly Report
This week, we focused on performance improvements, simplifying core architecture, and strengthening concurrency handling across Mainsail, while continuing to expand test coverage.
In the crypto-transaction layer, we improved transaction verification performance by precompiling the regex used for bytecode length validation. This avoids repeated compilation overhead and dynamically recompiles only when the maximumGasLimit changes via milestone updates. We also optimized forging performance by reusing already validated transaction data from the transaction pool, such as transaction hash and sender public key, reducing redundant computations.
Within the P2P layer, we modernized the codebase by updating protobuf.js to use ESM output. We also removed support for the x-forwarded-for header, simplifying the networking layer and reducing potential misuse or ambiguity in peer identification.
In the kernel, we streamlined service provider handling by removing optional and redundant configurations. All service providers defined in app.json are now strictly required, eliminating ambiguity and simplifying boot logic. We also removed obsolete environment variables (NETWORK_NAME, TOKEN, VERSION) and introduced various smaller fixes and improvements to increase overall maintainability.
Significant enhancements were made in the EVM package. Database resize handling was improved to safely operate within the consensus instance, with up to three attempts to increase the database size in 1 GB increments when limits are reached. This process no longer interferes with other EVM instances, such as the transaction pool or API. We also enabled concurrent reads using RwLock, improving read performance under load. Additionally, we introduced a semaphore mechanism to prevent EVM resource exhaustion. While the main thread (consensus and forger) remains unrestricted due to mostly serial execution, the transaction pool and RPC API are limited to 192 concurrent threads each, ensuring balanced resource usage and leaving sufficient capacity for the main process.
In other areas, we enhanced the test runner by adding type support, extending functionality, and applying various fixes. We also resolved Docker build issues by downgrading pnpm to v10 and ensuring the EVM package builds correctly within Docker environments that require Rust toolchains.
Test coverage continues to improve, with the test runner now at 100% coverage and the kernel reaching 98%.
Next week, we will continue expanding unit test coverage across the remaining modules, further optimize performance-critical paths (especially in EVM and transaction processing), and validate concurrency mechanisms under load. We’ll also address any issues identified during testing and continue refining build and deployment 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 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.
