ARK Ecosystem

Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, the ARK Scan team continued progressing with the Inertia migration, implementing several small fixes and improvements along the way. On the documentation site, we added a new local setup guide for Mainsail to make onboarding easier for developers. The ARK Vault team focused on finalizing the Ledger migration feature and resolving profile import issues, while the Mainsail team worked on general enhancements and expanded test coverage to further strengthen overall stability.
Development Activity Summary (October 24 – October 31, 2025)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from October 24, 2025, to October 31, 2025.

During this period, the team maintained strong productivity and engagement, delivering 101 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 working on the Inertia migration along with several small fixes and improvements. Work done included:
Refactored the transactions table on the wallet page to use Inertia for better performance and consistency. Improvements include adding the Addressing component with mobile support, fixing pagination and fee rounding issues, enhancing responsiveness, resolving multipayment and known wallet name bugs, and updating tests and PHPStan checks for greater stability and accuracy.Added an automated formatting workflow to enforce a consistent code style across the project. The workflow automatically formats all TypeScript and TSX files, ensuring uniformity and readability throughout the Inertia codebase.Introduced type definitions for SVG icon imports to prevent module resolution errors.Updated the transaction amount display to remove the redundant currency symbol, as it is already indicated in the column header. This simplifies the UI and avoids duplicate currency information in the transactions table.Rebuilt the validated blocks table using Inertia, replacing the previous implementation. The new version aligns design and behavior with other Inertia-based tables, improving maintainability and user experience.
Next week, we’ll continue progressing with the Inertia migration and address any reported issues.
ARK SDKs and Docs Weekly Report
This week, we have added a local setup guide for Mainsail to the documentation site, helping developers quickly set up and run the project in their local environment. We have also added an explanation note to the “Install from Source” section of the documentation for NTP (Network Time Protocol) to ensure system clocks are synchronized during setup.
ARK Vault Weekly Report
This week, we focused on finalizing the Ledger migration feature and resolving profile import issues. Work done included:
Implemented Ledger migration for multiple addresses, allowing users to migrate several old addresses to a new derivation path while preserving their relative order. The process handles gaps in old indices to ensure the new addresses are consecutive and fully utilized. Approval logic was updated to support multiple transactions during migration, including scenarios where multiple old addresses are sent to a single new address.Added full-balance migration for Ledger wallets, automatically transferring the entire balance from the sender wallet. Once migration completes, the old wallet is removed from the profile to maintain a clean portfolio.Introduced a modal to display the profile migration result after the first portfolio load post-import. The modal highlights any migration issues, including merged duplicate addresses or contacts and items that could not be migrated due to missing outgoing transactions, giving users clear and actionable feedback.Fixed the import flow to correctly handle password-protected profiles correctly, ensuring encrypted profiles can be imported without errors and allowing seamless migration or restoration.Corrected the profile import process to ensure newly imported wallets are properly synchronized, preventing the “wallet has not been synchronized yet” error and enabling immediate usability after import.Added a confirmation modal for stopping a Ledger migration, prompting users to confirm before halting the process.Implemented stop migration logic for Ledger address migrations. Selecting “Stop Migration” now stops the migration safely, with the modal dynamically displaying the number of addresses already migrated for clear progress feedback.Updated pwned password mocks to ensure proper recognition during tests, improving test reliability and preventing skipped checks.Fixed padding for form buttons in the Profile Import flow, ensuring proper spacing and preventing divider lines from touching page buttons for a cleaner and more usable layout.
Next week, we’ll thoroughly test the Ledger migration feature, fix any issues discovered, and continue developing new features.
Mainsail Weekly Report
This week, we have focused on general enhancements and expanding our test coverage. The work completed included:
Further improved P2P statistics for enhanced network diagnostics.Updated the internal Testnet with the latest changes.Exported parseTransactionError from @mainsail/evm-contracts for easier accessibility.Added more functional tests for the Consensus and Usernames contracts.
Next week, we’ll continue refining P2P functionality and prepare a new public Testnet release (including reset and upgrade). We’ll also work on improving the CI Testnet sync workflow.
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:
Mainsail - https://github.com/ArkEcosystem/mainsail/issuesARK Connect (Extension) - https://github.com/ArdentHQ/arkconnect-extension/issuesARK Connect (Demo) - https://github.com/ArdentHQ/arkconnect-demo/issuesARK Scan - https://github.com/ArdentHQ/arkscan/issuesARK Vault - https://github.com/ArdentHQ/arkvault/issues
Follow on Twitter (X)
Follow us on X  (https://x.com/ArkEcosystem) 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.
$ARK

Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, the ARK Scan team continued progressing with the Inertia migration while making several general development improvements. The ARK Vault team concentrated on advancing the Ledger migration feature, and the Mainsail team focused on database enhancements, performance optimizations, and updates to logging and P2P functionality to further strengthen reliability.
Development Activity Summary (October 17 – October 24, 2025)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from October 17, 2025, to October 24, 2025.

During this period, the team maintained strong productivity and engagement, delivering 94 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 working on the Inertia migration and made several general development improvements. Work done included:
Updated the .nvmrc file to use Node.js version 22, replacing the outdated version 12 reference to align with the project’s current environment and avoid nvm-related issues.Integrated the typescript-transformer package to automatically generate TypeScript definitions from data objects, removing the need for manual type creation and ensuring consistent typing throughout the codebase.Added an Inertia-powered option to vote for a validator directly from ARK Scan when viewing a validator’s address, streamlining and simplifying the voting process.Replaced remaining manual types with Laravel-generated Spatie Data Objects that automatically convert to TypeScript. Introduced resources/inertia/global.d.ts to define shared PageProps, improving type reuse and consistency across current and future Inertia pages.
Next week, we’ll continue progressing on the Inertia migration, address any reported issues, and make further general improvements.
ARK Vault Weekly Report
This week, we focused heavily on the Ledger migration feature, which was the primary area of development. Work done this week includes:
Implemented Ledger connection handling for the migration flow, requiring users to connect their Ledger device before starting migration. The side panel now opens with a “Connect your Ledger” prompt, consistent with the existing Ledger import experience.Added support for 1:1 Ledger migration, enabling users to migrate a single address directly. After selecting an address, transaction details are displayed for review, sent to the connected Ledger for approval, and upon confirmation, the migrated address is added to the portfolio while the old one is removed. If a transaction is rejected, users can retry or cancel the process.Implemented address verification through message signing, allowing users to confirm ownership of a target address before migration. Supports both successful and failed verifications, with the ability to send messages to the Ledger for signing and validate them on Vault’s side.Added functionality to display migratable Ledger addresses after device connection, scanning the first five and highlighting those with funds. Users can scan more if needed and select which addresses to migrate, including performing single-address migrations that guide the following flow steps.Adjusted form button styling to correctly use dim mode colors, replacing the incorrect dark mode appearance for improved visual consistency.
Next week, we’ll be finalizing the Ledger migration flow while continuing to work on general improvements and design updates.
Mainsail Weekly Report
This week, we focused on database improvements, optimizations, and updates to logging and P2P functionality. Work done included:
Reconstructed EVM storage to store objects instead of serialized data, with compression applied. This change improves restore times and reduces database size by approximately 40%.Preserved error context in EVM-related errors for clearer debugging and tracing.Updated inversify to the latest version and replaced the constructor usage with the @postConstruct decorator in the InstanceManager for improved lifecycle management.Reformatted logs so that all entries align consistently in-line regardless of log level, improving readability.Implemented a new WorkerLogger class and removed worker logic from logger-pino, separating concerns for cleaner architecture.Added support for log contexts such as p2p, evm, consensus, and tx-pool, displaying context information in log output. Introduced initial color differentiation for each context to make logs easier to scan.Removed the critical and emergency log levels. The current log levels are now: alert, debug, error, info, notice, and warn.Removed the isValidLevel method from the logger interface to simplify and declutter the codebase.Implemented P2P statistics logging, recording average, median, minimum, and maximum latencies each round, along with totals for peers, banned peers, and peers pinged in the last round.
Next week, we’ll continue working on P2P improvements and optimizations, as well as expanding unit test coverage for a more robust codebase.
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:
Mainsail - https://github.com/ArkEcosystem/mainsail/issuesARK Connect (Extension) - https://github.com/ArdentHQ/arkconnect-extension/issuesARK Connect (Demo) - https://github.com/ArdentHQ/arkconnect-demo/issuesARK Scan - https://github.com/ArdentHQ/arkscan/issuesARK Vault - https://github.com/ArdentHQ/arkvault/issues
Follow on Twitter (X)
Follow us on X  (https://x.com/ArkEcosystem) 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.

$ARK

Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, the ARK Scan team focused on resolving reported issues and implementing general improvements, while the ARK Vault team began work on the Ledger migration feature and made several UI fixes and updates based on design and testing feedback. Meanwhile, the Mainsail team implemented additional logging to capture detailed timing information, improving debugging options.
Development Activity Summary (October 10 – October 17, 2025)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from October 10, 2025, to October 17, 2025.

During this period, the team maintained strong productivity and engagement, delivering 95 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 focused on resolving reported issues and implementing general improvements. Work done included:
Fixed the username search functionality so that searching for a username now correctly returns the associated address.Corrected the address detail display on mobile, ensuring the total rewards shown in the validated blocks section match the accurate value.Refactored icon import handling to use a generic <Icon name="..." /> component, automating SVG imports and removing the need for manual icon component creation.
Next week, we’ll continue making general improvements and addressing any reported issues from the community and internal testing.
ARK Vault Weekly Report
This week, we began work on the Ledger migration feature and focused on fixing and updating the UI based on design and testing feedback. Work done includes:
Added a Ledger migration banner and menu option that displays for users with wallets eligible for migration. Implemented cancel functionality with a tooltip and a red dot indicator on the address menu, with user preferences stored in local storage per profile.Adjusted the copy button placement on mobile to ensure consistent positioning across all views and prevent layout shifts.Updated the side panel to show a maximize icon when minimized, clearly indicating how to restore the panel.Added a sender label to the send registration form, highlighting the selected parameter with a background for better visual feedback.Fixed transaction error flows by updating the icon to correctly reflect errors instead of using an incorrect symbol.Rounded balance display amounts to six decimal places on mobile, preventing long values from breaking the layout.Adjusted padding on the review step across all transaction forms, updated the fee input to match new design specifications, and fixed layout issues in the transaction details modal.Enhanced the TransactionSummary component to display numerical values consistently and added allowHideBalance support for uniform behavior across summary and transaction detail views, with updated snapshots.Fixed line height in side panel descriptions to reduce spacing between lines.Corrected the transaction status error icon size to 12px with thinner lines for improved visual consistency.Updated settings export layout by setting 16px padding between sections for uniform spacing.Improved state handling in validator and username registrations, resolving an issue where the continue button remained disabled during registration or key updates.Adjusted padding in the name edit view to align the delete button area with the rest of the layout.Reduced the size of the Scan QR modal for a more compact display of the QR code and window.Adjusted transaction dropdown padding on mobile in the portfolio view, setting the spacing between elements and the “x results” label to 24px for a cleaner layout.Fixed font sizes in transaction review and validator resignation steps on mobile, ensuring consistency and readability across views.Aligned the “More Details” section in the transaction summary on mobile by applying the containerClassname prop in the TransactionDetailContent component for layout consistency.Updated dark mode modal styling with a dark/dim-950 background at 80% transparency, added subtle shadows, and refined framing for better visual clarity.Refactored transaction review pages by removing divider lines between details, resulting in a cleaner and more cohesive UI.Updated portfolio icons for dark mode, setting the default color to dark/dim-200 and hover state to dark/dim-50 for improved visibility and contrast.Refactored dropdown styling to adjust hover colors in dark mode, ensuring alignment with updated design guidelines.Fixed wallet icon sizing so that the name icon matches the size of icons on the right side.Adjusted the settings header background to dark/dim-950 for better dark mode consistency.Updated dark mode dropdowns by adding a border and rounding corners to 12px, changing divider lines to dark/dim-700, and removing extra padding in main menu dropdowns for a more polished look.
Next week, we’ll continue developing the Ledger migration feature and address any reported issues.
Mainsail Weekly Report
This week, we implemented additional logging to capture detailed timing information, specifically, when a block is created by the forger, proposed, and broadcast to the network. These enhanced logs will make it easier to trace block propagation steps and diagnose issues more efficiently during debugging.
Next week, our focus will shift to improving the P2P layer and adding more debug logs, alongside planned database optimizations. These improvements aim to increase network reliability, make node interactions more efficient, enhance overall system performance, and maintainability.
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:
Mainsail - https://github.com/ArkEcosystem/mainsail/issuesARK Connect (Extension) - https://github.com/ArdentHQ/arkconnect-extension/issuesARK Connect (Demo) - https://github.com/ArdentHQ/arkconnect-demo/issuesARK Scan - https://github.com/ArdentHQ/arkscan/issuesARK Vault - https://github.com/ArdentHQ/arkvault/issues
Follow on Twitter (X)
Follow us on X  (https://x.com/ArkEcosystem) 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.

$ARK

Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, the ARK Scan team continued focusing on performance enhancements and progressing with the Inertia migration, while the ARK Vault team worked on HD wallet improvements and further development of the Side Panel minimization feature. Meanwhile, the Mainsail team made steady progress on improving test coverage, cleaning up several packages, and updating dependencies.
Development Activity Summary (October 3 – October 10, 2025)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from October 3, 2025, to October 10, 2025.

During this period, the team maintained strong productivity and engagement, delivering 70 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 have continued working on performance improvements and the Inertia migration. Work done included:
Migrated the wallet page header to Inertia, improving frontend integration, page load performance, and navigation consistency.Added an Inertia-based address QR code modal, allowing users to easily view and access their address QR code directly within the interface.
Next week, we’ll continue optimizing ARK Scan and address any reported issues.
ARK Vault Weekly Report
This week, we have been working on HD Wallet improvements and further developing the Side Panel minimization feature. Work done included:
Added support for multiple HD Wallets under a single profile, allowing users to import additional addresses or add to existing ones. The import flow now adapts dynamically based on existing HD Wallets and differentiates between “Encrypted Password” and “Mnemonic” types.Introduced a minimize action in the side panel, streamlining the action flow and merging core functionalities to avoid potential future conflicts.Enhanced the side panel to handle new flows when one is already pending, prompting users to either discard the existing minimized flow or start a new one. Options to continue, cancel, or suppress future prompts ensure proper data management.Updated the side panel to prevent minimizing during the “completed” step, ensuring that once a flow finishes, clicking outside doesn’t collapse it, and stored data is cleared correctly.Fixed an edge case where the side panel could reappear incorrectly after deleting and importing an address while minimized, maintaining consistent behavior with the new minimization logic.Updated the Exchanges page so that clicking on a transaction reopens the side panel, letting users view exchange status without losing context and resolving an issue that previously triggered profile sign-out.Corrected fee input fields to display a maximum of eight decimal places, ensuring precise and consistent fee entry.Fixed truncation issues for addresses and account names in HD Wallet creation, aligning names and details properly on mobile screens.Resolved an alias issue in the create address flow so the default address name correctly appears as Address #1 instead of the address itself, restoring proper name editing and completion behavior.Added test coverage for the lib module to validate previously untested functionality.Fixed failing tests in the exchange domain, confirming that all exchange-related operations function correctly.
Next week, we’ll continue addressing any issues with HD Wallets and Side Panel minimization, begin work on the Ledger migration functionality, and fix any newly reported issues.
Mainsail Weekly Report
This week, we continued improving test coverage, cleaned up several packages, and updated dependencies. Work done included:
Merged the crypto-transaction-evm-call package into crypto-transaction, simplifying structure and maintenance.Refactored and cleaned up schema handling within the crypto-transaction package for improved clarity and consistency.Updated EVM-related dependencies to the latest stable versions.Updated Docker images and installation scripts to use PostgreSQL 18.Ensured that all zero-balance accounts are correctly imported from snapshots into EVM storage.Increased unit test coverage across the crypto-transaction and database packages.
Next week we will continue focusing on unit test development to further increase coverage, perform additional refactoring, and address the latest reported bugs.
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:
Mainsail - https://github.com/ArkEcosystem/mainsail/issuesARK Connect (Extension) - https://github.com/ArdentHQ/arkconnect-extension/issuesARK Connect (Demo) - https://github.com/ArdentHQ/arkconnect-demo/issuesARK Scan - https://github.com/ArdentHQ/arkscan/issuesARK Vault - https://github.com/ArdentHQ/arkvault/issues
Follow on Twitter (X)
Follow us on X  (https://x.com/ArkEcosystem) 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.
$ARK

Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, the documentation site was updated with improvements to the Receipts API endpoint. At the same time, the ARK Vault team focused on finalizing the HD wallet feature, refining the Side Panel, and addressing various fixes. Meanwhile, we made further progress on optimizations and improvements to the overall Mainsail process.
Development Activity Summary (September 26 – October 3, 2025)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from September 26, 2025, to October 3, 2025.

During this period, the team maintained strong productivity and engagement, delivering 122 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 SDKs & Docs Weekly Report
This week, we rolled out updates to the Receipts API endpoint in our documentation. The changes include the latest improvements and new additions to make it easier for developers to retrieve and track receipts.
Looking ahead to next week, we’ll continue enhancing our documentation to keep it fully aligned with the latest updates.
ARK Vault Weekly Report
This week, we have been finalizing the HD wallet feature that will be a new addition to Vault, as well as working on further improvements to the Side Panel and addressing other fixes. Work done includes:
Adjusted the HD wallet import flow to import addresses sequentially, ensuring default names follow the same order as on the import page. This prevents mismatched naming and avoids confusion when Vault defaults to showing the first imported address.Enabled HD wallets by default in development environments, removing the need to manually toggle the setting on each new deployment. This streamlines testing and speeds up development while keeping production environments unaffected.Moved the exchange flow to the side panel, aligning it with other transaction flows. Error handling now follows the same pattern as the transaction flow to prevent accidental closures or invalid inputs.Improved the HD wallet import flow to scan the first five addresses automatically and display them immediately when importing. Depending on whether addresses have funds, the display adjusts to show only relevant addresses while keeping order logical.Added support for minimizing flows in the side panel, showing minimized actions at the bottom of the screen. A one-time tooltip explains the feature, and a smooth transition enhances the user experience.Fixed the Ledger send flow so that if a transaction is declined on the device and the user clicks “Back” in the Vault UI, the app safely returns to the previous form instead of crashing with a hash error.Moved the periodic fetching of unconfirmed transactions from a component interval to the profile job handler, preventing redundant API requests and ensuring consistent updates.Updated the Ledger import flow to reject non-ETH-based apps, preventing users from importing addresses with the old ARK Core app and ensuring only the correct Mainsail ETH Ledger app is used.Updated the wallet creation flow so encryption is set after the address is imported, preventing the encryption configuration from being overwritten and allowing transactions to request the encryption password instead of the mnemonic when needed.Fixed the HD wallet create flow to reset the mnemonic state when navigating back, preventing the “Loading Addresses” loop and ensuring address generation restarts properly.Changed the HD wallet creation flow so that clicking “load more addresses” adds only one new address at a time, keeping creation simple while imports remain flexible for recovering multiple addresses.Enhanced the navigation bar to highlight the current page using an isActive prop on menu items, with new logic and styles applied for clear visual feedback.Limited account names for HD wallets to 15 characters to prevent UI issues, with truncation applied when names exceed available space.Disabled the “Send” button in all transaction sidepanel forms until required validation is complete, preventing premature submissions.Added a “Select Account” step to the import flow for existing encrypted HD wallets. Users can choose to add to an existing wallet or import a new one, with entries labeled by type. Selecting an existing wallet prompts the correct input to continue.Fixed the HD wallet import flow so mnemonic state resets properly when exiting. Cancelling and restarting now clears the old mnemonic, ensuring new mnemonics generate the correct addresses.
Next week, we’ll continue to improve and finalize the HD wallet feature, as well as begin more thorough testing. We’ll also focus on extending Ledger hardware support and addressing any reported issues.
Mainsail Weekly Report
This week, we made further progress on optimizations and improvements to the overall Mainsail process. The work completed included:
Deferred database index creation until after the restore is completed.Added a maintenance mode to the API during restore.Ensured all zero-balance accounts were imported from the snapshot into EVM storage.Made the boot and reboot function interfaces asynchronous.Changed the transaction pool query parameter from id to hash.Enforced a stricter transaction schema.Removed the timestamp field from the TransactionJson interface.Removed deprecated version fields from docker-compose.yml files and Docker templates.Improved the performance of clear scripts.
Next week, we will continue adding unit tests, refactoring for further optimizations, and making additional improvements to database performance and 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:
Mainsail - https://github.com/ArkEcosystem/mainsail/issuesARK Connect (Extension) - https://github.com/ArdentHQ/arkconnect-extension/issuesARK Connect (Demo) - https://github.com/ArdentHQ/arkconnect-demo/issuesARK Scan - https://github.com/ArdentHQ/arkscan/issuesARK Vault - https://github.com/ArdentHQ/arkvault/issues
Follow on Twitter (X)
Follow us on X  (https://x.com/ArkEcosystem) 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.
$ARK

Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, the ARK Scan team fixed validator status issues and enhanced deeplinks support, while the ARK Vault team continued developing pending transactions and HD wallet features alongside general fixes and app improvements. Meanwhile, the Mainsail team released a new version of the public testnet and carried on refining other areas of the Mainsail.
Development Activity Summary (September 19 – September 26, 2025)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from September 19, 2025, to September 26, 2025.

During this period, the team maintained strong productivity and engagement, delivering 115 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
The ARK Scan team focused on fixing validator status issues and improving deeplinks. Specifically:
Validators without a BLS key now correctly show as dormant, instead of incorrectly appearing as active. Active/standby/dormant states are now consistently reflected on the address details page.The deeplink for voting has been updated to always use publicKey=<publicKey> instead of validator=<username>. This ensures compatibility even when a validator has no username registered, simplifying handling and guaranteeing valid URIs.Dusk tests were set up, and the missed warning was fixed. This ensures that testing works correctly with Inertia since React generates pages via the DOM, and allows the monitor PR tests to be included in workflows.
Next week, we’ll continue enhancing tests, improving overall performance, and addressing any reported issues.
ARK Vault Weekly Report
This week, we continued developing the pending transactions and HD wallets features, along with general fixes and app improvements. Completed work includes:
Pending transactions are now fetched from the /transactions/unconfirmed endpoint using the pending-transactions.service. A new Pending Transactions DTO was added to handle transaction types and properties, and query parameters for filtering by recipient and sender have been implemented.The HD wallet option was added to the wallet creation flow, including logic to show or hide it as appropriate.A general HD wallet creation flow was added, ensuring users can create HD wallets similarly to the regular address creation process. This provides a consistent and complete workflow for HD wallet management.The TimeAgo component for pending transactions was fixed to update correctly, ensuring that each row’s “Time Ago” column reflects the current elapsed time even when no new transactions are added.Account name functionality was added for HD wallets during the import flow, allowing users to assign and view names for imported HD wallet accounts.The create wallet flow was updated to prevent app crashes when exiting from the mnemonic generation step, fixing a TypeError caused by accessing undefined properties.The HD wallet flow was updated to display a message guiding users to use the import option when adding additional addresses.The periodic fetching of unconfirmed transactions was moved from the component to the profile job handler. This reduces multiple API requests caused by component re-renders and ensures consistent caching and handling of unconfirmed transactions across the portfolio page.Transaction signing for HD wallets was extended to support the encryption password option, allowing secure signing for encrypted HD wallet addresses.HD wallet addresses in the portfolio are now highlighted with a dedicated label, displayed in both mobile and desktop views, as well as in the side panel. Label styles were refactored, adding outline, primary, and neutral variants for consistent presentation.The side panels for validator and username resignations were updated to match the latest designs, including a modern variation for the wallet selector. New unit tests were added to ensure these changes don’t break existing implementations.All instances of “wallet” in the UI have been replaced with “address,” and corresponding translation keys and content were updated. Unused translations were removed, and implementations, unit tests, and snapshots were updated to ensure consistency across the codebase.The address alias generation for HD wallets was corrected to use the proper index, ensuring aliases now reflect Address #counter rather than incorrectly showing Address #counter+1. This provides accurate and consistent labeling for generated addresses.HD wallet-related classes, methods, files, and variables were renamed to follow BIP-44 naming conventions, improving clarity and consistency across the codebase.The profile transactions view was optimized to prevent multiple unnecessary renders, improving performance and ensuring smoother updates when transaction data changes.Link styling was removed from the address row on the vote page, improving visual consistency and reducing confusion by making the row appear as standard text rather than a clickable link.
Next week, we’ll keep progressing on the HD Wallet implementation, enhance Ledger hardware support, and address any other reported issues.
Mainsail Weekly Report
This week, we released a new version of Mainsail EVM v0.0.1-rc.6 for the public testnet. This update includes several improvements and changes:
The transaction pool API now supports filtering by the from and to fields.Networking now includes NTP time offset logging for better synchronization visibility.Consensus logs have been updated with a new format that displays height, round, and hash.The lint.sh script has been removed.A new db:drop command has been added to the API.Syncing now uses less memory, improving overall efficiency.Consensus log formatting has been improved to use toLocaleString. Outputs are using English format (en-US).
We have also continued improving other aspects of Mainsail. Work done this week includes:
Added support for re-processing downloaded blocks in consensus. This resolves edge cases in block processing not caused directly by consensus failures but by invalid node time settings. When node clocks are unsynchronized, a block may be rejected because it appears to come from the future. Such blocks are now reprocessed and accepted later.Enabled NTP sync by default in the install.sh script.Introduced getCommitBytes, using a single database call in the EVM package to improve performance.Restored functional consensus tests and enabled GitHub workflows for those tests.Extended the network generator to produce tests for functional consensus.Added support to read usernames from snapshots during database restore.
Next week, we’ll focus on improving unit testing and increasing coverage.
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:
Mainsail - https://github.com/ArkEcosystem/mainsail/issuesARK Connect (Extension) - https://github.com/ArdentHQ/arkconnect-extension/issuesARK Connect (Demo) - https://github.com/ArdentHQ/arkconnect-demo/issuesARK Scan - https://github.com/ArdentHQ/arkscan/issuesARK Vault - https://github.com/ArdentHQ/arkvault/issues
Follow on Twitter (X)
Follow us on X  (https://x.com/ArkEcosystem) 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.
$ARK

Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, the ARK Scan team concentrated on further optimizing performance, while the ARK Vault team continued development on the HD Wallet import feature alongside general cleanup and improvements to Ledger flows. Meanwhile, the Mainsail team focused on API enhancements and refining the installation script to improve the installation process.
Development Activity Summary (September 12 – September 19, 2025)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from September 12, 2025, to September 19, 2025.

During this period, the team maintained strong productivity and engagement, delivering 112 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, our efforts were focused on further optimizing Scan’s performance. Key accomplishments included:
Updated multipayment queries to use the new multi_payment_recipients column, enabling more efficient lookups with @> ARRAY[?]::citext[]. This ensures recipient searches work correctly and improves query performance.Adjusted validator monitor timing logic to handle extra forgers correctly within a round. This prevents unnecessary 8-second offsets, ensuring times no longer drift into the future and validators in their slot display accurate timing.Improved validator monitor logic to correctly display “now” when a validator is in their slot. Missed blocks are updated earlier so the next validator immediately shows as current, and countdowns now stay aligned with validator states for accurate real-time updates.
Looking ahead to next week, we will continue enhancing Scan’s performance while also addressing any reported issues.
ARK Vault Weekly Report
This week, we continued development on the HD Wallet import feature and carried out general cleanup and improvements to the Ledger flows. Specifically:
Refactored transaction error handling to use the new status API attribute instead of local decoding. Errors are now displayed directly from the API in a human-friendly format, with improved readability and consistency. Fallback logic still checks for potential out-of-gas cases, ensuring clearer failure reasons in transaction details.Updated sidepanel behavior to prevent closing when input is active. Also fixed an issue where pressing “Esc” in a modal would inadvertently close the sidepanel, ensuring modals and sidepanels now operate independently.Updated Ledger transaction messaging to avoid confusion with network confirmations. Pending Ledger transactions now display as “This transaction is pending approval on your Ledger device.” ensuring clarity that the approval is required on the device, not from the network.Fixed gas limit estimation by correcting the estimate call and ensuring the fallback properly accounts for multiple recipients instead of always defaulting to 21k. This update ensures accurate gas estimation across all transaction types.Added HD wallet option to the import flow, including logic to show or hide the entry in the import list. This enables users to import HD wallets directly alongside other supported methods.Added deeplink handling for vote transactions and removed the old legacy vote page. This streamlines navigation by opening the vote sidepanel directly from a deeplink while cleaning up unused legacy components.Enabled multipayments for Ledger wallets by updating the contract call logic, allowing transactions with multiple recipients. Tested recipient limits on the Ethereum Ledger app to ensure reliability, and added UI constraints if necessary to prevent exceeding supported transaction sizes.Removed outdated avatars from the Ledger vote pending UI, leaving only the background. Also checked other Ledger-related areas to ensure no similar leftover visuals remain.Updated the vote flow and related pages to display the validator’s name when available, falling back to the address only if no name is set. Implemented a general Address component to handle this consistently across pending transactions, vote creation, and other relevant areas.Removed all legacy transaction pages, consolidating transaction flows into the modern sidepanel implementation for a cleaner and more consistent user experience.
Next week, we will maintain our focus on advancing the HD Wallet import feature, while also addressing reported issues and making further progress on Side Panel optimizations.
Mainsail Weekly Report
This week, we focused on API enhancements and installation script improvements. Completed work includes:
Updated log structure to use height/round/block_hash.In special cases (when a block is reproposed), the format is height/consensus_round(block_round)/block_hash.Removed unused lint.sh scripts.Added drop:db command with support for additional flags:--force to skip confirmation--init to initialize the databaseRefactored the api-sync package to improve memory usage.
Next week, we will focus on consensus improvements and fixing edge cases. We will also restore the consensus tests and release updates for the public testnet.
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:
Mainsail - https://github.com/ArkEcosystem/mainsail/issuesARK Connect (Extension) - https://github.com/ArdentHQ/arkconnect-extension/issuesARK Connect (Demo) - https://github.com/ArdentHQ/arkconnect-demo/issuesARK Scan - https://github.com/ArdentHQ/arkscan/issuesARK Vault - https://github.com/ArdentHQ/arkvault/issues
Follow on Twitter (X)
Follow us on X  (https://x.com/ArkEcosystem) 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.
$ARK

Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, the ARK Scan team delivered additional fixes and updates for Mainsail alongside several design improvements, while the TypeScript Client SDK received a fix for handling pending transactions through the API. The ARK Vault team focused on introducing HD wallet address derivation, complemented by design updates and multiple fixes. Meanwhile, the Mainsail team released two new testnet versions packed with new features, improvements, and performance upgrades, while continuing to refine and enhance the overall Mainsail experience.
Development Activity Summary (September 5 – September 12, 2025)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from September 5, 2025, to September 12, 2025.

During this period, the team maintained strong productivity and engagement, delivering 150 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 focused on additional fixes and updates for Mainsail, along with several design improvements:
Fixed the QR modal in transaction details so it no longer closes immediately when opened. Also removed the memo field and updated the amount input layout to match Vault’s input design with the label above the field.Updated dropdown styling to align with the new design, adding visual consistency and an icon to indicate the selected option.Fixed the validators page error by properly handling the “Dormant” filter in the Select All action, ensuring it works consistently across all validator tabs.Fixed validator links in the monitor so they now open in the full page view instead of rendering inside a smaller window.Updated transaction table to display the unlocked amount when a Validator Resignation transaction occurs. This makes the display consistent with Validator Registration, where the locked amount is shown.Adjusted modal styling so that only the top and bottom sections update visually, while the main content remains consistent.Implemented unified translation handling so Blade, Livewire, and Inertia components all share the same translation strings. This was achieved using laravel-react-i18n for PHP to JSON conversion and react-i18next for frontend translations, ensuring consistency across the entire stack.Adjusted controller tests for BlockController and ExchangeController by disabling exception handling, ensuring more verbose error messages are shown during failures.Added Inertia page metadata support by introducing a layout header variant without static title/meta tags. This enables dynamic head information to be set from app-inertia.tsx, replacing the previous generic title and allowing proper per-page metadata handling.Fixed an intermittent test failure in missed blocks by ensuring stable sorting with cached data. The test now uses a forced time value to avoid unpredictable behavior across datasets like votes.
Next week, we’ll continue addressing reported issues and further improve Mainsail integration.
ARK SDKs and Documentation Weekly Report
This week, we fixed support for handling pending transactions for the transactions/unconfirmed API in the TypeScript Client SDK. With this change, unconfirmed transactions can now be fetched directly from the API and displayed in Vault as pending until they are confirmed.
Next week, we’ll continue to address reported issues and further improve documentation and SDKs as needed.
ARK Vault Weekly Report
This week, we focused on the new HD wallet address derivation feature, along with design improvements and multiple fixes. Work completed includes:
Implemented HD wallet address derivation using viem, enabling generation and import of addresses based on coin, account, chain, and address index. Added unit tests to validate the new logic.Added transaction signing support for HD wallets and updated the Send Transfer flow, allowing users to securely sign transactions with derived HD addresses.Introduced an HD wallet toggle on the Settings page, giving users control to enable or disable HD wallet functionality.Fixed contract-based transactions for Ledger wallets, ensuring vote and registration calls (username/validator) work correctly. Validated proper chain ID and contract data handling, resolving errors and ensuring correct Ledger app prompts.Added deeplink handling to the Send Transfer sidepanel, allowing transactions to be initiated via direct links. Removed the legacy send transfer page to unify the flow within the sidepanel.Enhanced the transaction sidepanel with gas details by including gasUsed and gasLimit for both signed and confirmed transactions. Introduced a TransactionGas component with dim and dark mode support, updated translations, and added unit tests.Improved pending transaction handling by refactoring how unconfirmed transactions are fetched and displayed.Simplified wallet selection logic in the Address Selection sidepanel to ensure the correct address is highlighted when switching, fixing inconsistencies with the “Viewing [Address]” display.Updated the sign message flow by removing the legacy sign page and adding deeplink support in the sidepanel, enabling messages to be signed directly via deeplinks.Moved the validator resignation flow into the sidepanel, aligning it with other transaction types for a consistent user experience and reusable logic.
Next week, we’ll continue implementing HD wallet integration, refine designs to match recent updates, and address any reported issues.
Mainsail Weekly Report
This week, we released Mainsail EVM v0.0.1-rc.4 and v0.0.1-rc.5, bringing several new features, improvements, and performance upgrades. Highlights include enhanced transaction filtering and multi-payment support, better error decoding, and performance boosts for crypto operations. We also applied important fixes to transaction pool handling, tightened validation, and streamlined our API and database structure. Additionally, setup and developer experience got a lift with updated dependencies, TypeScript ES2023 target, and BLS key support in Docker.
The full list of changes is available in the release notes for v0.0.1-rc4  and v0.0.1-rc5 .
This week, we have also continued making progress on various aspects of Mainsail. Updates include:
Added multi_payment_recipients column to transactions, enabling approved multi-payment queries.Implemented support for filtering transactions by address, allowing queries to match either the from or to field.Performed an NTP (Network Time Protocol) check and logged the time offset.
Next week, we’ll focus on further API improvements, as well as enhancements to consensus mechanisms and handling of edge cases.
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:
Mainsail - https://github.com/ArkEcosystem/mainsail/issuesARK Connect (Extension) - https://github.com/ArdentHQ/arkconnect-extension/issuesARK Connect (Demo) - https://github.com/ArdentHQ/arkconnect-demo/issuesARK Scan - https://github.com/ArdentHQ/arkscan/issuesARK Vault - https://github.com/ArdentHQ/arkvault/issues
Follow on Twitter (X)
Follow us on X  (https://x.com/ArkEcosystem) 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.
$ARK

Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, the ARK Scan team improved failed transaction feedback to make errors clearer and more actionable, while also integrating Simple Analytics for better insights. The ARK Vault team enhanced the side panel by integrating additional flows and delivered improvements to Ledger support. Meanwhile, the Mainsail team concentrated on bug fixes and continued refining the API with further enhancements.
Development Activity Summary (August 29 – September 5, 2025)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from August 29, 2025, to September 5, 2025.

During this period, the team maintained strong productivity and engagement, delivering 107 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 improved the feedback on failed transactions to make errors clearer and more actionable, and we also integrated Simple Analytics. Work done included:
Updated queries to reflect the removal of the receipts table, now using the corresponding column directly in the transactions table instead.Updated transaction details to use the new decodedError column for failed transactions instead of decoding receipts manually. Errors are now displayed in a more readable format. If the error is execution reverted, an additional gas usage check is performed: near-limit cases show “Out of gas”, while others display the general “Error encountered during contract execution” message.Integrated Simple Analytics to track visitor counts and page popularity on Scan. Added event tracking for key interactions such as exports, legacy addresses, and other modals. Tracking is limited to generic usage data only, ensuring no user-specific data is collected.
Next week, we’ll continue improving overall performance and address any reported issues.
ARK Vault Weekly Report
This week, we focused on improving the side panel by integrating more flows into it, along with enhancements to the Ledger. Work done included:
Improved transaction handling for Ledger accounts by detecting when the device is not connected or the Mainsail app is not open. Instead of failing immediately, the user is now prompted within the transaction flow to resolve the issue. This ensures smoother UX and prevents unnecessary transaction errors.Fixed an issue where the transaction table displayed data from the wrong address after importing a Ledger account. The table now correctly syncs with the selected Ledger profile, and refreshing no longer removes the imported Ledger address. This ensures accurate transaction history and consistent profile behavior.Corrected the header colors for the Select Sender and Select Recipient modals.Fixed multipayment transaction classification when the sender is also a recipient, preventing all recipients from being labeled as “Return.” Now only the sender’s own line is treated as a return (if applicable), while other recipients correctly show as incoming with the proper received amount.Moved the Vote/Unvote flow from pages to the side panel, aligning it with the updated transaction flow design. This makes the experience consistent with other transactions, improves usability, and allows for better reuse of side panel logic.Updated voting logic so that vote swaps are now handled as a single vote transaction rather than including both unvotes and votes. This prevents double-signing prompts on Ledger wallets and simplifies the flow by only including the new voting address.Added “Back” and “Retry” buttons to the Ledger import error page, allowing users to retry or navigate back when an error occurs. The handleRetry method was refactored to support different retry logic based on the Ledger step, improving error recovery and user experience.Implemented profile import migration to convert existing .wwe files for compatibility with the Mainsail version of Vault.Added a FeeService to the Network for streamlined fee handling via network.fees(). Also moved the transaction ABI encoder into a standalone TransactionEncoder class for better encapsulation and reuse in gas estimations.Refactored username and validator transactions by moving registration, resignation, and update flows into the side panel, unifying the transaction experience.Updated the Devnet manifest configuration to use the correct nethash value, ensuring proper network identification and connectivity.
Next week, we’ll continue refining the side panel, begin work on new features coming into Vault, and address any issues that arise.
Mainsail Weekly Report
This week, our focus was on bug fixes and continued API enhancements. The work completed includes:
Updated node sync status determination to use the median (90th percentile).Added pagination support for the /unconfirmed endpoint in the transaction pool API.Strengthened RLP validation to prevent adding extra fields or bytes to serialized transactions.Improved transaction pool handling by resetting sender state when no transactions remain after a block commit.Fixed the Mainsail update process by adding support for the --allow-build flag, enabling automatic execution of post-install build scripts for packages that need rebuilding after version changes.
Next week, we will focus on preparing a new version for the public testnet that incorporates all recent updates. We will also continue expanding test coverage and implementing further API improvements.
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:
Mainsail - https://github.com/ArkEcosystem/mainsail/issuesARK Connect (Extension) - https://github.com/ArdentHQ/arkconnect-extension/issuesARK Connect (Demo) - https://github.com/ArdentHQ/arkconnect-demo/issuesARK Scan - https://github.com/ArdentHQ/arkscan/issuesARK Vault - https://github.com/ArdentHQ/arkvault/issues
Follow on Twitter (X)
Follow us on X  (https://x.com/ArkEcosystem) 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.
$ARK

Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, the ARK Scan team concentrated on boosting loading performance and fixing several issues, while on the SDK side, efforts were directed toward improvements in the TypeScript SDK package. The ARK Vault team worked on adding new features to the side panel and enhancing the user experience with clearer error displays for failed transactions. Meanwhile, the Mainsail team focused on strengthening the database and API through a series of targeted improvements.
Development Activity Summary (August 22 – August 29, 2025)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from August 22, 2025, to August 29, 2025.

During this period, the team maintained strong productivity and engagement, delivering 118 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, our efforts were centered on improving loading performance and resolving several issues. Completed work included:
Refactored the validator monitor to improve initial load performance by optimizing data handling and deferring slower metrics where possible. Also fixed inconsistent column widths by enforcing fixed-width alignment across both monitor tables, ensuring proper layout even with overflow validators.Fixed block export by updating the height attribute to use a number type as per the API changes, and updated default API endpoints to point to the public testnet version.Fixed the multipayment transaction detail page by ensuring a valid model or address is provided, preventing errors when viewing multipayment details.
Next week, we will continue working on performance improvements in Scan to achieve faster load times and address any reported problems.
ARK SDKs and Docs Site Weekly Report
This week, we focused on enhancements to the TypeScript SDK package. We introduced ABI error decoding and added query parameter support for transaction calls.
Next week, we will continue refining the SDKs based on feedback from developers integrating them into ARK’s products and update documentation as needed.
ARK Vault Weekly Report
This week, we focused on adding new features to the side panel and improving the user experience when displaying errors for failed transactions, along with several other enhancements. Work completed included:
Refactored transfer and multipayment flows to run inside the side panel, consolidating common items like fees and logic for reuse across transaction types. Added safeguards to disable outside-click closing once the transaction flow has started, showing an error if attempted. Users can now only close the side panel via the X icon, with clear highlighting to indicate that data is present and protected from accidental closure.Hid the subtitle prompting for a secret when sending transactions with a Ledger address, as it’s not required for Ledger users.Added human-readable error messages to the transaction details side panel, displaying contract-provided failure reasons.Added a tooltip to the method label in transaction rows that appears when the text is truncated.Updated multipayment transactions in advanced mode to use the estimated gas limit, increasing default advanced fees to prevent transaction failures.Adjusted the transactions table UI by resizing columns to prevent overlap, reducing method column width on 768px view, preventing timestamp wrapping, and expanding transaction ID badges for pending/error states. Updated copy button positioning and test snapshots to reflect these changes.Fixed transaction sending for Ledger hardware wallets by resolving the unknown configuration value error.Updated the import flow so that the mnemonic input “Need Help” hint is expanded by default instead of being collapsed.
Next week, we will continue improving the side panel, begin developing new features, and work on general advancements to the app.
Mainsail Weekly Report
This week, we focused on database and API improvements. Completed work includes:
Merged transactions and receipts Postgres tables into a single transactions table to reduce disk usage and improve performance.Added decoded errors into the transactions table (supports basic EVM errors and custom errors on default Mainsail contracts).Implemented returning 503 HTTP status code during database restore to indicate that the database is not yet ready for the public API.Updated EVM dependencies.Increased unit test coverage for the CLI package.
Next week, we will work on increasing test coverage, further API improvements, and fixing Mainsail updates for PNPM updates.
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:
Mainsail - https://github.com/ArkEcosystem/mainsail/issuesARK Connect (Extension) - https://github.com/ArdentHQ/arkconnect-extension/issuesARK Connect (Demo) - https://github.com/ArdentHQ/arkconnect-demo/issues ARK Scan - https://github.com/ArdentHQ/arkscan/issuesARK Vault - https://github.com/ArdentHQ/arkvault/issues
Follow on Twitter (X)
Follow us on X  (https://x.com/ArkEcosystem) 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.
$ARK

Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, the ARK Scan team focused on enhancing multipayment functionality, improving performance, and updating design elements, while the ARK Vault team delivered a mix of general fixes and new features. Meanwhile, the Mainsail team concentrated on optimizing multipayment handling and block processing to further strengthen overall performance.
Development Activity Summary (August 15 – August 22, 2025)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from August 15, 2025, to August 22, 2025.

During this period, the team maintained strong productivity and engagement, delivering 122 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, our efforts were concentrated on enhancing multipayment functionality, optimizing performance, and updating design elements. Key tasks completed included:
Refactored wallet transaction processing to bypass multipayment-specific logic when multipayments are not present, boosting performance and reducing unnecessary queries that previously slowed down the transaction page.Improved transaction handling by querying the multipayment recipients table directly, eliminating extra queries and speeding up transaction page load times.Updated the “Copy” icon color to grey to align with ARK Vault styling.Adjusted the light mode badge so the From and To text now uses gray-700.Refined the “No results” message with better line height and added spacing between placeholder text, enhancing readability and creating a cleaner layout.Updated the Contract badge styling to match the Unvote tag, featuring a grey background and border.Revised filtering logic so “Validator Update” transactions now appear under the Validator filter instead of Other, ensuring accurate categorization and clarity when filtering.Enhanced the validator-monitor page with Inertia implementation and optimizations to lower resource usage, improving overall performance.Formatted the transaction count on the /transactions page to use standard number formatting (e.g., 183,853) for improved readability and consistency across the app.
Next week, we plan to continue refining design elements and implementing additional optimizations to achieve faster loading times.
ARK Vault Weekly Report
This week, we worked on general fixes as well as new features. Work completed includes:
Implemented design updates for the Select Sender modal, ensuring it matches the latest specifications. The component now shows fiat amounts only on mainnet and applies the updated styling across all reused instances, including the Receive flow.Implemented caching for notifications by storing fetched notification transactions in local storage, keyed by profile ID to avoid mixing data. Cached notifications are now shown instantly on reloads or errors, and updated when new transactions are fetched. Unit tests were updated to cover this behavior.Implemented handling for insufficient gas errors in transactions by checking if no other error is present and if the gas used is within ~95% of the set gas limit. When detected, Vault now shows “insufficient gas” as the failure reason in transaction details, mirroring ARK Scan’s approach.Moved transaction details from the modal to the side panel, so clicking a transaction in the table now opens its details in the side panel for a more consistent user experience.Implemented design updates for the Select Recipient modal on mobile, aligning it with the latest specifications and ensuring consistency with the updated Select Sender flow.Updated notification logic to support multiple addresses, enabling notifications to be fetched and displayed across all tracked addresses.Applied minor UI adjustments to the Select Sender modal: made the entire row clickable, updated tooltips, and fixed hover and selected row colors.Improved multi-address view by automatically switching to single view when only one address remains, replacing the “Multiple Addresses (1)” display.Implemented Mainsail profile migration for settings, converting imported settings to the new format during profile import.Fixed wallet alias consistency by ensuring address names display uniformly in the recipient search modal for transactions, with updated unit tests to cover this behavior.Fixed transaction status handling in transaction details to properly reflect failed transactions. Pending transactions now update to show contract failures immediately instead of displaying incorrect confirmations, without requiring a page refresh.Implemented Mainsail profile migration for contacts by converting them to the new format during import.Modified Address Name behavior on mobile by adding a top offset to the edit modal and opening it in the sidebar as an additional screen, preventing accidental closure of sidebar.
Next week, we’ll continue improving Mainsail integration and work on further design updates to enhance user experience.
Mainsail Weekly Report
This week, we worked on multipayment and block processing optimizations. Key work included:
Updated package dependencies to the latest versions.Upgraded TypeScript and set the target to ES2023.Synced multipayments to the Postgres database.Improved block processing performance by using Node workers to parallelize transaction deserialization.Reran tests on the main and develop branches after merges to publish Codecov reports.Increased unit test coverage for blockchain-utils.
Next week, our focus will be on further improving test coverage and implementing API enhancements based on feedback from the Vault and Scan teams.
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:
Mainsail - https://github.com/ArkEcosystem/mainsail/issuesARK Connect (Extension) - https://github.com/ArdentHQ/arkconnect-extension/issuesARK Connect (Demo) - https://github.com/ArdentHQ/arkconnect-demo/issuesARK Scan - https://github.com/ArdentHQ/arkscan/issuesARK Vault - https://github.com/ArdentHQ/arkvault/issues
Follow on Twitter (X)
Follow us on X  (https://x.com/ArkEcosystem) 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.
$ARK

Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, in ARK Connect, we removed the unused ‘memo’ field from extension pages and components to align with Mainsail changes, while the ARK Scan team streamlined the app by consolidating multiple tabbed components into a single, more efficient structure. On the documentation side, we focused on improving clarity and accuracy. The ARK Vault team introduced new features such as pending transactions, along with general design updates and fixes. Meanwhile, the Mainsail team refined the API based on feedback and implemented performance improvements to further optimize the platform.
Development Activity Summary (August 8 – August 15, 2025)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from August 8, 2025, to August 15, 2025.

During this period, the team maintained strong productivity and engagement, delivering 79 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
This week, we removed the memo field from extension pages and components, as it is no longer used in Mainsail.
Next week, we will continue addressing Mainsail changes and resolving any issues reported by our internal team.
ARK Scan Weekly Report
This week, we refactored parts of the app by consolidating multiple tabbed components into a single component.
We also updated app/Http/Livewire/Validators/Tabs.php to handle filters, fixing navigation errors when using the browser’s back button. We are also working on an Inertia implementation of the Validator Monitor to reduce its resource requirement over prolonged use.
Additionally, we merged mainsail-develop into the mainsail branch.
Next week, we will keep working on reported issues and continue optimizing for faster loading times and lower resource usage.
ARK SDKs & Docs Weekly Report
This week, we focused on improving the clarity and accuracy of our documentation. Specifically, we updated the example for configuring the validator public key, ensuring that developers have a more precise and easy-to-follow reference.
These changes aim to reduce setup confusion and help both new and experienced developers implement the configuration correctly.
Next week, we will continue addressing any issues reported by the community. In addition, we plan to further enhance the Mainsail documentation by adding more detailed explanations, refining existing examples, and expanding general documentation.
ARK Vault Weekly Report
This week, we have worked on introducing new features like pending transactions as well as general design updates and fixes. Work done included:
Added support for pending transactions with a new hourglass icon, adjusted transaction ID layout, created a use-pending-transactions hook for local storage management, and refactored use-profile-transactions to merge pending and confirmed transactions. All transaction forms now store newly created transactions in local storage until confirmed.Aligned detail titles in review steps for consistent text placement across pages.Updated the wallet label in the import success step to display the correct wallet name.Refactored the Votes table to show a tooltip when wallet balance is 0 and updated AddressRowMobile to disable the Vote button when Ledger is unsupported, matching AddressRow behavior.Fixed the image shake on the Ledger connection step by hiding the scrollbar and ensuring the section takes full height.Added the missing illustration for the Ledger import step in dim mode.Adjusted multipayment display to show “Multiple (1)” for a single recipient, linking to the explorer for consistency.Introduced tooltips for buttons disabled due to 0 balance with consistent text: “Disabled due to insufficient balance,” including vote transactions.Restored default password input behavior for the mnemonic field by rolling back previous custom input changes.Refactored API interactions to route all HTTP requests through centralized library services, improving maintainability and consistency.Corrected alignment of delete address buttons in the addresses side panel.Updated the UpdateWalletName modal to match the latest designs, replacing “Wallet Name” with “Address Name” and ensuring proper layout across breakpoints.Removed the JSON profile import feature along with all related tests, fixtures, and supporting code.Added padding in the “Remove Password” section of Settings for better visual alignment.Refined profile job handling to run synchronizers only for the active profile.Enabled browser “Back” button support for sidepanels; step-based sidepanels like ImportAddressSidepanel now handle actions based on the current step using onBack and hasSteps props.Implemented Mainsail profile migration for wallets, converting old addresses to the new format during import.Fixed table filtering logic so the “other” filter correctly includes all transaction types not covered by other options.Refined mobile navigation to hide the bottom bar on transaction flow screens.Adjusted wallet deletion alert on mobile to remove extra white space under the message.Updated semantic HTML on the Welcome page and introduced StyledRouterLink for styled internal links, with corresponding unit tests and snapshots updated.Improved Send All logic to handle cases where the amount plus fee exceeds the address balance, automatically adjusting single recipient transfers and showing an error for multiple recipients. Unit tests were added.Stabilized profile and message tests by mocking the delay function to remove timing issues from setTimeout.
Next week, we’ll continue to improve based on the feedback from the community as well as internal testing.
Mainsail Weekly Report
This week, we refined the API based on feedback and worked on performance improvements. Work completed includes:
Write multi-payments to the Postgres database to improve API efficiencyAllow filtering of unconfirmed transactions by sender or recipient.Replaced keccak256 usages with native implementations where possible for better performance.Added an explicit Assert type to resolve TypeScript complaints.Updated the pino logger dependency.Updated EVM dependencies.
Next week, our primary focus will be on continued testing and addressing any issues reported by the internal team and the community. We’ll also work on further API enhancements.
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:
Mainsail - https://github.com/ArkEcosystem/mainsail/issuesARK Connect (Extension) - https://github.com/ArdentHQ/arkconnect-extension/issuesARK Connect (Demo) - https://github.com/ArdentHQ/arkconnect-demo/issuesARK Scan - https://github.com/ArdentHQ/arkscan/issuesARK Vault - https://github.com/ArdentHQ/arkvault/issues
Follow on Twitter (X)
Follow us on X  (https://x.com/ArkEcosystem) 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.
$ARK

Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, we resolved several issues in the ARK Connect extension, while the ARK Scan team focused on enhancing error reasoning for failed transactions alongside various fixes and refactors. The documentation site was updated with additional guidance on API setup and a new option for configuring validators on nodes, and the PHP Crypto module was improved to display clearer reasons for transaction failures. In ARK Vault, we addressed a number of issues reported during testing, focusing on small UI fixes and general adjustments. Meanwhile, the Mainsail team released a new version of the Mainsail EVM Testnet, delivering numerous improvements based on community feedback and internal testing, along with ongoing fixes and performance optimizations.
Development Activity Summary (August 1 – August 8, 2025)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from August 1, 2025, to August 8, 2025.

During this period, the team maintained strong productivity and engagement, delivering 126 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
This week, we resolved several issues with the ARK Connect extension:
Synchronized recent PSDK changes from ARK Vault to the extension to fix transaction sending problems.Corrected the transaction approval screen to properly display transaction details after reopening the extension window.
Next week, we’ll continue testing the extension and addressing any reported issues.
ARK Scan Weekly Report
We’ve been working on improving error reasoning for failed transactions, along with various other fixes and refactors. Completed work includes:
Refactored failed transaction handling to decode receipts and display specific failure reasons (e.g. out of gas, contract errors) for known transaction types and contracts, improving user feedback on transaction errors.Fixed caching of transaction resignation IDs by optimizing the job to fetch only new transactions since its last run, improving efficiency and reducing redundant data retrieval.Refactored the CacheNetworkAggregates command to use the Validator Registration scope, enabling more targeted and accurate aggregation of validator-related data.Refactored failed transaction handling to detect and display insufficient funds and out-of-gas errors, providing clearer feedback for transaction failures.Fixed spacing in the transaction Input Data container to prevent the left border from extending beyond the rounded edges when expanded.Refactored logic to allow overriding of public Vault and Connect URLs via .env variables, enabling customization (e.g., for Mainsail explorer) instead of defaulting to hardcoded ARK Vault links.Removed the redundant TODO related to LargestTransactionAggregate scopes, cleaning up the codebase.
Next week, we’ll continue improving Mainsail optimizations and addressing any issues reported by the community.
ARK SDKs and Documentation Site Weekly Report
We’ve updated the documentation site with additional information on setting up the API and introduced a new option for configuring validators on nodes. Additionally, we’ve enhanced the PHP Crypto module to display specific reasons for failed transactions. Specifically:
Documentation Site:Added additional instructions to the documentation site for Mainsail API installations to assist users with setup and configuration.Added a guide to the documentation for using config:forger:bls during validator registration to help users correctly configure their BLS keys if using the private BLS key option.PHP Crypto Package:Refactored transaction handling to support decoding ABI errors, enabling display of specific failure reasons for known transaction types when available. Next week, we’ll continue improving the documentation site and addressing any reported issues.
ARK Vault Weekly Report
This week, we focused on addressing issues reported during testing, primarily small UI fixes and various other adjustments. Work completed includes:
Fixed the addresses panel on mobile to use radio buttons (instead of checkboxes) in single view, matching the desktop behavior for consistent address selection.Refactored theme handling to persist the last used theme after logout, continuing to apply the signed-out profile’s theme until a new profile is created or a different one is signed in.Adjusted the loading indicator line width to be thinner for better alignment with the design specifications.Refactored gas fee calculation to add a 20% buffer to the eth_estimategas estimate, ensuring fees are safer by multiplying the increased gas estimate by the network gas price.Fixed fee rounding by using integerValue() to ensure fees are whole numbers, preventing errors from decimal values when submitting transactions.Refactored the multipayment recipients UI to implement the updated recipient design.Fixed the portfolio header on mobile by adding the missing vote button to ensure consistent functionality across devices.Refactored to remove reliance on the global configManager by storing network configuration (block height, crypto settings) within the network instance after synchronization, improving state encapsulation.Implemented address name editing and explorer link opening in the addresses side panel, along with adding corresponding unit tests.Enabled e2e tests for the message domain on Firefox by updating signature data to use correct Ethereum address formats and modifying e2e.yml to include Firefox test runs.Implemented fee time estimates based on actual block times by fetching block time from the network configuration and setting slow confirmations to 2× block time, with average and fast set to 1× block time, improving transaction confirmation accuracy.Fixed multipayment values in the transactions table to prevent unwanted text wrapping by applying filtering only to multipayment entries.Adjusted padding between the amount input and the “Add Recipient” button to 16px for consistent spacing.Fixed portfolio header on large screens to display the full address instead of truncating it, utilizing available space for better clarity.Added a hover state style for selected address entries in the address panel to improve visual feedback.Fixed transaction filter bug where undefined was sent to the API when deselecting filter options, preventing invalid requests and API errors during transaction type filtering.Corrected capitalization to display “Multiple Addresses” properly.Fixed side panel subtitle line height by increasing it to 28px for better readability and spacing.Updated project dependencies including Vite to v7.0.6, Cucumber to v12.1.0, ESLint plugins, and React Router to v7.7.1, ensuring the codebase uses the latest compatible versions.Updated table row hover background color to navy-blue-100 for improved visual consistency.
Next week, we’ll continue addressing reports from testing and focus on further improving the user experience with the recent Mainsail EVM integration.
Mainsail Weekly Report
This week, we released a new version of the Mainsail EVM Testnet, incorporating numerous improvements based on community feedback and internal testing. Highlights of this update include faster node synchronization, optimized syncing behavior, an updated napi-rs dependency, support for legacy transaction formats, and a new configuration command for setting validators using BLS12-381 private keys.
We have also made further progress on the following items:
Checked sync status and skipped transaction rebroadcast if the block is syncing. Non-included transactions are rebroadcast randomly between 1 and the MAINSAIL_TRANSACTION_POOL_REBROADCAST_COOLDOWN_BLOCKS option.Used distinctive server names with the service name (p2p, api, tx-pool, …) in the response on the main/endpoint for each HTTP server.Disabled internal Hapi logs.Removed the /transactions/schemas endpoint, as only EVM transactions with a single schema are supported.Used the skipPeerStateVerification option in the P2P tx-pool verifier, fixing an issue where nodes were partially checked even when the option was set to true.Added support for BLS private keys in Docker.Optimized TypeScript settings by enabling the composite: true option and adding scripts to update references in tsconfig.json files inside each package. These changes allow the TypeScript language server to correctly find references between packages, not just within the local package.
Next week we’ll be testing and making further improvements for the Public Mainsail Testnet.
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:
Mainsail - https://github.com/ArkEcosystem/mainsail/issuesARK Connect (Extension) - https://github.com/ArdentHQ/arkconnect-extension/issuesARK Connect (Demo) - https://github.com/ArdentHQ/arkconnect-demo/issuesARK Scan - https://github.com/ArdentHQ/arkscan/issuesARK Vault - https://github.com/ArdentHQ/arkvault/issues
Follow on Twitter (X)
Follow us on X  (https://x.com/ArkEcosystem) 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.
$ARK

Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, the ARK Connect team simplified the extension by removing the external PSDK Ledger dependency, while the ARK Scan team merged ongoing work into Mainsail and delivered fixes to performance and validator state. On the documentation side, efforts were centered on preparing the site for the release of the Mainsail EVM public testnet. The ARK Vault team continued with Ledger improvements, general UI fixes, and Mainsail-related updates. Most importantly, this week marked a major milestone for Mainsail development with the launch of Mainsail EVM on the Public Testnet and bringing us a significant step closer to full EVM compatibility within the ARK ecosystem.
Development Activity Summary (July 25 – August 1, 2025)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from July 25, 2025, to August 1, 2025.
ProjectCommitsAuthorsARK Connect81ARK Scan101ARK SDKs & Docs223ARK Vault684Mainsail473
During this period, the team maintained strong productivity and engagement, delivering 155 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
This week, we removed the external PSDK Ledger dependency from the ARK Connect extension to simplify the codebase. We also resolved issues with importing Ledger addresses to ensure smooth functionality.
Next week, we’ll continue integrating Mainsail EVM and address any issues that arise during development.
ARK Scan Weekly Report
Work done this week included consolidating work by merging the branch into Mainsail, as well as fixes to performance and validator state. To be precise:
Merged the mainsail-develop branch into mainsail, consolidating recent development work and ensuring the latest features, fixes, and refactors are integrated into the primary Mainsail branch for upcoming testing and deployment phases.Enabled the Validator Performance schedule command in app/Console/Kernel.php, allowing periodic performance checks for validators to be executed automatically via Laravel’s task scheduler.Implemented a dormant validator state and adjusted the filtering logic so that validators without a rank are correctly marked as “Standby” instead of “Active”, improving clarity in validator status display and preventing confusion around rank “0” validators.
Next week we’ll be addressing any issues that are reported from the internal team and community.
ARK SDKs and Documentation Site
This week we have been focused on improving documentation site for the release of Mainsail EVM public testnet. Work done included:
Updated the general Mainsail documentation site based on feedback, addressing clarity, structure, and content accuracy to improve the developer experience and alignment with recent Mainsail updatesAligned the documentation with recent SDK changes by updating references to EIP-155 and EIP-191, adjusting method names like gas to gasLimit, incorporating legacySecondSign for Core addresses, updating message signing examples for EIP-191, and pointing URLs to their MainsailHQ equivalents, ensuring accuracy and consistency across developer resources.Enabled anchor tag generation for h3 headers in documentation, improving navigability and deep-linking to more specific sections within a page.Fixed handling of h3 slugs by updating configuration to ensure anchor tags are correctly generated, enabling direct linking to third-level headings in the documentation.Updated the transaction tester documentation by fixing broken links and improving content on the tx-tester page, ensuring clearer guidance and navigation for users interacting with Mainsail transaction testing tools.Added further guidance on the validator registration process in the documentation, helping users better understand the necessary steps and requirements for registering a validatorClarified the meaning and usage of the BIP39 value during validator setup, including an explanation of the alternative method using a private key, to reduce confusion during configuration.Updated the Mainsail installation process to include installing python3-setuptools, setting default environment variables, and removing the forced checkout to the main branch to streamline source installation.
Next week, we’ll be further improving the Mainsail documentation site based on community feedback, as well as addressing any SDK issues that get reported.
ARK Vault Weekly Report
This week, we have been working on Ledger improvements, general UI fixes, and Mainsail enhancements. Here’s a summary of the work completed:
Disabled the Ledger import option on the public testnet to prevent users from importing Ledger wallets in that environment.Refactored error handling for user-rejected Ledger transactions to show a clear “rejected” message, distinguishing it from generic errors, and added “back” and “close” options for quick retries or adjustments.Adjusted fee validation logic so that the 250 ARK locked balance check applies only to validator registrations, allowing other registration types (like usernames) to proceed without it.Resolved a timing issue where the transaction review screen appeared prematurely by ensuring it waits for the Ledger connection and signing flow to complete.Corrected header margin on the contacts page for consistent spacing and improved visual alignment.Centered the checkbox within the create address flow to enhance UI consistency.Updated Send button colors in dim mode to use dim-blue-600 by default and dim-blue-700 on hover, improving visual feedback.Added .env.test to network configurations, allowing Vitest to use predefined values for easier test/mock maintenance and local network customization.Improved the transaction block status text by styling the “N/A” label with a semibold font weight for better emphasis.Replaced the BLS key documentation link with a direct resource to provide clearer access to key information.Enhanced the CreateProfile test suite with refinements that boost reliability and accuracy.Increased test stability by addressing flaky settings domain coverage: added a targeted test and reorganized existing ones into appropriate describe blocks.Expanded test coverage for the src/app/lib/mainsail/* module.Refactored environment storage to include the app version from package.json, and introduced automatic profile cleanup in environments missing a version tag.Implemented logic to hide the Exchange tab by toggling its visibility based on the VITE_HIDE_EXCHANGE_TAB flag.
We’ll continue working on community feedback, address any reported issues, and make further Mainsail integration improvements.
Mainsail Weekly Report
This week was exciting and a big milestone for Mainsail development as we announced the launch of Mainsail EVM on Public Testnet, marking a significant step toward bringing full EVM compatibility to the ARK ecosystem. This release introduces key features like 2-stage BFT consensus, instant block finality, on-chain usernames, and an updated validator set—all built on a snapshot of the Core v3 Devnet.
We invite developers, validators, and community members to jump in, explore, test, and help shape the future of Mainsail EVM. Your feedback will be vital in guiding us toward a stable mainnet launch.
Read the full announcement, Public Mainsail EVM Testnet Launches - Ushering in a New Chapter, to learn more.
We have also continued making improvements to Mainsail EVM. The work completed this week included the following:
Implemented transaction usage in consensus storage to store proposals, prevotes, and precommits as a single atomic commit.Updated revm and napi-rs to the latest version.Replaced ethers with viem to improve overall node performance and enhance block synchronization.Skipped dirty validator calculation during block commit when the Public API is disabled.Modified the ETH JSON-RPC API to return data in the legacy 0x0 Ethereum format, which is the default format in Mainsail.Added a config:forger:bls command for setting up validators using a private BLS12-381 key.Enhanced the install-testnet.sh script to install additional packages, enabling support for more cloud providers.Adopted the develop branch for releases tagged with rc for the public testnet, and continued using the evm branch for internal releases.Increased the pm2 version specified in peerDependencies.
Next week, we will focus on testing and refining the Public Mainsail Testnet, alongside preparing a new release that includes all recent fixes. We also plan to improve transaction rebroadcast logic.
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:
Mainsail ARK Connect (Extension) ARK Connect (Demo) ARK Scan ARK Vault 
Follow on Twitter (X)
Follow us on X  (https://x.com/ArkEcosystem) 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.
Here is the original article if you are looking for more info and links: https://arkscic.com/blog/ark-development-report-august-1-2025
$ARK

We’re thrilled to announce the launch of our first Public Mainsail EVM Testnet, built from the Core v3 Devnet Snapshot. After months of intense development and coordination, we’ve prepped everything, from infrastructure to tools, documentation, and user resources, so you can jump right in. This marks a major step forward in bringing EVM capabilities to ARK. And while we’ve come a long way, this is just the beginning. Over the next few months, we’ll be relying on your feedback, from the community and validators, to help us refine, secure, and polish Mainsail EVM into a production-ready product. So, whether you’re here to explore or help uncover the odd bug or two (we like to think of them as “undocumented features”), we welcome you aboard!
NOTE: Links are not allowed here and this article is full of them. If you are interested in learning more, here is the link to the original article: https://arkscic.com/blog/public-mainsail-evm-testnet-launches-ushering-in-a-new-chapter
A Few Key Notes Before You Set Sail
Delegate(s) are now officially Validator(s). If you spot any “Delegate(s)” references lingering around our front-end products, please give us a nudge.What was previously known as Devnet is now Testnet. We’ve aligned the terminology with broader blockchain standards for better clarity.The Public Mainsail EVM Testnet is spun up from a snapshot of the Core v3 Devnet at block height 22,002,491 . That means:Existing passphrases still work.Delegates who previously registered a BLS key and made it into the top 51 will appear as Validators.Validators will need to register again (using the new transaction type) to start producing blocks, unless they already did so on the previous Devnet.We’re transitioning from addresses starting with 'D' to the familiar Ethereum-style 0x format. It’s a small change in characters, but a big step toward EVM compatibility.We now refer to wallets (e.g., ARK Vault) as software products. The term address(es) is used to identify user account(s) capable of sending/receiving tokens on the network.Mainsail EVM features a two-stage BFT consensus mechanism with instant block finality. (Because who likes waiting?)The Public API is now an optional, standalone process, giving node operators more flexibility.Transaction broadcasting has moved:Old port: 4003 → New port: 4007P2P moved from 4001 → 4000To avoid a three-way split, the number of validators has increased to a prime number 53, up from 51.On-chain usernames can now be registered to any address, thanks to a dedicated username registration transaction done via contract.The ChainID for this Public Testnet is: 11812
We invite you to dive in, test things out, and help shape the future of Mainsail EVM. Your feedback is the wind in our sails - let’s build something great together.
Essential Resources to Get You Started
Ready to dive into Mainsail EVM? Whether you’re spinning up a node or aiming to become a validator, we’ve got you covered. Below is a curated list of essential documentation to help you get set up quickly and confidently:
Node Requirements  – Hardware, software, and system prep for running a Mainsail node.Network Details  – Ports, files, and public API nodes for connecting to the testnet.TX Tester CLI Guide  – Learn how to simulate transactions with our CLI testing tool as well as register a Validator.Registering as a Validator  – Step-by-step guide to validator setup and registration.Install Script (Recommended)  – The fastest and easiest way to install your node.Install from Source  – Prefer to build it yourself? We’ve got the guide for that too.Docker Install Guide  – Run your node in a containerized environment.
General Information
Our internal testnet has been running behind the scenes for several months. During that time, we performed multiple resets as we ironed out bugs and collected feedback from developers working on companion products like Vault, Scan, and Connect.
Now, with the foundation solid, we’re inviting you to join the next phase of real-world testing. Your participation will help us fine-tune performance, squash lingering bugs, and make Mainsail EVM production ready.
Here’s what’s currently available (products are still considered as alpha, so a few rough edges may remain; please open GitHub issues if you spot any!):
🔍 ARK Scan  – A full-featured blockchain explorer built for Mainsail EVM.💼 ARK Vault  – Your go-to wallet for managing tokens and interacting with the testnet.📖 Mainsail & SDKs Documentation  – Step-by-step setup guides, validator registration, SDKs, and more. (Note: this is a new site that will eventually replace ARK.dev)🧪 Mainsail TX Tester CLI  – A CLI tool to test transactions and validator flows.💧 Public Testnet Faucet  – Get free testnet tokens for testing transactions and registering as a validator.
This post outlines everything you need to begin your Mainsail journey and highlights what to expect in this early stage rollout.
We’re excited to have you onboard - test boldly, report issues, and help us shape what’s next!
Supported Transactions in the Public Mainsail EVM Testnet
During this initial phase of the Public Mainsail EVM Testnet, the following transaction types are supported. All except for general transfers are now processed through EVM smart contracts, bringing flexibility, composability, and a future-proof foundation to the ARK ecosystem.
Here’s what’s currently available:
Transfers – The classic: sending tokens from one address to another.Multipayments – Send tokens to multiple addresses in a single transaction. One click, many payouts.Vote – Cast your support for a validator using your address balance.Unvote – Remove your vote from a validator.Switch Vote – Change your vote from one validator to another, no need to unvote first.Validator Registration –Register your BLS public key to become a validator. You can update it at any time.Validator Resignation – Step down as a validator. The address becomes ineligible for new votes and block production.Username Registration – Claim a unique username for your address, adding a human touch to the chain.Username Resignation – Give up a previously registered username, much like a validator resignation, but for your alias.
This set of transactions forms the foundation for testing and interacting with Mainsail EVM. More functionality will follow as we expand and iterate based on your feedback!
Have a Question or Found an Issue?
Running into setup hiccups or spotting something that’s not quite right during testing? We’re here for it and we’d love to hear from you.
You can reach us through these channels:
Open an Issue on GitHub  – Found a bug or something not behaving as expected? Drop us an issue and we’ll take a look.Join the ARK Community Discord  – Swing by the community-run Discord and visit#mainsail_testnet channel to chat with the team and other community testers.
We encourage participation - whether it’s testing, providing feedback, or diving into the codebase itself. Your input is instrumental in making Mainsail EVM more resilient, efficient, and ready for prime time.
A Note on Architecture & Experience
We know Mainsail introduces some big architectural changes compared to Core v3. Validators and node operators will especially notice some differences in how things are set up. It might take a little time to adjust, but we’re here to support you every step of the way.
That said, we’ve made sure that for everyday users, the UI and experience feel familiar. Interacting with the network, whether through ARK Vault or ARK Scan, should still feel intuitive and aligned with what you’re used to from the current Production Network.
Thanks for helping us test, tune, and shape the future of Mainsail EVM. Let’s build something rock solid together.
What’s Next?
Over the coming weeks and months, we invite users to join the network and run public nodes. This will help us simulate real-world usage scenarios and test Mainsail EVM under broader network conditions.
On the development side, here’s what’s on the horizon:
Expanded Documentation – We’ll continue refining and expanding Mainsail docs to make setup, usage, and development even more accessible.Ongoing Issue Resolution – As bugs surface on Testnet, we’ll be addressing them swiftly; your reports are key here.Ledger Hardware Wallet Support – Integration into the Ledger ecosystem is underway, bringing hardware-level support.Vault & ARK Connect Integration – Work is in progress to make Mainsail EVM fully compatible with ARK Vault and ARK Connect.SDK Enhancements – Expect improvements to our SDKs based on real-world usage and developer feedback.Ecosystem Integrations – We’ll continue exploring and implementing integrations that make Mainsail more useful, flexible, and developer-friendly.
We’re committed to refining the Mainsail codebase, improving performance across the stack, and delivering a seamless user experience, powered by community input and real-world testing.
Thanks for being part of the journey. We’re just getting started.
Follow on Twitter (X)
Stay connected with 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.
$ARK

Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, the ARK Scan team added the ALPHA tag to the navigation bar in preparation for the upcoming Mainsail public testnet and continued work on ABI handling. On the documentation front, efforts were focused on adding Mainsail-specific content and expanding support for various EIP standards across the Python, PHP, and TypeScript packages. The ARK Vault team worked on enhancing Ledger compatibility alongside a series of fixes and general improvements. Meanwhile, the Mainsail team carried out a range of updates and final preparations based on internal testing as we get ready for the launch of the first public Mainsail testnet.
Development Activity Summary (July 18 – July 25, 2025)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from July 18, 2025, to July 25, 2025.

During this period, the team maintained strong productivity and engagement, delivering 140 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 worked on adding the ALPHA tag to the navigation bar in preparation for the upcoming Mainsail public testnet, along with continued work on ABI handling. The work completed included:
Added an ALPHA tag implemented via configuration, allowing flexible future use (e.g., switching to BETA). Setting the config value to an empty string hides the tag entirely.Updated the navbar logo to display the ALPHA tag with a tooltip for context, and styled it with rounded corners for a more polished appearance.Refactored transaction type handling to determine method names using a prioritized approach:Check explicitly defined types (e.g., isMultipayment) and use corresponding localized names.Match the payload hash against known contract entries from language files.Format the method name using the ABI if available.Fallback to displaying the raw 0x<PAYLOAD_HASH> if no match is found.
Next week, we’ll address any reported issues from our internal team and continue looking into general app optimizations.
ARK SDKs and Documentation Site Weekly Report
This week’s focus included adding Mainsail documentation to the documentation site and extending support for various EIP standards across Python, PHP, and TypeScript packages. Work completed involved:
Documentation Site:Added the initial Mainsail documentation covering key topics like overview, installation, deployment, EVM, testing, and support, and updated the site navigation to include the Mainsail section.Updated the Meilisearch configuration to use environment variables for endpoint selection, ensuring that search results are scoped correctly to each documentation section. This fixes the issue where searching on the Mainsail docs page would return SDK-related results and restores missing Mainsail pages to the search index.Pinned the Meilisearch DocSearch dependency to an explicit version instead of latest, preventing unexpected breaking changes and ensuring predictable builds and stable search behavior.Python Crypto Package:Added the validator registration value to the builder.Added EIP-155 support to the Python package, enabling compatibility with the latest transaction signing formats used in Mainsail.Support for legacy second signature handling has been added, allowing transactions that require a second signature to be properly processed and signed.Updated the Python package to implement EIP-191 message signing, refining the signing logic to comply with this standard for improved compatibility when signing messages.PHP Crypto Package:Added EIP-155 support to the PHP package, enabling compatibility with updated transaction signing formats required by Mainsail and ensuring proper handling of chain-specific signatures.Support for legacy second signature handling has been added, enabling transactions that require a second signature to be correctly processed and signed.The PHP package has been updated to implement EIP-191 message signing, refining the signing logic to comply with this standard and improving compatibility for message signing across supported systems.TypeScript Crypto Package:Added support for signing messages using the EIP-191 standard, improving message signing compatibility and security.
Next week, efforts will continue on refining Mainsail documentation based on feedback and resolving any issues encountered when interacting with the crypto SDK packages.
ARK Vault Weekly Report
This week, we focused on further improving Ledger compatibility along with a range of other fixes and improvements. The work completed included:
Corrected the chain ID used during Ledger signing by removing the unnecessary addition of 27 to the signature’s v value. This resolves transaction failures with newer Mainsail packages, improving compatibility and preventing signature errors.Added an ALPHA tag with a tooltip in the navigation bar to indicate that Vault is running an alpha version, improving version visibility and preparing users for the Mainsail release.Adjusted the Select Profile page layout to prevent the “Import Profile” text from overlapping on small-height mobile screens, enhancing readability.Updated the explorer URL for the Mainsail network to ensure correct linking and accurate network references.Extended the transaction table to support all known contract methods (consensus, multipayment, usernames) using ABIs, enabling human-readable method names and parameter data instead of hardcoded signature mappings.Fixed the back button behavior in the send vote flow to properly return to the review step during error states, improving navigation and user experience.Fixed validator address and name display in transaction details, ensuring correct display in vote-related views (pending and confirmed).Added support for message signing using Ledger devices, expanding hardware wallet functionality for Mainsail.Removed unused WIF-related code and added a fromWif method in the PublicKeyService, cleaning up the codebase.Standardized form label padding across all mobile action forms for consistent alignment and improved layout.Resolved an error during profile import in the profile domain that was causing test failures.Moved tests from the wallet domain to the portfolio domain and fixed them accordingly.Cleaned up e2e-utils.ts by adding a dynamic mock for /api/transactions/transaction-hash to reduce flakiness.Removed e2e test-related files from the wallet domain and updated import paths across files for consistency.
Next week, we’ll focus on resolving any remaining issues reported by our internal testing team and making further improvements based on their feedback.
Mainsail Weekly Report
This week, we focused on a range of improvements and fixes based on our internal testing. The work completed includes:
Added support for snapshot configuration publishing in the Mainsail install-testnet.sh script.Removed obsolete environment variables from the Mainsail codebase.Enabled nethashSalt configuration in the network generator to allow the creation of networks with the same chainId but different nethash values.Improved block downloading over P2P — synchronization can now be completed from a single node.Updated logic to use the commit round (instead of block round) to increment and store the total round in the EVM database. This resolves issues where blocks from a previous round could be re-proposed, causing inconsistencies and stuck nodes.
Looking ahead, next week we’ll be preparing for the launch of the first public Mainsail EVM Testnet — stay tuned!
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:
Mainsail - https://github.com/ArkEcosystem/mainsail/issuesARK Connect (Extension) - https://github.com/ArdentHQ/arkconnect-extension/issuesARK Connect (Demo) - https://github.com/ArdentHQ/arkconnect-demo/issuesARK Scan - https://github.com/ArdentHQ/arkscan/issuesARK Vault - https://github.com/ArdentHQ/arkvault/issues
Follow on Twitter (X)
Follow us on X  (https://x.com/ArkEcosystem) 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.
$ARK

Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, we continued refining the ARK Connect extension by addressing reported issues and cleaning up unused code. On the SDK side, we updated the crypto packages for Python, PHP, and TypeScript to include the latest fixes and improvements in line with recent Mainsail updates. The ARK Vault team focused on end-to-end testing and coverage, added support for a new transaction format, and implemented a range of fixes and UI enhancements. Meanwhile, the Mainsail team concentrated on legacy support and general fixes as part of the ongoing preparation for the upcoming Public Testnet.
Development Activity Summary (July 11 – July 18, 2025)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from July 11, 2025, to July 18, 2025.

During this period, the team maintained strong productivity and engagement, delivering 120 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
This week, we continued work on the ARK Connect extension by addressing issues and cleaning up unnecessary code. The work completed included:
Fixed a Firefox-specific build issue and resolved problems with transaction sending to ensure smooth functionality and cross-browser compatibility.Refactored the application to enable viewing of the private key, allowing users to access and display their private key when needed.Removed unnecessary wallet.synchroniser().coin() calls for message signing as part of the PSDK migration. Since syncing is not required for signing messages, the redundant sync logic was safely eliminated to improve performance and simplify the flow.
Next week, we’ll focus on further fixes and improvements to the extension based on feedback from the internal testing team.
ARK SDKs and Documentation Weekly Report
This week, we continued updating the crypto packages (Python, PHP, and TypeScript) to incorporate the latest fixes and enhancements aligned with recent Mainsail changes. The work completed included:
PHP Crypto Package:Refactored component iteration to avoid using array indices as keys. Instead, it now relies on the named keys from the ABI definitions, ensuring compatibility with component structures like those in the Consensus and Usernames contracts that use named fields such as from and to.Refactored the code to include the validator registration value. This supports accurate transaction construction and display.Added tests to cover the remaining utility functions, improving overall test coverage and ensuring more reliable and maintainable utility code.Upgraded PestPHP and configured code coverage reporting to enhance testing capabilities.Updated the network chain ID values for both testnet and mainnet in the package to match the specified configurations. This ensures correct identification and interaction with the intended blockchain networks.TypeScript Crypto Package:Fixed signature padding by ensuring the v value of 0 or 1 is properly formatted as 00 and 01 during signing.Added support for legacy second signature transactions in the TypeScript package, enabling signing and verification of these older transaction types.Refactored transaction handling to support legacy EIP-155 format instead of EIP-1559, aligning with recent Mainsail protocol updates while preserving the option to revert if needed.Python Crypto Package:Updated the network chain ID values for both testnet and mainnet in the package to match the specified configurations. This ensures correct identification and interaction with the intended blockchain networks.Documentation Site:Configured Meilisearch workflows to run only on the main branch. This update also adjusts the scraping process to run locally within the workflow and modifies the “fix” script to correctly update Mainsail index URLs.
Next week, we’ll focus on further package improvements and begin updating the documentation site in preparation for the public launch of the Mainsail EVM testnet.
ARK Vault Weekly Report
This week, we focused on end-to-end (E2E) testing and coverage, added support for a new transaction format, and made various fixes and UI improvements. The work completed included:
Added support for sending transactions with legacy second signatures by enabling Vault to detect and prompt users for the required second signature during wallet import and transaction signing, preventing transaction failures caused by missing legacy second signatures and ensuring smooth processing of transactions for addresses that require this authentication method.Fixed an issue where signing transactions with a Ledger device failed due to an invalid state error (“device must be opened”) by ensuring the Ledger is properly connected and the device state is validated before signing, preventing errors when sending from newly imported Ledger addresses immediately after profile creation.Updated the ts-crypto package to support the EIP-155 transaction format, enabling Vault to handle this standard correctly.The balance tooltip is now centered for better visibility and is disabled when opening the settings dropdown on mobile, preventing unwanted overlap or distraction.Implemented a fix for mnemonic/secret autocomplete issues by using an approach that involves overlaying an uninteractive password input on top of a text input with invisible text to simulate masked input. This workaround aims to prevent browser autofill from interfering while maintaining user privacy.Moved the Ledger icon from beside the Copy Address button to directly next to the address on the dashboard, improving visual association and clarity.Adjusted the “Update Validator” form fields on mobile to ensure consistent width across mobile screens, improving the user interface and layout.Improved mobile tooltips to break long words, enhancing readability and preventing layout issues on smaller screens.Updated mobile transaction headers to ensure consistency and alignment with the new design mockups, improving the visual coherence across transaction views.Removed the Ledger USB dependency setup steps from the CI configuration to simplify the build process.Added Dim Mode support to the transaction confirmations component, enhancing the UI by ensuring consistent theming during transaction confirmation steps.Updated end-to-end test workflows by adding the feat/evm branch to push triggers and restricting pull request triggers to run only for PRs targeting the main branch, refining test execution scope.Enabled and fixed end-to-end (e2e) tests across multiple domains—contact, dashboard, vote, settings, message, and transaction—improving overall test coverage and reliability. Additionally, musig-related tests and ARK coin mocks were removed, and delegate references in tests were replaced with validator to reflect recent terminology changes.
Next week, we’ll continue improving test coverage across the app and address an issue reported by our internal testing team.
Mainsail Weekly Report
This week, we focused on legacy support and general fixes in preparation for the Public Testnet. The work completed included:
Added support for pre-EIP-2718 transactions to improve compatibility with wallets such as MetaMask, Rabby, and others.Fixed issues with the installation script.Continued preparations for the Public Testnet.
Next week, we’ll turn our attention to the final phase of internal testing and make the last preparations for the fast-approaching Public Mainsail Testnet launch.
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:
Mainsail - https://github.com/ArkEcosystem/mainsail/issuesARK Connect (Extension) - https://github.com/ArdentHQ/arkconnect-extension/issuesARK Connect (Demo) - https://github.com/ArdentHQ/arkconnect-demo/issuesARK Scan - https://github.com/ArdentHQ/arkscan/issues ARK Vault - https://github.com/ArdentHQ/arkvault/issues
Follow on Twitter (X)
Follow us on X  (https://x.com/ArkEcosystem) 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.
$ARK

Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, we focused on the ARK Connect demo site and began updating the ARK Connect extension to align with the latest changes from Mainsail. The ARK Scan team worked on optimizing loading times and addressing Composer warnings, while improvements to the documentation site included user experience enhancements and the addition of ABI definitions to the PHP Crypto SDK. In ARK Vault, development continued with fixes and improvements driven by recent internal testing and Mainsail updates. Meanwhile, the Mainsail team addressed issues reported by the development team and continued work on legacy support features.
Development Activity Summary (July 4 – July 11, 2025)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from July 4, 2025, to July 11, 2025.

During this period, the team maintained strong productivity and engagement, delivering 132 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
This week, we focused on the ARK Connect demo site and began updating the ARK Connect extension to incorporate the latest changes from Mainsail. Work completed includes:
ARK Connect Demo Site:Fixed an issue where the vote modal did not correctly display the currently voted validator, ensuring the voting state is accurately reflected in the UI.Adjusted the validators list to display the username when available and fall back to the address otherwise, while also updating the filter logic to search by both username and address.ARK Connect Extension:Replaced all instances of “Delegate” with “Validator” across the codebase to reflect updated terminology and ensure consistency with current protocol language.Fixed the vote transaction sending logic to ensure the voting flow works correctly, allowing users to successfully broadcast their vote transactions.Fixed the logic for checking transaction confirmation status to ensure accurate detection and updates of confirmed transactions.Removed the network field from the contact object and updated the contact creation and editing pages accordingly. Simplifies the address validation logic for cleaner and more consistent handling.Adjusted the useExchangeRate hook to use the active profile for retrieving exchange rates instead of relying on the global environment object.Removed the network selection step from the create/import wallet flow and added a “Use Testnet” switch in the dropdown menu for testing purposes. Also refactored the useActiveNetwork hook to derive the active network from the profile.Fixed address truncation across multiple pages to ensure addresses display correctly.Fixed the UI to hide the validator username labels when the validator has no username set, so “Vote Validator Name” and “Unvote Validator Name” entries no longer show empty or placeholder text.Fixed the recent transactions list to correctly display vote and unvote transactions by falling back to the address when the validator’s username is not set and hiding helper text for unvote transactions.
Next week, we will continue implementing the necessary Mainsail updates in the extension and make further improvements to the demo site.
ARK Scan Weekly Report
This week, we focused on improving loading times and addressing Composer warnings. The work completed includes:
Optimized performance by improving how “voted for” wallets are handled in transaction tables and how delegates are fetched for missed blocks, reducing redundant queries and enhancing load times.Refactored support for the updateValidator transaction by displaying the correct method name and showing the BLS public key being set, rather than relying on the raw method signature.Resolved Composer warnings, updated the Foundation package, and fixed failing tests related to toast notifications to ensure a clean build and consistent test results.
Next week, we’ll address any issues reported by our internal testing team and continue working on further performance optimizations.
ARK SDKs and Documentation Site Weekly Report
This week, we focused on user experience improvements for the documentation site and added ABI definitions to the PHP Crypto SDK. Specifically, the work completed includes:
Documentation Site:Refactored to support additional Meilisearch indexes, allowing separate Meilisearch instances per documentation set (e.g., SDK and Mainsail) within a single-site setup. This introduces endpoint-based isolation to ensure each instance is scoped to its respective domain.Enhanced the search functionality to prioritize and filter results based on the currently selected language (e.g., Python, JavaScript), improving result relevance. The active language is now highlighted in search results for better clarity and usability.Updated scraper workflows to use new configuration files, aligning with recent structural changes and improving long-term maintainability.TypeScript Crypto Package:Refactored transaction handling to export ABI definitions for all known contracts (e.g., consensus, multipayment, usernames) and dynamically resolve contract method names. This enables the transaction table to display human-readable method names and parameters, eliminating the need for hardcoded signature mappings and improving clarity and maintainability.
Next week, we’ll continue refining the SDKs based on feedback from the development team and begin documenting the upcoming Mainsail public devnet.
ARK Vault Weekly Report
This week, we worked on improvements and fixes based on recent internal testing and updates from Mainsail. Highlights include:
Refactored the transaction table to display raw method signatures (e.g., 0x9f5523eb) for unknown contract methods instead of defaulting to “Contract Deployment,” improving transparency and debugging accuracy.Fixed the “Load More” button behavior in the transaction table. Previously, it would reset the view after a few seconds. Now, loaded transactions persist without disruption.Enhanced validator registration: If an address is already a validator without a validatorPublicKey, the flow now uses updateValidator instead of registerValidator, bypassing fund locking and displaying a relevant message to support legacy delegates.Resolved a bug in “Single View” mode where deleting an address would clear the entire profile. Now, the app correctly falls back to another imported address.Added deeplink support for voting, allowing links to trigger the voting flow using a validator’s name, public key, or legacy delegate name.Enabled deeplink support for message signing. The deep link now triggers the signing panel directly from the dashboard, aligning with the new side panel layout.Refactored the dim theme selection: it now appears as a dropdown on mobile while retaining button groups on larger screens. Added unit tests to cover these changes.Fixed padding issues in the contacts page header for consistent alignment with other views.Refactored the address select dropdown component to clarify whether changes apply globally or only to specific forms like transfer and signing, taking into account wallet balance display.Fixed an error when importing a Ledger wallet and immediately sending a transaction. The wallet now syncs with the network correctly upon import, avoiding milestone configuration errors.Adjusted spacing and button layout in the Ledger side panel to better align with design specifications.Fixed alignment issues in mobile views by removing excess margin in transaction review and approval pages.Standardized label usage across transaction flow pages by replacing all “Category” labels with “Method” in the Action section.Fixed mobile layout of the transaction table by truncating the “failed” label to prevent overflow. Added tests for this behavior.Improved mobile readability by adjusting font sizes: import buttons, success steps, recipient cards (14px), and sign message sidepanel close button (16px).Updated the empty state UI on the Contacts page for mobile to match design specifications.Revised the verify message form content and styling to match the latest designs. Updated success screen titles and corresponding test snapshots. (Note: header and padding updates to follow separately.)Enhanced the portfolio header to display the full address on desktop instead of truncating, improving visibility and clarity.Fixed and re-enabled E2E tests for the profile domain to improve test coverage and reliability.
Next week, we’ll continue addressing feedback from internal testing and refining the UI based on recent tester remarks.
Mainsail Weekly Report
This week, we focused on resolving issues reported by the development team and continued work on legacy support. Key updates include:
Fixed an issue where the username attribute was missing under certain conditions.Updated legacy second signatures to use raw ECDSA values (r, s, v).Removed the obsolete timestamp field from transactions.Cleaned up the api-development package by removing unused and broken endpoints.
Next week, we’ll conduct a final round of internal testing and begin preparations for the first Public Mainsail Devnet.
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:
Mainsail - https://github.com/ArkEcosystem/mainsail/issuesARK Connect (Extension) - https://github.com/ArdentHQ/arkconnect-extension/issuesARK Connect (Demo) - https://github.com/ArdentHQ/arkconnect-demo/issuesARK Scan - https://github.com/ArdentHQ/arkscan/issuesARK Vault - https://github.com/ArdentHQ/arkvault/issues
Follow on Twitter (X)
Follow us on X  (https://x.com/ArkEcosystem) 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.

$ARK