Welcome to this week’s Weekly Development Report, highlighting continued progress across the ecosystem, with a focus on reliability, performance, and improving the stability of core applications and infrastructure. This week, Mainsail saw further improvements to consensus testing, P2P networking, API performance, and snapshot export validation. ARK Scan received updates to improve test reliability and simplify unused functionality, while ARK Vault released version 1.20.2 to address inconsistent fiat value displays and continued its dependency updates.
Development Activity Summary (October 16 – October 23, 2026)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from October 16, 2026, to October 23, 2026.
| Project | Commits | Authors |
|---|---|---|
| ARK Connect | 0 | 0 |
| ARK Scan | 8 | 1 |
| ARK SDKs & Docs | 0 | 0 |
| ARK Vault | 24 | 3 |
| Mainsail | 68 | 3 |
In total, 173 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’s ARK Scan work focused on improving test reliability, simplifying wallet submission, and removing unused dependencies.
The delegate monitor tests were updated to address intermittent failures affecting the overflow delegates and data box cases. These failures occurred inconsistently across local runs and CI, so the tests were made more deterministic to improve reliability and reduce unnecessary pipeline failures.
The wallet submission modal on the Livewire-based develop branch was also replaced with a mailto link, aligning it with the move away from the previous submission flow. In addition, the unused zendesk-laravel dependency and its associated personal fork repository were removed, as Zendesk is no longer used following the migration of the contact page to email. These cleanup changes were applied to the relevant development branches.
Next week, we’ll continue aligning ARK Scan branches with the latest changes, address any remaining issues identified during internal testing, and continue dependency cleanup and updates to keep the application stable and maintainable.
ARK Vault Weekly Report
This week’s ARK Vault work focused on improving transaction value consistency, keeping dependencies up to date, and releasing a patch addressing the fiat value display issue.
The transaction table was fixed to ensure fiat values consistently use the exchange rate from the transaction date across all screen sizes. Previously, larger screens used the historical rate while smaller screens used the current rate, causing the same transaction to display different values depending on the layout. The updated logic falls back to the current rate only when a transaction has no timestamp. This fix was included in ARK Vault v1.20.2, which was released this week. As a web wallet, ARK Vault updates automatically when users open it, so no manual action is required.
Dependency maintenance also continued with updates to p-queue and eslint-plugin-unicorn, alongside minor version updates across the remaining dependencies. These included updates to Vitest and its coverage package, TypeScript ESLint tooling, i18next, viem, Framer Motion, React Hook Form, PostCSS, and Testing Library’s user-event package.
Next week, we’ll continue updating dependencies across ARK Vault, address any compatibility issues identified during testing, and monitor the latest changes.
Mainsail Weekly Report
This week’s Mainsail work focused on improving consensus reliability, strengthening P2P networking, optimizing API performance, and making the legacy snapshot exporter more robust.
Consensus tests were fixed, including a restart race condition in the double-signing functional test. P2P improvements covered canonical formatting of remote IP addresses, API node discovery, and rejecting API node URLs that are not publicly accessible.
The API-HTTP package received a broader set of performance and reliability improvements. List parameters are now capped at 50 values, pagination is limited to 10,000 rows, and counts stop at 10,001 before being marked as estimates. Several slow queries were rewritten, covering value lists, token listings, wallet activity, token inclusion, and wallet attribute filters. Missing database indexes were also added for votes, block proposers, block sorting, token holders, and fee statistics. To reduce unnecessary database load, the API now returns a 503 response when the database is overloaded and avoids querying the database on every request for the maintenance flag and block number header. The /blocks?proposer= endpoint was also fixed to accept a proposer address.
Work on the legacy snapshot exporter focused on ensuring that exported data is consistent and validated against the V3 chain state. The exporter now reads the chain tip, totals, and wallet records from a single V3 snapshot, retrieving wallets in byte order through a cursor. It requires the V3 height and block ID to be specified and the V3 node to be stopped before exporting. Before proceeding, it validates the snapshot totals, including wallet existence, produced block counts, negative balances, and the relationship between balances, HTLC locks, and forged rewards. Duplicate wallets are rejected, and the exported wallets must match the expected totals. Additional changes include removing unimported attributes from the V3 side, improving connection-string handling to keep passwords out of logs and errors, increasing the statement timeout for cursor sorting, writing a manifest alongside the snapshot, and returning a non-zero exit code on failure. The EVM exporter was also updated to prevent cold wallets from being merged into legacy accounts.
Next week, we’ll continue work on snapshot imports and replace Hapi with a custom server in the P2P package.
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.
