ARK Development Report - February 16, 2024

By ARK Ecosystem
2 months ago

Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week, we’ve rolled out a new version of ARK Scan, featuring enhancements in price caching and ‘send to self’ functionality. Additionally, we’ve been refining the drafting process for an upcoming WebSockets feature. The Mainsail team has been hard at work crafting documentation and further optimizing the codebase.

Development Summary

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

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

During this week, we released a new minor version of the ARK Scan , which incorporates the following updates:

  • Simplified crypto stats decimals to improve clarity.
  • Adjusted cached pricing and developer commands to enhance operational smoothness.
  • Improved user interface for the multipayment ‘sent to self’ feature.

For a comprehensive overview of the modifications, please refer to our Changelog .

In the upcoming week, we will continue our focus on drafting the necessary changes for the addition of WebSockets to ARK Scan.

Mainsail Weekly Progress

During this week, we focused on optimizing the codebase, enhancing the install script with additional features, and continuing documentation efforts. Here are the specific updates:

  • Removed the api-sync and api-database packages from the default testnet app.json. This simplifies the project’s initial setup for new users, eliminating the requirement for an active PostgreSQL instance.
  • Renamed PM2 process names to mainsail and mainsail-api.
  • Consolidated ENV variables into a single file, accessible for users to review all variables used in the project.
  • Removed the necessity of flags for token and network, resulting in shorter and more legible commands. For instance, the command mainsail env:list --token=ark --network=testnet is now mainsail env:list. Additionally, mainsail folder paths no longer include token or network namespaces. For example, the data path has been updated from ~/.local/share/ark-core/testnet/mainsail to ~/.local/share/mainsail. This restructuring reflects the common usage of a single network by users.
  • Enhanced the install script to support mainsail and mainsail-api installations alongside the PostgreSQL instance.
  • Updated the script to support Docker setups, to be executed from the Docker host.

Next week, our focus will be on finalizing documentation for public release and commencing the last preparations for the initial public 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:

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.

Related News