ARK Development Report - October 25, 2024

Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, the ARK Scan team finalized the migration to the latest major version of Laravel and continued implementing the required changes for the EVM. The ARK Docs team worked on cleaning up the obsolete Crypto and Client Libraries section and made additional design updates. Meanwhile, the ARK Vault team focused on design improvements and addressed reports from internal testing in preparation for the final internal release candidate. The Mainsail team focused on enhancing both EVM functionality and API integration.

#Development Summary

Below is a breakdown of total commits and authors by project for development activity over the last week from October 18th through October 25th, 2024.

Overall, the team has demonstrated consistent productivity and engagement over this period, with a total of 122 commits across all projects.

The number of commits and data for each project will fluctuate every week depending on internal sprints, objectives, and difficulty.

#ARK Scan Weekly Report

The ARK Scan team has completed a major upgrade to Laravel and made further progress on Mainsail EVM integration. Here’s a breakdown of the work done this week:

• Updated Laravel to its latest major release, version 11. This upgrade involved addressing several breaking changes to ensure compatibility across the project. ARK Scan now requires PHP v8.3. To align with this new PHP version, workflows and the composer configuration were adjusted.
• Added git as a dependency to the Dockerfile. This ensures git is included in the installed dependencies, streamlining setups in Docker-based environments.
• Adjusted the list of validators (active, standby, and resigned) to work with the latest changes introduced by Mainsail.
• Refactored the handling of cached public keys, specifically for wallet, statistics, and validator data.
• Improved how vote public keys are managed, including updates to caching voting-related data. This also fixed some failing tests regarding vote percentages.

Next week, the team will continue to work on Mainsail EVM integration further and address any issues that arise from ongoing work.

#ARK SDKs & Docs Weekly Report

We’ve been working on new docs site improvements including:

• Reviewed the “Crypto Libraries” & “Client Libraries” sections and identified what was outdated, and potentially misaligned with current API changes and library updates and initiated a thorough review by removing deprecated content and adding missing information to lay the groundwork for a more comprehensive revision in the future.
• Updated the installation steps for the crypto and client SDKs to reference the latest changes in the feat/mainsail branch, temporarily directing users to install the development versions instead of the latest release.
• Added the missing social networks & removed the obsolete ones from the footer section.
• Added a new favicon to the documentation site.
• Started on further adjustments to the PHP SDK to be compatible with the latest changes introduced by Mainsail.

Next week we’ll continue working on further documentation improvements as well as fix any issues with SDK packages for Mainsail.

#ARK Vault Weekly Report

This week we continued working on the design updates and fixes that were reported in the previous week. Work done this week includes:

• Worked on replacing the current dropdown implementation with a new one to reflect UI design changes.
• Modified the pending table to display multisignature registrations as “To” instead of “From” when registering a multisignature address.
• Added 16px of padding between the page description and the “Addressing” section on the review page of the voting transaction.
• Added missing header on the Ledger import page at 640px breakpoint.
• Updated the recipients interface for multipayment transactions on mobile to align with the latest design changes.
• Corrected the font color in a light mode for transaction forms, addressing an issue caused by a recent design change that resulted in the incorrect color being displayed.
• Added the delegate name to the UI on the Pending and Confirmed pages for vote transactions, which was previously missing.
• Moved the “Send All” button on the mobile Send transaction form to align it with the Amount header for improved user interface consistency.
• Resized and relocated the “Scan QR” button on the mobile transactions interface.
• Adjusted the Wallet Details page on mobile to prevent the address from being cut off by reducing the number of characters displayed before and after truncation.
• Corrected the transaction details in the pending table for multisig wallet transactions, ensuring that it now displays To <recipient> instead of From <multisigAddress> and updated the value to reflect the correct amount.
• Updated the Review page for multipay transactions to display “To Multiple (n)” and implemented a link that opens a modal showing the complete list of recipients.
• Updated the delegate registration interface to reflect the latest design changes.
• Adjusted the font size of the text in the recipient dropdown on mobile transaction forms to 14px for consistency with the rest of the page.
• Centered the profile selection content on the profile select page for improved layout on mobile devices.
• Resolved the alignment issue on the Transaction Review page for Delegate Registration by ensuring the address name aligns properly with the content below it.
• Implemented a bottom border for the transaction table when the “Load More” button is not present, visually indicating the end of the table content.
• Adjusted the transaction details modal on mobile to display in full screen, fixing the visual padding issue. Additionally, implemented a custom scrollbar class for improved usability within the modals.
• Adjusted the E2E tests to use port 5001 instead of the default port 5000 on Mac, resolving potential conflicts. Additionally, configured the tests to run sequentially, ensuring that each e2e test executes one at a time to improve reliability and address intermittent issues with GitHub CI.

Next week, our goal is to prepare the release candidate for final checks before the public release and address any issues reported by the internal team. At the same time, we’ll begin work on the new sprint, which will include a few additional design updates planned for future releases.

#Mainsail Weekly Report

This week, we continued developing new features and improvements in the EVM. Key accomplishments included:

• Adapted the HTTP API to accommodate the latest transaction changes.
• Implemented PostgreSQL database restore functionality without the need to re-process all blocks.
• Developed a prototype to combine block and EVM storage.

Next week, we will focus on making further improvements to the API and contracts. We will also work on finalizing the Ethereum transaction format and continue with PostgreSQL database restore follow-ups.

We’ve also published a detailed blog post covering all the recent changes, including Mainsail’s full integration with the EVM. To learn more, check out the post titled “Mainsail EVM - Transitioning to Full EVM Support.”

#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 (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.