Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team. The ARK Scan team has completed the Livewire update and is progressing with the Laravel update. The ARK Vault team is focused on ongoing design tasks. For ARK SDKs, we are advancing work on the Go packages, while the Mainsail team continues to make improvements to EVM.
Development Summary
Below is a breakdown of total commits and authors by project for development activity over the last week from September 20th through September 27th, 2024.
Project | Commits | Authors |
---|---|---|
ARK Connect | 0 | 0 |
ARK Scan | 9 | 1 |
ARK SDKs & Docs | 59 | 2 |
ARK Vault | 73 | 3 |
Mainsail | 26 | 2 |
Overall, the team has demonstrated consistent productivity and engagement over this period, with a total of 167 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
This week, we finished updating Livewire to the latest version and continued working on making the codebase compatible with the latest version of Laravel. Additionally, we started designing the initial EVM transaction page, which will include new data such as Gas Information, Payload, and other transaction attributes.
Next week, we plan to complete the Laravel compatibility upgrade and begin focusing on the EVM changes required by the latest Mainsail updates.
ARK Vault Weekly Report
This week, we made several updates to the app’s design:
- Adjusted the Portfolio table design to align with other parts of the app.
- Redesigned the camera permission denied alert, introducing a new warning-dark variant and updating button colors.
- Made changes to the transfer transaction details, including:
- Moving the transaction ID to the top.
- Updating the design to match ARK Scan.
- Grouping relevant data for easier user understanding.
- Fixed minor issues with the transaction table:
- The grey column header now extends to the border on screens 1024px and larger.
- The alias width for the receiver is now correct on tablet screens.
- Padding for the table has been fixed (it was missing after the last update).
- Updated Registration transactions to follow the new transaction history designs.
- Redesigned step 1 of the Multisignature transaction (Create transaction).
- Fixed the width of the Select Sender/Recipient/Participant search bar on mobile view.
- Fixed the border and padding for transaction labels in dark mode.
- Refactored the ‘Show All Wallets’ page to follow the new UI designs.
- Fixed an issue where the dropdown wasn’t visible in the wallet list table.
- A thicker bottom border was added to the wallet list table.
Next week, we plan to finalize the ARK Vault redesign and address any issues found during further testing.
ARK SDKs & Docs Weekly Report
This week, the focus has been on finalizing Go packages (client
and crypto
) to include Mainsail support. Key work on Go included:
- Added support for BLS keypair generation & validation
- Adjust the client to allow for configurable hosts to match the Mainsail API
We have also been working on the documentation for these Go changes, which will be featured on the new documentation page. Additionally, we’ve designed an updated homepage for the documentation site.
Next week, we’ll finalize the Go package changes and begin work on the new documentation homepage.
ARK Mainsail Weekly Report
This week, we’ve been focused on improving the EVM implementation. Here’s what we’ve worked on:
- Removed most of the state logic, including snapshots, wallet repositories, attributes, and wallet indexes.
- The EVM API now reads account balances and nonces directly from the EVM, instead of the wallet repository.
- Updated Rust dependencies for the EVM package.
- Stored full receipts in the EVM store.
- Re-enabled API database sync after state refactoring.
- Added Foundry and Solidity contracts under the
/contracts
folder.
Next week, we plan to address transaction pool issues and handle transactions with the recent EVM updates. We’ll also deploy an initial internal test network with native EVM transactions, including contracts for Validators and Voting.
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.