<p><em><strong>Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. The ARK Scan team has been working on recent EVM changes to ensure compatibility. The ARK SDKs team has focused on updating Go packages (client and crypto) and has also worked on improving the API documentation for those packages. The ARK Vault team has continued to make design improvements. The Mainsail team successfully launched the initial EVM network, which includes new Validators and Voting contracts, and has made further improvements to the EVM.</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 September 27th through October 4th, 2024.</p><img src="https://academy-public.coinmarketcap.com/srd-optimized-uploads/ec4a1eb2fc1043e4bb8a4def6bd0cc74.png" /><p>Overall, the team has demonstrated consistent productivity and engagement over this period, with a total of 171 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’ve been focusing on ARK Scan, outlining the necessary adjustments to accommodate the changes introduced by Mainsail’s EVM support. We’ve started a new branch based on the current Mainsail development branch to serve as the foundation for these updates. Our primary focus has been adding support for 18 decimal points and Keccak addresses support, a requirement for EVM compatibility. Once the initial EVM support is in place, we’ll resume upgrading Laravel to the latest version.</p><p>Next week, we’ll continue enhancing ARK Scan with additional EVM support, enabling more thorough testing of the EVM changes.</p><h2 id="header-2">ARK SDKs &amp; Docs Weekly Report</h2><p>This week, we focused on the Go packages (client and crypto) to support Mainsail. Here’s what we worked on:</p><ul><li>Refactored issues with broadcast transactions:Made the serialize method public (required for sending serialized transactions).<br />Fixed incorrect GetFee logic.<br />Added methods for building username registration/resignation.<br /></li><li>Updated Go client packages for Mainsail support.</li><li>A configurable host option for go-client was added.</li></ul><p>We also made progress on the Go documentation, adjusting public API docs and updating crypto-related Go docs. Additionally, we worked on design changes for the new documentation site.</p><p>Next week, we plan to finalize the necessary changes to the Go packages and continue working on the new docs website.</p><h2 id="header-3">ARK Vault Weekly Report</h2><p>This week, we continued updating UI elements across the app. Here’s what we completed:</p><ul><li>Updated the 2nd signature creation and review pages:Added an icon in the title section for each step.<br />Modified the UI to match the new design.<br />Reorganized data to align with other pages.<br /></li><li>Updated the delegate resignation creation step:Added an icon in the title section for each step.<br />Modified the UI to match the new design.<br />Reorganized data to align with other pages.<br /></li><li>Updated pending and success steps for the multisignature transaction flow:Added icons to each step.<br />Refactored the data structure to match other pages.<br />A new model for the signing steps was added.<br />Updated designs for all steps, including new layouts for pending and signed signees.<br /></li></ul><p>With these changes, only a few more pages need updating to match the new designs, which we’ll focus on next week. We’ve also started revising the ‘Exchanges’ design flow based on feedback from users who encountered issues. Once these updates are complete, we’ll begin thorough internal testing.</p><h2 id="header-4">Mainsail Weekly Report</h2><p>This week, we launched the initial testnet with full EVM support, including Validators and Voting as part of the EVM. This will be the foundation we build on going forward. The work completed this week includes:</p><ul><li>Refactored transaction pool:Added checks for sender’s balance and nonce. It now reads the actual balance and nonce from the EVM on new transactions to create the sender’s state.<br />Simplified the transaction pool logic and removed unnecessary code.<br />Only the affected transaction senders are passed to the worker, which avoids transaction deserialization in the worker. All transactions for the affected sender are reapplied after commit. Re-adding transactions is now cheaper since only balance and nonce checks are done.<br />Added logic to revert transactions for expired and removed ones. On revert, the nonce decreases, and the balance is restored to the sender’s state.<br /></li><li>Implemented the start handler for evm-api-worker and transaction-pool worker. The start method sets the latest height, resets transactions, and loads the correct milestones. The API server boots up after initialization is complete, ensuring it serves accurate data. Instead of passing the entire block on every commit, only the new height is passed to the workers to avoid deserialization.</li><li>Removed EVM mock instance. Transactions in the pool no longer call the apply transaction handler, so the mock instance is no longer necessary. Transactions are processed when they are included in the block and when the block is processed.</li><li>Removed unused milestones:multiPaymentLimit: Since we can’t control the payment logic in applied contracts, limiting max payments no longer makes sense.<br />nativeGasLimits and fees: These are no longer needed because native transactions were removed.<br /></li><li>Transaction apply now returns TransactionReceipt.</li><li>Restored crypto-signature-ecdsa, which will be used for transaction signing.</li></ul><p>Next week, we’ll continue working on general EVM improvements and fixes based on feedback from other teams who will start integrating these changes into user-facing apps. We’ll also refactor transactions to match the ETH format and make further API improvements.</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 4, 2024

Table of Contents

ARK Ecosystem

Other articles published on Oct 5, 2024

FXGuys’ Game-Changing Trading Rewards: Can It Outperform Ethereum?

Weekly Article Recap: 9/23-9/27

Crypto: The SEC Drops Ripple (XRP) By +15%!

Qubetics Making Waves In The Crypto Market Alongside Arweave and Avalanche

Top 3 Solana-Based Memecoins to Watch Next Week: WIF, POPCAT, or BONK—Who Will Lead the Rally?

EigenLayer says $5.7M hack ‘isolated’ incident, no vulnerability on protocol

Join our free newsletter for daily crypto updates!