Welcome to our latest Weekly Development Report, where we highlight ongoing progress across our ecosystem. This week, the ARK Connect team made major strides by starting to work on token functionality and advancing the migration to a new extension architecture. The ARK Scan team delivered a small but impactful UI refinement to improve visual consistency. The ARK Vault team enhanced reliability by improving cold wallet handling, fixing stability issues, and updating dependencies and workflows. Meanwhile, the Mainsail team strengthened security and consensus integrity while delivering targeted performance optimizations across the codebase.
Development Activity Summary (May 15 – May 22, 2026)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from May 15, 2026, to May 22, 2026.
| Project | Commits | Authors |
|---|---|---|
| ARK Connect | 63 | 4 |
| ARK Scan | 2 | 1 |
| ARK SDKs & Docs | 0 | 0 |
| ARK Vault | 85 | 3 |
| Mainsail | 22 | 2 |
During this period, the team maintained strong productivity and engagement, delivering 175 merged commits across all projects.
It’s important to note that weekly commit counts and project-specific data may fluctuate based on the focus of internal sprints, evolving objectives, and the complexity of tasks undertaken.
ARK Connect Weekly Report
A major area of progress was the introduction of token-related functionality across the application. We implemented the foundation for token-aware navigation by adding tabs that dynamically appear when a wallet holds tokens, while preserving the original transaction view for wallets without tokens. Building on this, we introduced a tokens overview tab that displays the assets owned by the user, initially showing the top 10 tokens with plans to extend this further. We also added a dedicated token detail page, allowing users to drill down into individual token information for a more complete view of their holdings.
Token support was further integrated into the transaction flow. We introduced an asset selector within the send form, enabling users to choose between ARK and any tokens they hold. This selector is shown conditionally based on whether the wallet owns tokens, ensuring a clean experience for users who only use the native asset. Alongside this, we implemented the actual token transfer functionality, completing the end-to-end flow for sending tokens directly within ARK Connect.
A significant portion of the work this week involved migrating the extension to a new architecture based on WXT. This included replacing vite-plugin-web-extension, introducing a base configuration, porting manifests, and restructuring background, content, in-page, and popup scripts into WXT entry points. We also updated development and build scripts, cleaned up environment variable handling, and removed hardcoded paths to make the project more maintainable and scalable. As part of this migration, we resolved several browser-specific issues, including fixing an invalid permission in the Firefox manifest and addressing a problem where the extension’s pop-up would fail to open or render correctly.
Next week, we’ll continue building on the newly introduced token functionality by refining the user experience, adding features such as pagination or “load more” for token lists, and improving performance and edge-case handling in token transfers. We’ll also continue stabilizing the WXT-based extension architecture, expand test coverage, and address any issues reported through ongoing testing.
ARK Scan Weekly Report
This week, we focused on a small but important UI refinement to improve visual consistency within ARK Scan.
We fixed an issue where the bookmark button appeared slightly larger than adjacent action buttons, causing a subtle misalignment in the interface. While minor, this inconsistency could make the layout feel uneven, particularly in areas where multiple actions are grouped together. The button has now been adjusted to match the size and alignment of its neighboring elements, resulting in a more balanced and cohesive appearance.
Next week, we’ll continue focusing on UI consistency and polish, alongside ongoing testing and addressing any reported issues.
ARK Vault Weekly Report
This week, we focused on improving cold wallet handling, stability, and overall reliability within ARK Vault, alongside important dependency and workflow updates.
A significant part of the work involved refining how cold wallets are managed. We removed unnecessary wallet syncing from the transaction fetching flow, ensuring that wallets are fully prepared earlier in the process. Building on this, we implemented a more robust approach for handling legacy cold wallets. When a wallet is not found via the standard API (returning a 404), we now detect it as a potential cold wallet, derive its Core ARK address, and query the dedicated legacy/cold-wallets endpoint. The retrieved balance is cached to avoid repeated requests, allowing users to view and interact with their legacy balances seamlessly. Once the wallet becomes active on the network, it transitions back to the standard flow.
On the stability side, we fixed several bugs, including profile loading failures caused by undefined transaction totals, token state not updating after refresh, and outdated ledger mocks in tests. We also improved CI reliability by updating the snapshots workflow and aligning it with current testing requirements.
Finally, we upgraded Node.js and various dependencies (minor and patch versions), ensuring compatibility across workflows and keeping the project up to date.
Next week, we’ll continue focusing on testing and stability, expand coverage around cold wallet scenarios, and address any issues that arise from these changes.
Mainsail Weekly Report
This week, we focused on strengthening security, improving consensus reliability, and optimizing internal performance within Mainsail.
A key update was made to the Consensus contract, where validator registration and updates now require both a BLS public key and a Proof of Possession. The proof is verified through a REVM precompile backed by a Rust implementation for BLS checks. This enhancement significantly improves network security by protecting against rogue key attacks and ensuring validator authenticity.
We also enhanced consensus message integrity by including the genesis block hash and previous block hash in validator messages (prevote and precommit). While the message size remains unchanged, these hashes are now part of the signing process, effectively preventing cross-chain replay attacks and mitigating risks associated with forked chain replays.
On the performance side, we replaced lodash’s deep clone functionality with a faster implementation using fastCopy, reducing overhead in critical code paths. Additionally, we fixed an issue with genesis account initialization to ensure it is correctly synchronized with the Postgres database when setting genesis information.
Next week, we’ll continue focusing on expanding unit test coverage around the new consensus and security features, while also addressing any issues that arise during internal testing and reviews.
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 on Twitter (X)
Follow us on X (Formerly Twitter) and keep checking the blog to stay up-to-date on all of our new releases. We post a weekly development report so you can easily see what we’ve been up to and follow along our journey towards making your decentralized future a reality.
