Welcome to this week’s Weekly Development Report, highlighting continued progress across the ecosystem, with ongoing work focused on keeping our tooling up to date, improving reliability, and aligning components as development moves forward. This week, Mainsail saw further improvements to configuration validation, consensus-related functionality, and EVM integration, alongside additional testing and build workflow updates. Dependency and tooling updates also progressed across ARK Connect, the SDKs, and documentation, while work continued on keeping these components aligned with the latest Mainsail changes.
Development Activity Summary (September 25 – October 02, 2026)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from September 25, 2026, to October 02, 2026.
| Project | Commits | Authors |
|---|---|---|
| ARK Connect | 12 | 2 |
| ARK Scan | 0 | 0 |
| ARK SDKs & Docs | 42 | 3 |
| ARK Vault | 0 | 0 |
| Mainsail | 29 | 4 |
In total, 83 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’s ARK Connect work focused on the demo app, with its hardcoded configuration values moved into environment variables. Default values are provided, so configuring a separate .env file remains optional while still allowing the settings to be adjusted when needed. We also updated the demo app’s core dependencies, including Next.js 16, React 19, ESLint 10, and Tailwind CSS 4, along with updates to TanStack React Table, i18next, and other dependencies. The Tailwind migration also included a few UI fixes, such as restoring button cursors and adjusting modal stacking, while BigNumber.js was reverted due to a change in how invalid input is handled.
Next week, we’ll continue improving ARK Connect based on the recent Mainsail changes and address any updates needed to keep the integration in line with the latest development.
ARK SDKs & Documentation Weekly Report
This week’s work on the ARK Docs and SDKs focused on bringing dependencies and tooling up to date across the board, along with an update to how proof-of-possession is built for validators. On the documentation side, the Mainsail docs site received a broad dependency refresh. Next.js was updated to 15.5.15 and is now pinned to an exact version together with eslint-config-next, Tailwind CSS moved to 4.3.3, TypeScript to 5.9.3, and the Meilisearch client to 0.62.0, alongside updates to ESLint, Prettier, sharp, and a number of smaller packages. The project now also declares pnpm 12 as its package manager, and @types/node was aligned with the Node.js 24 engine requirement, keeping the site’s builds consistent and reproducible.
The TypeScript Client SDK was moved to pnpm 12, and its development tooling was upgraded, including Jest 30.5, ESLint 10.11, typescript-eslint 8.70, Prettier 3.9, esbuild 0.28.2, and @types/node 26.6. The GitHub workflows were updated to match the new pnpm version and tooling, so tests and checks continue to run reliably in CI.
The TypeScript Crypto SDK received the same pnpm 12 upgrade, development tooling updates, and workflow changes, along with updates to its core cryptographic dependencies. @noble/curves and @scure/bip39 were updated to 2.4.0, ethers to 6.17.0 and bignumber.js to 11.1.5. BLS key derivation now comes from micro-eth-signer, replacing the previously used micro-key-producer package. In addition, proof-of-possession building was refactored to include the chainId and registrantAddress parameters. This binds each proof to a specific network and registering address, so a proof created for one chain or address cannot be reused elsewhere, adding another layer of precision to how validator identities are verified.
Next week, work will continue on dependency updates across the remaining SDKs and tooling, along with further CI improvements and keeping the documentation in step with the latest Mainsail changes, as preparations for the upcoming testnet reset continue.
Mainsail Weekly Report
This week’s Mainsail work focused on tightening configuration and consensus checks, improving EVM integration, and expanding test coverage.
Additional validation was added for the crypto configuration to ensure the genesis milestone and the following milestone are configured with the expected round validator settings. Chain IDs are now passed through to the EVM so contracts can use the correct block.chainid, and EVM dependencies were updated. We also fixed a round validator conversion issue caused by the latest Rust update and updated proof-of-possession signing to include the chain ID and registrant address, limiting proofs to the address and chain they were created for.
Native contract events are now collected and emitted when a block is committed, covering events such as validator registration, resignation, and updates, voting changes, and username registration and resignation. Additional unit tests were added for the processor and utils packages. GitHub release workflows were also updated to simplify Rust package builds, fix version publishing, and adjust pnpm installation settings, while a jemalloc warning was resolved.
Next week, we’ll focus on P2P work, fixing transaction signing for second signatures, and addressing additional edge cases as they come up.
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.
