Development Activity Summary
This report details the development efforts across the ARK Ecosystem from August 22 to August 29, 2025. The development team maintained strong productivity, delivering a total of 118 merged commits across all projects. This figure may fluctuate weekly due to the dynamic nature of internal sprints, evolving objectives, and task complexity.
ARK Scan Weekly Report
The ARK Scan team focused on enhancing loading performance and resolving several identified issues. Key accomplishments include:
- •The validator monitor was refactored to optimize initial load performance. This involved improving data handling and deferring the loading of less critical metrics. To ensure a consistent layout, column widths across both monitor tables were fixed, preventing issues even when dealing with overflow validators.
- •The block export functionality was fixed by updating the height attribute to use a number type, aligning with recent API changes. Default API endpoints were also updated to direct to the public testnet version.
- •The multipayment transaction detail page was corrected to prevent errors. This was achieved by ensuring that a valid model or address is provided when viewing multipayment details.
Moving forward, the team will continue to prioritize performance improvements in ARK Scan to achieve faster load times and address any outstanding reported problems.
ARK SDKs and Docs Site Weekly Report
This week's efforts for the ARK SDKs and Docs Site were concentrated on the TypeScript SDK package. Significant updates include the introduction of ABI error decoding and the addition of query parameter support for transaction calls.
In the upcoming week, the team will continue to refine the SDKs based on feedback from developers integrating them into ARK's products. Documentation updates will be made accordingly to reflect these changes.
ARK Vault Weekly Report
The ARK Vault team concentrated on introducing new features to the side panel and enhancing the user experience for displaying errors related to failed transactions, alongside other improvements. Completed tasks include:
- •The transfer and multipayment flows have been refactored to operate within the side panel. This consolidation allows for the reuse of common elements such as fees and logic across different transaction types. Safeguards have been implemented to prevent accidental closure of the side panel once a transaction flow has commenced; users can now only close it via the dedicated 'X' icon, with clear visual cues indicating protected data.
- •The subtitle prompting for a secret when sending transactions with a Ledger address has been hidden, as this is not required for Ledger users.
- •Human-readable error messages have been added to the transaction details side panel, providing contract-provided failure reasons for enhanced clarity.
- •A tooltip has been added to the method label in transaction rows, which appears when the text is truncated.
- •Multipayment transactions in advanced mode have been updated to utilize the estimated gas limit, and default advanced fees have been increased to mitigate transaction failures.
- •The transactions table UI has been adjusted with resized columns to prevent overlap. The method column width has been reduced on 768px views, timestamp wrapping has been prevented, and transaction ID badges for pending/error states have been expanded. The copy button positioning and test snapshots have been updated to reflect these modifications.
- •Transaction sending for Ledger hardware wallets has been fixed by resolving an unknown configuration value error.
- •The import flow has been updated so that the "Need Help" hint for mnemonic input is expanded by default, rather than being collapsed.
Next week, the team will continue to enhance the side panel, begin developing new features, and implement general advancements to the application.
Mainsail Weekly Report
This week's focus for Mainsail was on database and API improvements. Notable completed work includes:
- •The transactions and receipts Postgres tables have been merged into a single transactions table. This consolidation aims to reduce disk usage and improve overall performance.
- •Decoded errors have been added to the transactions table, supporting basic EVM errors and custom errors on default Mainsail contracts.
- •The implementation of returning a 503 HTTP status code during database restore has been completed. This indicates that the database is not yet ready for public API access.
- •EVM dependencies have been updated.
- •Unit test coverage for the CLI package has been increased.
The upcoming week will involve work on increasing test coverage, further API enhancements, and addressing Mainsail updates related to PNPM updates.
Feedback & Feature Requests
Users of our open-source products are encouraged to provide feedback or request features. Please reach out via the contact pages for the specific product you are using or open an issue on GitHub.
Direct links to GitHub issues pages are provided for convenience:
- •
- •
- •
- •
- •