Welcome to our latest Weekly Development Report, where we spotlight the valiant efforts of our development team.The ARK Scan team continued implementing changes needed for Mainsail’s EVM integration. On the SDK side, we’ve also made further updates to the Platform SDK (PSDK) to support EVM, alongside progressing with design improvements for the new documentation site. Meanwhile, the ARK Vault team has been addressing issues reported by our community and identified internally from the latest release, and the Mainsail team has been focused on API and EVM enhancements.
Development Summary
Below is a breakdown of total commits and authors by project for development activity over the last week from November 1st through November 8th, 2024.
Project | Commits | Authors |
---|---|---|
ARK Connect | 0 | 0 |
ARK Scan | 38 | 1 |
ARK SDKs & Docs | 22 | 3 |
ARK Vault | 126 | 3 |
Mainsail | 18 | 3 |
Overall, the team has demonstrated consistent productivity and engagement over this period, with a total of 204 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’ve continued working on EVM compatibility for Mainsail, addressing reported issues, and implementing design updates for upcoming changes. Here’s a summary of what was accomplished:
- A “Copy Code” feature was added to the transaction payload data box.
- Updated the code block tab design in the data box.
- Additional identifiers for methods within code blocks were added.
- Refactored statistics cache to use gas price instead of fees.
- Transaction filters were removed due to differences in EVM data handling.
- Fixed a wallet page error caused by recent database structure changes in the transactions table.
- Resolved transaction error in the
CacheUsernames
job. - Fixed transaction error in Scout Import, where changes to transaction columns prevented model synchronization with Meilisearch.
- Removed validator registration scope for the
cache networks
command.
Next week, we’ll continue working on EVM-related changes for Mainsail and address any new issues identified during testing.
ARK SDKs and Docs Weekly Report
This week, we focused on additional Platform SDK (PSDK) changes to support EVM compatibility and working on documentation design updates. Here’s a summary of the progress:
-
PHP Crypto SDK Updates
- Started on adjusting signatures to make use of ECDSA to match the new Mainsail EVM signatures
-
Platform SDK Updates
- Added support for multiple types in the transactions query.
- Refactored
isReturn
andtotal
methods for the signed/unconfirmed transaction class in PSDK to align with the confirmed transaction class API. - Adjusted handling of amounts and transaction directions for unconfirmed musig transactions, ensuring they are managed from the sender’s perspective.
- Fixed an issue where the typegroup was incorrect when filters included both Core and Magistrate transaction types.
- Corrected filtering for transfer transactions.
-
Documentation Site Design
- Implemented additional design updates for the upcoming documentation site.
Next week, we’ll continue with PHP SDK adjustments, refining the PSDK for EVM support and further enhance the design of the documentation site.
ARK Vault Weekly Update
This week, our work focused on resolving bugs and issues reported by our internal team and community members (thank you for the reports) from last week’s release of the ARK Vault, along with advancing specifications for EVM changes:
- Reused components in the musig registration review step to align with other transaction types.
- Handled sent-to-self cases for multipayment and return transactions to match ARK Scan.
- Refactored handling of totals and sent-to-self for unconfirmed transactions.
- Fixed an issue where the nonce on the transaction confirmation screen displayed as N/A.
- Corrected the sent-to-self label when the sender’s wallet address is also the recipient, including in multipayment transactions.
- Refactored button styles by removing
roundedClassName
andsizeClassName
props, usingclassName
instead. - Added wallet transaction total count in wallet tabs.
- Refactored to use transaction methods for extracting voting information.
- Updated hover styles for buttons and links to match the design, including:
- New navy and green variants for style adjustments based on the selected palette.
-
StarFilled
SVG refactored for color management of fill and stroke. - Updated homepage profile button hover styles.
- Updated the ‘Type’ button filter to match ARK Scan.
- Refactored hover styles and transaction rows to prevent issues in the transaction history table.
Next week, we’ll be releasing an updated version of ARK Vault with these fixes and improvements. We’ll also keep working on any new reports and continue refining the specifications and designs for the upcoming EVM changes needed for Mainsail’s integration into ARK Vault.
Mainsail Weekly Update
This week, we continued our efforts on API and EVM improvements, along with addressing reported issues on the internal testnet. Here’s a summary of the work completed:
- Removed the
/transaction/fees
endpoint from@mainsail/api-http
. - Added a new
/configuration
endpoint on@mainsail/api-transaction-pool
. - Fixed GitHub CI workflow for tests. The build command now generates artifacts for all test suites.
- Calculated
totalGasUsed
for the genesis block. - Fixed receipts sync to the database, ensuring the
0x
prefix is removed and receipts from deployed development contracts are excluded. - Resolved issues with bootstrap and restored functionality in
api-sync
. - Stored
totalRound
in the ledger database instead of recalculating it. - Released version
0.0.1-emv.7
for the internal testnet, including all the latest improvements and fixes.
In the coming week, we’ll focus on improving smart contracts and addressing any additional issues observed on the internal testnet.
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.