<p><em><strong>Welcome to our latest weekly development report, where we spotlight the valiant efforts of our development team. During the past week, our focus was primarily on Dashbrd testing and addressing identified issues. Additionally, noteworthy progress was achieved in the ongoing work on consensus changes by the Mainsail team. Now, let’s dig a bit deeper into the work that’s been tackled this week.</strong></em></p><h2 id="header-0">Development Summary</h2><p>Below is a breakdown of total commits and authors by project for development activity over the last week from the August 11th through August 18th, 2023.</p><p></p><img src="https://academy-public.coinmarketcap.com/srd-optimized-uploads/46fb00cc1d644554aecb8fd512b661cc.png" /><p></p><p>Overall, the team has demonstrated consistent productivity and engagement over this period, with a total of 170 commits across all projects.</p><p>The number of commits and data for each project will fluctuate on a weekly basis depending on internal sprints, objectives and difficulty.</p><h2 id="header-1">ARK Scan Weekly Progress</h2><p>This past week, the entire team was dedicated to advancing the Dashbrd project, which means no significant changes were made to ARK Scan. Since most of the biggest items are now sorted on the Dashbrd, we are determined to maintain our schedule by completing the remaining tasks for the ‘Delegates’ page next week.</p><h2 id="header-2">Dashbrd Weekly Progress</h2><p>This week, a significant portion of our team dedicated their efforts to testing Dashbrd. As a result, several issues were uncovered that require resolution and data optimization prior to the upcoming release. These matters are set to take precedence in the week ahead. Furthermore, we have successfully finished other major tasks, and the development of the Dashbrd landing page has been finalized.</p><p>Here’s a more detailed breakdown of the work accomplished this week:</p><p><strong>Dashbrd General Items</strong></p><ul><li>The design of the navbar and user menu has been improved to enhance the user experience. The navbar now provides easy access to key features, and within the user menu, quick access buttons have been added for ‘Send and Receive,’ ‘My Galleries,’ and ‘My Collections.’ These buttons display precise numbers of galleries created by the user and the number of collections they own NFT in.</li><li>Implemented a maintenance mode feature for the landing page and application.</li><li>Incorporated a Cookie modal and policy, along with a Privacy Policy and Terms of Service pages.</li><li>Resolved Markdown formatting issues present in certain sections.</li><li>Optimized the metadata component for better SEO performance.</li></ul><p><strong>Dashbrd Wallet Items</strong></p><ul><li>Corrected inaccuracies in the market cap and volume data within the wallet table. These figures were inconsistent when compared with the details slider. Additionally, the market cap and volume did not align with the user’s chosen currency. These issues have been resolved.</li><li>Resolved the issue of a non-functional Send button in the mobile view, ensuring its now working properly.</li><li>Resolved issue with incorrect negative percentages.</li></ul><p><strong>Dashbrd Collections &amp; Gallery Items</strong></p><ul><li>Identified and resolved a scenario that would cause a white screen on the collection overview.</li><li>General improvements have been made to the handling of user NFTs in the collection overview.</li><li>Implemented a restriction on storing collection traits exceeding a specific character limit, to avoid showing very large values (e.g. the full Bitcoin whitepaper as a trait).</li><li>Ensured proper display of the NFT Count overlay.</li></ul><p>During the upcoming week, our attention will be directed towards resolving the reported issues that were identified through internal testing, with a primary focus on addressing concerns related to the ‘Collections’ feature.</p><h2 id="header-3">Mainsail Weekly Progress</h2><p>During this week, there were notable advancements in Mainsail’s consensus domain, along with enhancements in the transaction pool and block verification areas. Here are the specific developments:</p><ul><li>Transaction pool replay was modified to use the transaction index instead of the transaction ID. This adjustment eliminates the need to deserialize the buffer in certain cases.</li><li>Block verification has been improved. The node verifies the aggregated signature on the committed block and confirms that sufficient validators have signed the precommit message for that block.</li><li>Consensus now reevaluates all rounds during the bootstrap phase, not exclusively the final one. A block is considered committed when over two-thirds of valid precommits and a valid proposal are received for any given round.</li><li>Verification of lock proposals has been shifted to the proposal processor. The processor aims to promptly address invalid messages in the initial stages to prevent malicious peers, thereby banning them upon detection of invalid messages.</li><li>The methods isMajority and isMinority have been extracted as standalone functions, as they are utilized across multiple locations.</li><li>A new environment variable, CORE_P2P_PEER_BAN_TIME, has been introduced to establish the duration of peer bans. Peer banning is deactivated by default.</li></ul><p>Moving into the upcoming week, our focus will shift toward researching potential database and public API implementations. This effort aims to enhance data readiness. Concurrently, we will assess the test network that has been established, addressing any issues uncovered during the testing phase.</p><h2 id="header-4">Feedback &amp; Feature Requests</h2><p>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.</p><p>Quick access links to GitHub issues pages:</p><ul><li><a href="https://github.com/ArkEcosystem/mainsail/issues" rel="noopener noreferrer nofollow">Mainsail </a></li><li><a href="https://github.com/ArdentHQ/arkscan/issues" rel="noopener noreferrer nofollow">ARK Scan </a></li><li><a href="https://github.com/ArdentHQ/arkvault/issues" rel="noopener noreferrer nofollow">ARK Vault </a></li><li>Dashbrd <em>(coming soon)</em></li></ul><h2 id="header-5">What’s Next</h2><p>As we look forward to the coming week, our main aim is to stay on track with thoroughly testing Dashbrd and tackling any bugs that popped up this week and the next. Additionally, we will continue on the ongoing work for ARK Scan, with the goal of wrapping up the ‘Delegates’ page redesign.</p><p><em><strong>Follow us on <a href="https://twitter.com/ArkEcosystem" rel="noopener noreferrer nofollow">X </a> 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.</strong></em></p>

ARK Development Report - August 18, 2023

Table of Contents

ARK Ecosystem

Other articles published on Aug 18, 2023

Hoskinson Fires Back at Critic for Demeaning the Cardano Network

Kaspa (KAS) Plummets: Time to Evaluate the Real Value Proposition

Ripple Partners With Mastercard, While XRP Price Falls Below Crucial Level

Bitcoin Plummets to $25K, Catalysing $1 Billion in Liquidation

Ethereum surges 11% after report SEC is set to approve Futures ETF

Everything To Know About Contracts For Difference (CFD)

Join our free newsletter for daily crypto updates!