Welcome to this week’s Weekly Development Report, highlighting strong progress in SDK evolution, UI refinement, and core system stability. We made major improvements in the Go Crypto SDK, aligning it with Mainsail and EVM standards through a new RLP-based transaction model, improved signing mechanisms, and enhanced security and testing. The ARK Vault team focused on UI responsiveness and consistency, refining address rendering and simplifying navigation components for a smoother user experience. Meanwhile, the Mainsail team improved system reliability with better bootstrap handling, updated EVM dependencies, and protocol alignment, while continuing to refine transaction pipeline behavior and overall stability.
Development Activity Summary (July 24 – July 31, 2026)
Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from July 24, 2026, to July 31, 2026.
| Project | Commits | Authors |
|---|---|---|
| ARK Connect | 0 | 0 |
| ARK Scan | 0 | 0 |
| ARK SDKs & Docs | 26 | 1 |
| ARK Vault | 42 | 2 |
| Mainsail | 32 | 2 |
In total, 100 commits were merged across all projects this week. As always, commit counts fluctuate with sprint focus and task complexity.
ARK SDKs and Documentation Site Weekly Report
This week focused on major progress in the Go Crypto SDK, aligning it with Mainsail/EVM standards and improving reliability, security, and developer ergonomics.
We migrated the transaction envelope to an RLP-based format using ECDSA signing, replacing the legacy Ark v2 binary structure. Transactions now follow an EVM-compatible structure [nonce, gasPrice, gasLimit, to, value, data, v, r, s], with a newly introduced Transaction model reflecting these fields.
A custom RLP codec was implemented to handle encoding and decoding without external dependencies, alongside a new ABI codec to support encoding/decoding for known Mainsail contract interactions. Transaction signing was fully reworked to use recoverable ECDSA (secp256k1), including new methods for signing, verification, hashing, and sender recovery.
We also strengthened robustness by hardening RLP and ABI decoders against malformed input, ensuring strict validation, bounded conversions, and eliminating risks like silent truncation or runtime panics.
The SDK saw a significant cleanup, including:
- Removal of legacy transaction models and Schnorr-related code
- Dependency trimming and upgrades for improved maintainability
- Introduction of transaction builders for easier construction of transactions
- Implementation of message signing capabilities
Testing was expanded with end-to-end round-trip scenarios (sign → serialize → deserialize → verify), along with updated fixtures and additional unit tests tailored to Mainsail.
Next week we will continue advancing the Go Crypto SDK and begin deeper work on the Go Client SDK, focusing on integration with the updated transaction model and improving developer usability. We will also ensure that any new features or changes are properly reflected in the documentation site, keeping all SDK documentation accurate, consistent, and up to date.
ARK Vault Weekly Report
This week focused on improving UI responsiveness and simplifying component usage across the application.
We refactored the Address component to provide more accurate and responsive truncation. This resolves several UI issues where truncation would break during resizing, particularly in the transaction review side panel, and where table views (notably between 1024–1280px) would improperly cut off text instead of adapting to available space. With the updated implementation, transaction IDs and addresses now adjust smoothly to screen size changes and consistently occupy the correct width.
Additionally, we streamlined the navigation experience by adopting a simplified dropdown component across the navigation bar. This change standardizes dropdown behavior and reduces complexity in areas such as the server status check, user menu, and main menu on smaller screens.
Next week we will continue refining the user interface and overall experience, addressing any remaining edge cases, and resolving issues identified through testing. We will also focus on general performance improvements and ongoing component cleanup to keep the codebase maintainable and consistent.
Mainsail Weekly Report
This week focused on improving system stability, updating dependencies, and refining core behavior.
We added tolerance for concurrent CREATE EXTENSION execution during bootstrap, preventing errors when the API and core processes start simultaneously or when PostgreSQL extensions are already installed. This improves reliability in multi-process and preconfigured environments.
We updated REVM dependencies to the latest version, ensuring better compatibility, performance, and alignment with upstream EVM improvements.
In the transaction pipeline, we fixed transaction pool tests by ensuring that getTransactions no longer flushes the mempool, preserving expected behavior and improving test accuracy.
Additionally, we upgraded the EVM specification by replacing the Shanghai spec with Osaka, aligning Mainsail with the latest protocol changes and future-proofing execution behavior.
Next week we will focus on adding support for the prevrandao block variable in REVM, continuing to improve EVM compatibility. We will also work on expanding test coverage, refining edge-case handling, and making further performance and stability improvements across the core system.
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 issue pages:
Follow Us on X
Follow us on X and keep an eye on the blog to stay up to date with everything we ship. We publish a development report every week so you can follow along as the ecosystem grows.
