23rd Aug 2024
4 min read

ARK Development Report - August 23, 2024

Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. For ARK Scan, we’ve been keeping a close eye on the production network to ensure everything is functioning smoothly with the new WebSockets integration. Meanwhile, progress continues on the Python and Java ARK SDKs, adding support for BLS keys. The ARK Vault team has been focused on enhancing the app’s UI, while the Mainsail team has been making EVM improvements and working on the Validators & Voting contracts within the EVM.

Development Summary

Below is a breakdown of total commits and authors by project for development activity over the last week from August 16th through August 23rd, 2024.

Project Commits Authors
ARK Connect 1 1
ARK Scan 1 1
ARK SDKs 8 3
ARK Vault 90 4
Mainsail 5 1

Overall, the team has demonstrated consistent productivity and engagement over this period, with a total of 105 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

We have been closely monitoring ARK Scan’s new WebSockets integration on the production network, and it’s been running smoothly without any issues. Additionally, we are continuing to work on the Validator Monitor overflow for Mainsail and testing it in a staging environment.

Next on the list for development on the ARK Scan front will be furthering integration with Mainsail support with all of the recent changes and additions in the upcoming weeks.

ARK SDK’s Weekly Report

This week, our efforts on the Python and Java SDKs continued, with a primary focus on BLS keypairs. Here’s a summary of the work completed:

Python Crypto and Client

  • Completed the integration of BLS key generation support, including necessary adjustments to a third-party library to ensure correct key generation.
  • Fixed an issue related to including submodules in packages.
  • Resolved issues with multi-sign signatures and fees.

Java Crypto and Client

  • A method for transaction serialization support was added.
  • Implemented handling for the client API split.

In addition to the above, we’re also working on updating the SDK documentation to reflect these changes. Next week we’ll continue the documentation updates and start on implementing the adjustments for the Go SDK.

ARK Vault Weekly Report

This week, we focused on making improvements to the UI of ARK Vault. Key updates included:

  • Made design changes to the create profile page, introducing a new starting screen and adding a small slider with useful information.
  • Redesigned the import Ledger page, which involved:
    • Adding a new icon.
    • Updating the translation file.
    • Creating a new LedgerWalletImport.blocks file for reusable components.
    • Refactoring the Ledger import completed page to align with the new designs, including support for dark/light mode and desktop/mobile views.
    • Updating and refactoring the single wallet import view.
  • Updated error screens by refreshing images and refactoring the disconnected and error pages to match the new designs.
  • Worked on design changes for the ‘My Votes’ section to align it with the overall design.
  • Adjusted long memos so they now break into multiple lines instead of overflowing.
  • Updated the border radius for the header section of tables to resolve spacing issues.
  • Made design adjustments to all steps of the import profile flow. We also replaced snapshot tests with real tests for the import profile flow files and made useTheme reactive.
  • Updated @testing-library related dependencies and fixed unit tests.
  • Improved test coverage for the recent changes we’ve made.

Next week, our team will continue to work on design improvements and address any outstanding issues reported during testing.

Mainsail Weekly Report

This week, we continued our work on the Validator and Voting contracts within the EVM, along with some additional improvements. Here’s what we accomplished:

  • Evaluated the performance of different sorting algorithms, including bubble, merge, and insertion sorts.
  • Prepared a linked list of top validators and compared its performance with other sorting algorithms.
  • Added vote and voter update logic to the contracts.

We also set up an internal prototype EVM network for testing these contracts, which included:

  • Configuring the network with code changes from a custom repository.
  • Including the consensus contract and initializing it.
  • Adding reward calculations for Validators using Rust.
  • Calling the contract to update the vote balances of the Validators after each block.
  • Retrieving active Validators from the contract.

Next week, we plan to continue testing contract performance and scalability. We’ll also work on improving the prototype network with the consensus and contract changes we’re currently implementing.

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.