Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. The ARK Scan team has continued working on the initial set of required changes for EVM compatibility. In the ARK SDKs, additional support for EVM changes has been added to the PHP client. The ARK Vault team has been focusing on design updates and user experience improvements to the ‘Exchanges’ flow. Meanwhile, the Mainsail team has fixed some of the reported issues and implemented further optimizations to the newest EVM testnet.
Development Summary
Below is a breakdown of total commits and authors by project for development activity over the last week from October 4th through October 11th, 2024.
Project | Commits | Authors |
---|---|---|
ARK Connect | 0 | 0 |
ARK Scan | 22 | 2 |
ARK SDKs & Docs | 7 | 1 |
ARK Vault | 54 | 2 |
Mainsail | 27 | 2 |
Overall, the team has demonstrated consistent productivity and engagement over this period, with a total of 110 commits across all projects.
The number of commits and data for each project will fluctuate every week depending on internal sprints, objectives, and difficulty.
ARK Scan Weekly Report
We’ve continued working on the EVM changes required to display the initial set of data and ensure it works properly with Mainsail’s EVM updates. Work completed this week includes:
- Merged changes from
mainsail-evm
intomainsail-develop
, which will, for now, serve as the primary development branch. - Added a new column to the database and updated the models to reflect the revised structure. For example, blocks now include a
total_gas_used
field, among other changes. - Displayed the list of validators (active, standby, resigned) based on the smart contract.
- Began work on the EVM transaction details page, starting with the “More Details” section for smart contracts.
Next week, we will continue integrating the EVM to ensure basic data is displayed correctly for testing.
ARK SDKs & Docs
This week, we have been working on additional PHP client changes and tests required for recent updates, which include:
- Added JSON-RPC handling support for the PHP client.
- Added a
/receipts
endpoint for the PHP client. - Added EVM transaction support to the transaction tester for PHP.
Next week, we’ll monitor if any further changes are needed for EVM support in any of the packages and continue our work on the new documentation site.
ARK Vault Weekly Report
On ARK Vault, we’ve continued working on UI updates throughout the app. Work done this week included:
- Implemented new notifications design for incoming and outgoing transactions.
- Updated the ‘Sign Message’ and ‘Verify Message’ flow with new design elements.
- Adjusted address creation success step design.
- Made user experience improvements, as well as design updates to the ‘Exchanges’ functionality, based on user feedback. Many users struggled with initiating exchanges, not realizing they needed to send tokens to the provided address, so we made adjustments to better guide them.
- The loading state of the Welcome page still showed the skeleton UI of the old Welcome page. We can adjust this to reflect the new UI.
- Adjusted welcome slider speed on the homepage to give users more time to read a slide.
- Aligned skeleton table column widths with the normal view.
- Fixed the size on pending transaction ‘From’ / ‘To’ labels.
- Added a basic transition (similar to button hovers) to the profile selection so the hover change isn’t instant anymore.
- Added a missing back button hover state on the profile import page.
- Fixed a missing border on the portfolio page’s table when transaction history is enabled in the Settings.
- Updated the profile creation flow so that when a user enters a password, the checklist and text turn blue instead of green.
- Fixed the chevron icon state so it displays correctly.
- Reduced the entry height of the ID field on the transaction details page.
- Reduced paddings between fields on the settings page.
Next week, we aim to finalize most of the tasks related to UI updates, ramp up testing of recent changes, and fix any issues that get reported.
Mainsail Weekly Report
This week, we focused on the newest internal Mainsail network with EVM support and addressed several internally reported issues. The work completed includes:
- Reset the internal testing network with the latest breaking changes.
- Fixed a potential panic caused by unhandled execution results when a transaction reverted.
- Refactored the transaction layout and adopted RLP encoding for signing and hashing.
- Repopulated the public key column in the wallets table.
- Adjusted the bootstrap order to ensure the state is updated before reading milestones.
Next week, we will concentrate on improving and fixing APIs required for our front-facing applications (ARK Vault and ARK Scan). This will allow the rest of the development team to focus on integrating EVM support. Additionally, we’ll be working on smart contract updates and optimizations.
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 (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.