Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, the ARK Scan team continued migrating the codebase to Inertia while addressing several reported issues. On the SDK side, the TypeScript Client was improved with pagination support for the token addresses endpoint. The ARK Vault team continued progressing on the Tokens feature integration, while the Mainsail team focused on expanding ERC-20 support across the API and core services.
Development Activity Summary (January 09 – January 16, 2026)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from January 09, 2026, to January 16, 2026.
| Project | Commits | Authors |
|---|---|---|
| ARK Connect | 0 | 0 |
| ARK Scan | 42 | 2 |
| ARK SDKs & Docs | 2 | 1 |
| ARK Vault | 78 | 3 |
| Mainsail | 63 | 2 |
During this period, the team maintained strong productivity and engagement, delivering 185 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 Scan Weekly Report
This week, we continued migrating the codebase to Inertia while also addressing several reported issues. Work completed includes:
- Integrated the home page blocks section into Inertia, bringing blocks data into the unified Inertia-based home view for smoother navigation and improved performance.
- Enhanced dropdown interaction behavior in Inertia so selections register when clicking anywhere within a highlighted option, improving usability and consistency.
- Transitioned home page network statistics to Inertia, updating the layout to match the new design and making gas fee information more prominent.
- Moved the home page market overview to Inertia and refreshed the chart area to align with the updated design, reusing the existing chart components with new background elements.
- Added a bottom call-to-action banner on the Inertia home page to promote ARK Vault.
- Brought the Compatible Wallets page into Inertia, ensuring a consistent experience across informational pages.
- Ported the Block Detail page to Inertia, aligning block views with the rest of the Inertia-based navigation.
- Cleaned up legacy home components and removed the temporary
home-oldroute fromroutes/web.phpafter completing the migration. - Restored and fixed browser tests in
WalletTest.phpfor the Inertia homepage, ensuring automated workflows validate expected behavior. - Migrated the
/support(Contact) page to Inertia while preserving conditional visibility and keeping mail handling on the PHP backend. - Corrected contract address links in tables so “Contract” recipients now navigate to their respective contract pages without 404 errors.
Next week, we’ll continue progressing the Inertia migration and address any remaining issues or bugs that arise.
ARK SDKs and Docs Weekly Report
This week, we improved the token addresses endpoint in the TypeScript Client by adding pagination support. The endpoint now accepts page and limit parameters, making it easier to work with larger token datasets and control response sizes more effectively.
The updated endpoint supports requests such as:
api/wallets/tokens?addresses=a,b&page=1&limit=10
In addition, we released v0.13.0 of the package, enabling these improvements to be used in our products.
ARK Vault Weekly Report
This week, we continued working on the Tokens feature integration. Work done includes:
- Implemented a token reload feature that refreshes the latest tokens for the selected address(es) when the refresh button is clicked, updating the UI accordingly.
- Added a “Hide Dust” toggle to the tokens page that hides tokens with a balance below 1, with the toggle state persisting across page visits; future updates will refine this based on supply and fiat value.
- Added token selection to the token transfer flow UI, enabling users to choose which token to send. The default asset is ARK unless a specific token is preselected, and flows adapt based on token ownership; actual token sending logic will be implemented in a separate task.
- Implemented a tokens overview table for screens >768px with backend support for fetching tokens across multiple addresses, pagination, loading skeletons, and periodic updates. Refactored the token service for improved performance, added table columns per design, and included unit tests for both SDK and UI.
- Added a tokens overview table for mobile devices, adapting the layout and functionality for smaller screens while maintaining feature parity with the desktop version.
- Implemented the token receive flow by connecting the receive button to the existing receive mechanism, allowing users to receive tokens without altering selection logic.
- Fixed the token details side panel so it can be reopened multiple times after closing, ensuring consistent behavior when selecting tokens from the tokens table.
Next week, continue to integrate the Tokens feature and address any of the reported issues or bugs.
Mainsail Weekly Report
This week, we focused on expanding ERC-20 support across the API and core services. Work completed includes:
- Restructured service providers by extracting them into dedicated
service-provider.tsfiles outside ofindex.ts, laying the groundwork for more effective and isolated unit testing. - Introduced ERC-20 token support by enabling Mainsail to detect ERC-20 transfers and verify whether they belong to a valid ERC-20 contract. Contract detection is based on common view methods (such as
totalSupply,name, andsymbol), with support for executing core ERC-20 transactions in isolation (e.g.,transfer,transferFrom). - Exposed new public API endpoints to access ERC-20 data and activity, including:
/wallets/tokens/wallets/{id}/tokens/tokens/tokens/transfers/tokens/{address}/tokens/{address}/transfers/tokens/{address}/holders
Next week, we’ll continue enhancing ERC-20 functionality and focus on expanding unit test coverage to improve reliability.
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.
