<p><em><strong>Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. ARK Scan has been focusing on EVM compatibility, while the ARK SDKs and Docs teams have been expanding the documentation. The ARK Vault team has been diligently addressing bugs reported by the QA team and finalizing a few remaining design changes. Mainsail has made progress on the Consensus contract, implemented a new internal EVM test network, and worked on additional fixes and features.</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 October 11th through October 18th, 2024.</p><img src="https://academy-public.coinmarketcap.com/srd-optimized-uploads/6e079ce454f446e48455184343de7379.png" /><p>Overall, the team has demonstrated consistent productivity and engagement over this period, with a total of 146 commits across all projects.</p><p>The number of commits and data for each project will fluctuate every week depending on internal sprints, objectives, and difficulty.</p><h2 id="header-1">ARK Scan Weekly Report</h2><p>This week, we continued focusing on making ARK Scan compatible with the latest changes in Mainsail, primarily related to EVM. The work completed includes:</p><ul><li>A block was added to display input data in EVM transactions. This block will include additional information, such as the payload and contract method being called.</li><li>Updated the Validator Monitor to work with recent EVM changes, fixing issues related to the lingering generator_public_key from Slots and related files while Mainsail now relies on generator_address.</li><li>Adjusted productivity caching by public key.</li><li>Modified WalletCache entries to store data by address to handle the change to validators, as that’s how it gets stored in the database.</li><li>Implemented payload output formatting for code blocks.</li></ul><p>Next week, we will continue working on EVM compatibility and add new features required to properly display information.</p><h2 id="header-2">ARK SDKs and Docs Weekly Report</h2><p>We’ve been focusing on expanding documentation and introducing new design elements. This week’s progress includes:</p><ul><li>Added PHP receipts to public API documentation.</li><li>Introduced new PHP unit converter documentation.</li><li>Added EVM call builder documentation.</li><li>Completed JSON-RPC API documentation.</li><li>Removed the green pattern background from the new homepage.</li><li>Added a ‘Clients’ documentation link to the main navigation bar.</li><li>Cleaned up outdated documentation by removing references to Ruby and Elixir, eliminating the feedback component, and removing the ‘Login’ button and unused navigation links.</li><li>Updated the crypto libraries documentation to reflect the latest changes and additions.</li></ul><p>Next week, we will continue refining the new homepage design and writing additional documentation as new features are added to the crypto and client packages.</p><h2 id="header-3">ARK Vault Weekly Report</h2><p>Our team has been working diligently on the latest design updates and addressing issues reported by the internal testing team. The work completed this week includes:</p><ul><li>Adjusted the height of the amount label to the correct size.</li><li>Corrected the design of the “View More” button on the transaction tables.</li><li>Fixed label size in the mobile view of the pending transaction row.</li><li>Removed duplicate tooltips in the transaction row.</li><li>Improved alignment in the pending transaction table.</li><li>Fixed the focus state in the “Recipient Search” modal for smaller breakpoints.</li><li>Refactored the pagination design to align with the ARK Scan style.</li><li>Corrected the transaction amount label based on the transaction type.</li><li>Adjusted font sizes for multiple recipient labels.</li><li>Scoped hover states in the link component using an inner group.</li><li>Adjusted colors for the transaction ID explorer button.</li><li>Replaced “Second Signature” with “2nd Signature” for consistency.</li><li>Fixed alignment issues in the vote transaction review step.</li><li>Reduced button sizes in the sign message form.</li><li>Corrected alignment and font sizes across the recipient search modal, wallet search table, amount labels in transaction details, and wallet addresses in the transaction table.</li><li>Fixed sender address color for incoming transactions.</li><li>Enabled the transaction explorer link for confirmed transactions.</li><li>Adjusted alignment for pending and successful steps in transactions, review steps, wallet header items, the “Create Wallet” checkbox, and the vote button.</li><li>Corrected the font size and weight of the amount label and total amount in the transaction summary.</li><li>Fixed colors for the recipient address, disabled the send button in the wallet list, and tab borders in dark mode.</li><li>Fixed an issue where the addressing column displayed incorrect information in the pending transactions table.</li><li>Resolved an issue where the dropdown text in the pagination overlapped with itself.</li><li>Adjusted the height of the mobile navigation bar.</li><li>Fixed padding in the portfolio header and breakdown sections.</li><li>Corrected the color of the dashboard filter icon.</li><li>Implemented truncation in the recipient dropdown list.</li><li>Aligned the IPFS send flow UI with the designs.</li><li>Updated the select caret icon according to design specifications.</li><li>Adjusted paddings in the mobile select dropdown.</li><li>Added pagination to the portfolio overview, defaulting to 10 wallets displayed.</li><li>Updated snapshots and restored failing tests and coverage.</li></ul><p>Next week, we’ll continue resolving any reported issues from our QA and internal testing teams as we prepare to finalize this design update ahead of the general release.</p><h2 id="header-4">Mainsail Weekly Report</h2><p>This week, we continued working on our internal EVM testnet, implementing optimizations and fixes. We also made additional changes to align the EVM more closely with its specifications and worked on the consensus contract. The work completed this week included:</p><ul><li>Consensus contract updates:Added votersCount to ValidatorData.<br />Implemented the unvote function.<br />Added Unvoted, ValidatorRegistered, and ValidatorResigned events.<br />Introduced onlyOwner and preventOwner modifiers.<br />Improved the resignation logic.<br /></li><li>Other Mainsail work included:Synced all validators from the Consensus contract to Mainsail. Calculated the list of dirty validators on ValidatorSet, which are synced to PostgreSQL.<br />Restored validator attributes and included them in the API response: vote, validatorVoteBalance, validatorVotersCount, validatorLastBlock, validatorForgedFees, validatorForgedRewards, validatorForgedTotal and validatorProducedBlocks.<br />Added wallets_validators index.<br />Prepared update_validator_ranks SQL function to calculate validator rank.<br />Fixed /rounds controller.<br />Fixed /block controller to query the block at height 0.<br />Fixed /fees controller.<br />Fixed invalid totalRound calculation in the bootstrapper.<br /></li></ul><p>Next week we plan to focus on refactoring transactions to match the Ethereum format and developing the PostgreSQL database restore feature. We’ll also monitor our internal testnet and address any issues that arise. Additionally, we’ll publish a blog post with more details about the EVM integration.</p><h2 id="header-5">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/arkconnect-extension/issues" rel="noopener noreferrer nofollow">ARK Connect (Extension) </a></li><li><a href="https://github.com/ArdentHQ/arkconnect-demo/issues" rel="noopener noreferrer nofollow">ARK Connect (Demo) </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></ul><h2 id="header-6">Follow on Twitter (X)</h2><p>Follow us on <a href="https://x.com/ArkEcosystem" rel="noopener noreferrer nofollow">X </a> (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.</p>

ARK Development Report - October 18, 2024

Table of Contents

ARK Ecosystem

Other articles published on Oct 18, 2024

Binance Labs's Latest Investment: What Is Lombard Finance?

These Under-$1 Altcoins Could Be Bigger Than Cardano by 2026

Sui Foundation Denies Insider Trading Allegations Amid $400M Token Sale Claims

Weekly Article Recap: 10/07-10/11

Gold Hits New High, Bitcoin Struggles – What Is the Better Buy?

Tapioca DAO hit by $1.6 million hack

Join our free newsletter for daily crypto updates!