Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. This week includes a huge milestone for the team with the release of Dashbrd!! We have also continued our efforts on ARK Scan and the Mainsail team has made significant progress in their ongoing work related to consensus and API. Let’s get into the details.
Below is a breakdown of total commits and authors by project for development activity over the last week from August 25th through September 1st, 2023.
Overall, the team has demonstrated consistent productivity and engagement over this period, with a total of 157 commits across all projects.
The number of commits and data for each project will fluctuate on a weekly basis depending on internal sprints, objectives and difficulty.
Dashbrd Weekly Progress
We’re thrilled to announce that the Dashbrd beta is now available!
You can test the beta now at Dashbrd.com .
The entire team at Ardent has put in a ton of effort building Dashbrd and we are excited to share it with you. What makes Dashbrd truly unique is its open-source nature, making it the first of its kind in the market. Not only can you try out the beta right now, but you can fork, steal, copy, or contribute to your heart’s desire. All we ask is that you stick to the GPL license. In this way, we believe we can encourage even more active participation from Web3 enthusiasts and empower the community to build together.
For those eager to explore further, here are some essential links you might find interesting:
- Dashbrd.com - The main website of the Dashbrd app.
- GitHub Repository - Feel free to raise issues, engage in discussions, and show your support by starring the repository.
- X / Twitter Account - Stay updated by following Dashbrd on X / Twitter.
- Discord Server - Join the Dashbrd Discord server to stay connected with the latest updates and become an active part of our community.
Be sure to also read Ardent’s release blog for a more comprehensive overview of this exciting milestone.
The Ardent team has a ton of additional features in the works and they can’t wait to get your feedback to help them steer the future direction of Dashbrd. Make sure you check it out and congratulate them on their big milestone!
ARK Scan Weekly Report
This week, we started work on enhancing the dedicated transactions and blocks pages. These updates will introduce a unified table design and incorporate additional statistics that may be of interest to end-users. Furthermore, we have addressed reported issues on the delegates page. To delve into more specific details:
- We introduced a new design for the blocks and transactions tables to ensure consistency with other pages.
- Implemented information boxes displaying statistics related to blocks and transactions, offering users valuable insights.
- Added a transaction table filter feature, enabling users to tailor their view based on specific criteria.
- Resolved an issue where pagination settings were reset upon page reload.
- Ensured proper pagination display during the loading state.
- Improved user experience by displaying delegate usernames instead of addresses in the voters’ table when an address is associated with a delegate.
- Enhanced the visual representation of ‘From’ and ‘To’ hover colors in light mode.
- Optimized the loading speed of the transactions table for improved performance.
In the upcoming week, our focus will be on completing all outstanding tasks related to the transactions and blocks pages as well as conducting thorough QA testing before the release.
Mainsail Weekly Report
During this past week, our Mainsail team continued their efforts to refine the consensus process. They also began work on API changes and addressed any issues that surfaced during this process. Here is a more detailed breakdown of the tasks accomplished:
- Redundant data fields, specifically blockId and height, were removed from the
IBlockCommit. This change was made due to the accessibility of this information within the block data itself, contained within
- The verification process for aggregate signatures of committed blocks was shifted from the block processor to the
CommittedBlockProcessorwithin the consensus package. This restructuring separates block-related logic, handled by
BlockProcessor, from consensus-related logic, now managed by
- The implementation of
CommitLockwas completed. This feature facilitates critical state changes during the commit phase, such as height adjustments, wallet updates, and validator set modifications. Verification processes dependent on the state can be executed in parallel, either preceding or following the commit stage.
- The deserialization of messages was relocated from the consensus module to the P2P component. P2P handlers now conduct basic data verification on received messages. If the received data is invalid or missing, the respective peer is blocked.
- Several minor fixes were applied to the P2P system to enhance its functionality.
- The existing API package has been renamed as api-development, reserving the API package designation exclusively for production API logic.
- The initial implementation of the public API has been initiated, encompassing blocks and transactions tables.
In the upcoming week, our objectives include further extending the API implementation based on predefined specifications and enhancing block processing. Additionally, we are actively monitoring the limited testnet, promptly addressing any issues as they arise during testing.
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 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.