Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. The ARK Scan team has made further progress on EVM support and integration. Additionally, we’ve been extending EVM support in the Platform SDK and other SDKs. The ARK Vault team has been focused on implementing Mainsail EVM support, while the Mainsail team has worked on enhancing Core V3 data import functionality and adding RLP support.<h2 id="header-0">Development Summary</h2>Below is a breakdown of total commits and authors by project for development activity over the last week from December 6th, 2024 through December 13th, 2024.<img src="https://academy-public.coinmarketcap.com/srd-optimized-uploads/e081e56905674d02bb6ba77ebcbbc295.png" />Overall, the team has demonstrated consistent productivity and engagement over this period, with a total of 288 commits across all projects.The number of commits and data for each project will fluctuate every week depending on internal sprints, objectives, and difficulty.<h2 id="header-1">ARK Scan Weekly Report</h2>This week, our primary focus remained on advancing Mainsail EVM support and integration, with significant progress made on various tasks:<ul><li>Tests &amp; Fixes:Fixed block table tests &amp; transaction factory encoding. Resolved an issue where transaction controller tests were not displayed. Fixed and updated:Transactions controller tests Block view model tests Webhook controller tests Cache fees command tests Cache validator tests DTO tests Webhook jobs test Failing model tests Transactions view model tests </li><li>Library Updates:Moved selected methods to the php-crypto library. </li><li>New Tests Added:Transaction historical fee aggregates. Home transactions. Statistics components. Transaction validators header stats. Recent votes. </li><li>UI Enhancements:Added contract deployment method as a type in the user interface. </li><li>Miscellaneous Fixes:Fixed data stream issue when creating multiple records through factories. Export blocks now use the address instead of the public key. Renamed the recipient_id column in the transaction repository. Resolved a 500 error caused by failed token transfers. Output username for username registration transactions, showing the username in the “action” section. Updated the failed status icon to display properly for failed transactions. </li><li>Performance Improvements:Refactored the filter query for transaction types to load much quicker. </li></ul>Looking ahead, we will continue enhancing EVM integration, refining tests, and addressing any newly reported issues related to the integration.<h2 id="header-2">ARK SDKs and Docs Weekly Report</h2>This week, our primary efforts focused on advancing the Platform SDK along with updates to supporting libraries and docs site:<ul><li>Platform SDK:Refactored to use an empty string (&#34;&#34;) for transfer transactions due to API inconsistencies. Removed VendorField (memo) logic as it is not part of EVM specifications. Updated to use the method name hash as the type for non-predefined transactions. Adjusted voting methods for the Mainsail network to align with its naming conventions (e.g., vote swaps now appear as votes). Unsupported transaction types were removed from the signed transaction class. Fixed fee unit display in signed and confirmed transaction DTOs. </li><li>Documentation site: Added new documentation for:PHP argument decoder. Java Crypto SDK, including recent EVM-related additions. </li><li>PHP Crypto Library: Refactored the argument decoder:Made methods static. Added support for unit conversions (wei, gwei, ark). Improved helper methods and resolved style violations. Added a string-decoding method. Removed deprecated and obsolete code. </li><li>Python Crypto Library:Updated transaction builders and added ABI encoding/decoding. Removed deprecated functionality. Improved serializers/deserializers. Made extensive test adjustments. </li></ul>Next week, we will continue making the necessary changes and enhancements for EVM integration and further improve project documentation.<h2 id="header-3">ARK Vault Weekly Report</h2>This week our primary focus was on enhancing EVM support and addressing issues identified during internal testing:<ul><li>Validator Enhancements:Worked on EVM validator registration/resignation methods and refactored to use “validator” terminology instead of “delegate.” The validator public key is now displayed instead of the name, as a username is no longer required for validator registration. Updated the vote domain to use “validator” instead of “delegate.” Adjusted the “Validator Name” column title to “Validator” on the votes page. Added validator address display in the wallet voting section. Added the ability to show the validator address in the vote flow. </li><li>EVM-Specific Changes:Removed the memo field across the app, as it is not part of EVM. Transactions can now support up to 18 decimals for networks configured as Mainsail EVM, instead of being capped at 8 decimals. </li><li>UI Improvements:Failed transaction status is now displayed in the “Confirmed Details” modal. Transactions that are not of predefined types now display their method names. </li><li>Refactoring Components: Refactored components using emotion:Common reusable components starting with letters A to I. Wallet, Vote, Form, Input (text, textarea, radio), and Navigation components. Removed emotion or twin.macro dependencies, including css(), tw(), and styled() functions. Introduced a new media query in the Tailwind config for devices that support not all and (hover: none). Replaced small, non-exported components with simple HTML tags. Removed dozens of unused components. </li><li>Transaction Fixes:Refactored contract deployments to be treated as contract transactions. Fixed signed transaction type lookup, ensuring proper transaction signing. Addressed an issue in transfer transaction rows:Added validation to check if a transaction is not mistakenly identified as a contract. Correctly displays the “To (Contact) [Address]” information. </li></ul>We’ll continue to improve EVM integration and implement the required UI changes.<h2 id="header-4">Mainsail Weekly Report</h2>This week we continued working on V3 import functionality and adding RLP support. Here’s a summary of the progress:<ul><li>Legacy Second Signatures:Added partial support for legacy second signatures. Wallets with secondSignature are imported, and the second signature is stored on the EVM account. </li><li>Legacy Multi-Signatures:Added partial support for legacy multi-signatures. </li><li>Database Service Fix:Resolved an issue with the database service to use the correct height when fetching the last commit. </li><li>Transaction Serialization and Deserialization:Updated the transaction serializer and deserializer to use RLP (Recursive-Length Prefix). Transactions are now compatible with Ethereum EIP-1559, with the following differences:access_list: Always set to an empty array ([]) since REVM does not support this field. Fee Strategy: Mainsail does not use the same gas fee strategy as Ethereum (GasFee and PriorityFee).maxPriorityFeePerGas is always 0. Mainsail uses max_fee_per_gas as gasPrice. Transaction fee is calculated as max_fee_per_gas * gasUsed and added to the generator balance instead of being burned. </li></ul>Next week, we will focus on adding new JSON_RPC methods to the EVM API and updating the TX tools to simplify testing and incorporate support for the latest changes.<h2 id="header-5">Feedback &amp; Feature Requests</h2>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:<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>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.

ARK Development Report - December 13, 2024

Table of Contents

ARK Ecosystem

Other articles published on Dec 13, 2024

Bitcoin Hashrate Hits New Peak as Price Breaks Through $100K

WRX Token Soars 50% in an Hour! Why a Surge?

The XRP Bull Run Has Barely Begun, Analyst Draws 2017 Parallels

PEPE and BONK Beware: The Next Big Meme Coin Is in Presale With a Growth Forecast

Hedera Empowers Zoniqx to Transform Real-World Asset Ownership with Blockchain

Homo Shiba Inu (HOMOSHIB) Will Surge Over 15,000% Before Exchange Listings, While Shiba Inu and D...

Join our free newsletter for daily crypto updates!