Technical Update 1.0.3
While in the holiday spirit, Gear Protocol is excited to release version 1.0.3! The updates enhance the user experience and overall Gear ecosystem.
Let’s dive in ⬇️
Release Highlights
Crates and runtime version bumped to “1.0.3” (#3522).
This release maintains the integrity of gear protocols in the execution layer and user space libraries. There’s no need to update programs.
💻 Node Binary Updates: RECOMMENDED
The node binary introduces a two-phase block proposing mechanism (#3558), enhancing the stability and fault tolerance of Gear protocol implementers. The custom block proposer optimizes block creation when Gear::run extrinsic takes an extended duration, preventing block drops.
Additionally, node code adaptations for the new substrate version (#3584) include renaming — ws-port to — rpc-port for better clarity.
⚙️ Runtime Enhancements
The substrate version upgraded from v0.9.41 to v0.9.42 (#3584). Notable changes in pallet-balances:
➜ Config, error names and constant adjustments.
➜ Transition from fn set_balance() to fn force_set_balance() with distinct parameters (deprecated setting of reserved balance).
➜ Essential: Balance must be ≥ existential deposit (10 Vara for Vara Network) for any pallet-balances interaction.
Substrate version further bumped to v0.9.43 (#3584).
➜ The “controller” instance in Stakings is no longer in use and has been replaced by “stash”, which serves the same purpose.
API Updates
External node/runtime API changes may be necessary due to substrate alterations. The API has been slightly modified to align with substrate changes, with potential updates in the future.
For a comprehensive list of changes, check the Full Changelog.
Gear Protocol remains committed to providing top-notch solutions. Users are encouraged to review their JS-related code for compatibility with these updates.
Stay tuned for more updates.
