5th Dec 2025
6 min read

ARK Development Report - December 5, 2025

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 on the Inertia migration while implementing general performance improvements across the application. The ARK Vault team made further advancements on the Contract Deployment feature and resolved multiple UI issues identified during internal testing. Meanwhile, the Mainsail team expanded JSON RPC functionality and enhanced the TX Tester script based on valuable community feedback.

Development Activity Summary (November 28 – December 5, 2025)

Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from November 28, 2025, to December 5, 2025.

Project Commits Authors
ARK Connect 0 0
ARK Scan 62 2
ARK SDKs & Docs 0 0
ARK Vault 55 2
Mainsail 13 2

During this period, the team maintained strong productivity and engagement, delivering 130 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 focus remained on the Inertia migration, along with general performance improvements across the application. Work completed includes:

  • Introduced the desktop logo and top navigation bar as part of the Inertia migration.
  • Added responsive mobile navigation to the navbar, enabling a fully functional browsing experience on smaller devices.
  • Applied a bottom border to active navbar dropdown pages so that Inertia-rendered dropdowns visually match the Livewire/Alpine version.
  • Restored proper hover styling on the theme selection button to improve usability and visual feedback.
  • Created a reusable Inertia layout that includes the default navbar and shared page elements, streamlining future migrations and ensuring consistent structure across pages.
  • Refactored the monitor page to eliminate duplicate queries by investigating repeated proposer and block height requests and reducing unnecessary database load.
  • Improved job execution by ensuring all fast explorer commands use withoutOverlapping(), and setting quick cache-refresh jobs to $tries = 1 so the scheduler handles retries more efficiently.
  • Corrected the heavy “most transactions” query by identifying the problematic logic and adjusting it to reduce server strain while maintaining the 5-minute execution interval.
  • Implemented mobile search in the navbar, restoring missing behavior from the previous implementation and revisiting lockBody, isIOSSafari, and @theme-changed logic to ensure smooth navigation in the migrated Inertia version.
  • Corrected formatting for transaction fee averages so displayed values accurately reflect the underlying data.
  • Updated navigation behavior to properly handle and preserve URL query strings, ensuring consistent rendering and browser history behavior.
  • Refined the address tabs design by slimming them down and aligning the layout with ARK Vault for improved visual consistency.
  • Fixed the loading state of the voters’ balance table so that currency translation updates correctly within the loading column.
  • Hid the Blocks and Voters tabs for non-validator addresses to avoid showing irrelevant data.
  • Updated dropdown styling throughout the application to match other Inertia and Vault components, improving UI cohesion.
  • Added the missing mobile header and “0 Results” indicator for the voters loading table to ensure a complete mobile layout.
  • Introduced an empty-state page for validators in Inertia, including a clear title and subtitle for situations where no validator data is available.
  • Removed unused AlpineJS properties from an Inertia component that were triggering devtools errors, resulting in cleaner and more stable code.

Next week, we’ll continue progressing on the Inertia migration, work on further performance improvements, and address any issues reported during testing.

ARK Vault Weekly Report

This week, we continued developing the Contract Deployment feature and addressed several UI issues identified during internal testing. Work completed includes:

  • Refactored the contract deployment flow by updating the review step and integrating the remaining transaction stages—review, fees, and authentication—to provide a complete and intuitive deployment experience.
  • Introduced an HD wallet import hint with a lightweight queue system to prevent overlapping tooltips and maintain a clean interface when multiple hints appear.
  • Saved the sent timestamp for pending transactions, enabling accurate timing information in the transactions table.
  • Improved spacing in the Select Sender modal by fixing the padding between rows for clearer readability.
  • Added validation for contract bytecode to ensure only valid hexadecimal input is accepted, reducing user errors.
  • Resolved an issue in the single-selection view where clicking the active address would deselect it and close the sidebar, ensuring the selected wallet remains stable.
  • Corrected HD wallet account name editing so that changes apply consistently across all wallets derived from the same seed.
  • Updated the title in the value-entry step of the HD wallet import flow for accuracy.
  • Adjusted the lock icon color in dark mode to match the design specification.
  • Cleaned up text alignment on the welcome page, ensuring the “Exported a Profile before? Import it here” line is properly positioned.
  • Fixed the Create → Import Address transition so the correct side panel closes and opens seamlessly when clicking “Import instead.”
  • Enabled contract deployment by allowing deployment transactions to be sent with complete, correct data in the background.
  • Hid the full-screen/expand button on mobile devices to declutter the side panel interface.
  • Updated the transaction details side panel to display contract bytecode for deployment transactions, giving users full visibility of the deployed content.
  • Corrected the error message styling in the addresses side panel.
  • Fixed transaction ID formatting at the 640px breakpoint to prevent overflow and layout issues.
  • Resolved a double-error issue in validator registration and adjusted button padding on the error step for a cleaner presentation.
  • Reworked gas limit handling by removing debounce(data, 700) from FeeField, fixing multiple related problems and ensuring accurate gas estimation.

Next week, we’ll finalize the Contract Deployment feature, address incoming issues, and begin outlining the UI for the Tokens feature.

Mainsail Weekly Report

This week, we continued expanding JSON RPC functionality and improved the TX Tester script based on community feedback. Work completed includes:

  • Mainsail

    • Added deploy-transaction support to both eth_call and eth_estimateGas, enabling more accurate simulation and gas estimation for contract deployments.
    • Improved eth_call handling to correctly process undefined outputs, ensuring more reliable responses across various contract interactions.
  • TX Tester

    • Enabled compilation of simple Solidity contracts using the compile_contract command.
    • User can alternatively use outputs from external sources (like Remix) for more complex contracts.
    • Introduced the prepare_contract command to generate a ready-to-use contract object for the tester.
    • Added multi-network support by allowing seamless replacement of the network object in config.js.
    • Made contract deployment executable directly from each contract’s menu for a more intuitive workflow.
    • Added error-decoding support via eth_call for deployments, transactions, and view calls, improving debugging clarity.
    • Removed reliance on the transaction_pool API, switching fully to the EVM JSON RPC API for consistent behavior.
    • Ensured compatibility with any EVM-compliant JSON RPC client, making the tester more flexible and broadly usable.

Next week, the focus will shift to further enhancing the JSON RPC API and addressing issues reported by the community or internal testing team.

Feedback & Feature Requests

If you are using our open-source products and would like to provide feedback or request a feature, please feel free to contact us via the contact pages for the specific product you are using or open an issue on GitHub.

Quick access links to GitHub issues pages:

Follow on Twitter (X)

Follow us on X (Formerly Twitter) and keep checking the blog to stay up-to-date on all of our new releases. We post a weekly development report so you can easily see what we’ve been up to and follow along our journey towards making your decentralized future a reality.

Share:

Get in Touch!

Whether you want to learn more about ARK Ecosystem, want to apply for developer bounty, become our partner or just want to say Hello, get in touch and we will get back to you.



An Ecosystem of Developers

Join us on our journey to create the future of Web3.