ARK Ecosystem

Laipni lūdzam mūsu jaunākajā iknedēļas attīstības ziņojumā, kur mēs izceļam mūsu attīstības komandas varonīgos centienus. Šonedēļ ARK Scan komanda turpināja virzīties uz priekšu ar Inertia migrāciju un uzlaboja Eksporta funkciju, lai atbalstītu papildu datu eksportēšanas iespējas. ARK Vault komanda koncentrējās uz Sānu paneļa atjauninājumiem, labāku gaidīšanas darījumu apstrādi un dažādiem labojumiem un uzlabojumiem. Tikmēr Mainsail komanda strādāja pie apstrādes veiktspējas paaugstināšanas, statistikas atbalsta paplašināšanas un papildu vispārēju uzlabojumu nodrošināšanas visā platformā.

Laipni lūdzam mūsu jaunākajā Nedēļas Attīstības Ziņojumā, kur mēs izceļam mūsu attīstības komandas drosmīgos centienus. Šonedēļ ARK Scan komanda turpināja progresēt ar Inertia migrāciju, īstenojot vairākus mazus labojumus un uzlabojumus ceļā. Dokumentācijas vietnē mēs pievienojām jaunu vietējo uzstādīšanas ceļvedi Mainsail, lai padarītu uzņemšanu vieglāku izstrādātājiem. ARK Vault komanda koncentrējās uz Ledger migrācijas funkcijas pabeigšanu un profila importēšanas problēmu risināšanu, kamēr Mainsail komanda strādāja pie vispārējiem uzlabojumiem un paplašināja testēšanas segumu, lai vēl vairāk nostiprinātu vispārējo stabilitāti.

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