Welcome to this week’s Weekly Development Report, highlighting continued progress across the ecosystem, with ongoing work focused on simplifying architecture, improving reliability, and preparing our products for their next stage of development. This week, Mainsail saw further work on simplifying consensus and improving state persistence and recovery, while testing and preparation continued across ARK Scan, ARK Vault, and ARK Connect. We also reviewed the current dependency versions across the front-facing applications ahead of a broader round of updates to bring them in line with the latest versions.
Development Activity Summary (September 11 – September 18, 2026)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from September 04, 2026, to September 11, 2026.
| Project | Commits | Authors |
|---|---|---|
| ARK Connect | 0 | 0 |
| ARK Scan | 0 | 0 |
| ARK SDKs & Docs | 0 | 0 |
| ARK Vault | 0 | 0 |
| Mainsail | 32 | 2 |
In total, 32 commits were merged across all projects this week. As always, commit counts fluctuate with sprint focus and task complexity.
Mainsail Weekly Report
This week’s Mainsail work focused on simplifying the consensus architecture, improving state handling, and making recovery more reliable. The consensus boot procedure was moved into the bootstrapper, allowing consensus to be initialized before P2P and started with its initial state, while test-only methods for manually setting consensus state were removed. The proposer reporter was also extracted into the validator package, separating reporting from the consensus logic and keeping the core consensus code easier to maintain. Validators now use pending validated commits to determine whether they should propose, skipping proposals while the node is catching up.
Consensus state and all verified messages and proposals are now persisted to disk, making the consensus storage the single source of truth and removing the previous double-sign protection logic. Message persistence was also moved to the point where messages are verified, improving the restore process after a restart. Functional test assertions were updated to check commits at the expected block height rather than relying on the latest commit, which avoids issues caused by the chain continuing to grow during tests. The kernel also gained a new failure-handling method that starts application termination without waiting for it, preventing a deadlock when consensus is being disposed from within a handler.
Next week, work will continue on block processing and P2P, with further integration between these components and consensus as the current work progresses.
Other Work Done
We continued internal testing of the front-facing apps, including ARK Scan, ARK Vault, and ARK Connect. We also documented their current dependency versions and outlined the updates needed across the apps to bring them in line with the latest versions.
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.
