Bifrost Node Release Analysis v1.2.4

[BIFROST-Team]

The following report is a set of changes that deserves to be highlighted due to their impact on the Bifrost Network. Highlights are categorized into High Impact, Medium Impact, and Low Impact for ease of navigation.

For more information on setting up your node please follow our official documentations.

Summary

This report presents the latest modifications to the Bifrost Network’s Node. The key highlight of this new version is the transition in Substrate and Frontier from bifrost-polkadot-v0.9.39 to bifrost-polkadot-v0.9.43. As a result of this update, we’ve now achieved the version immediately preceding the significant new release, polkadot-v1.0.0. Additionally, this update enhances the robustness and reliability of in-built EVM (Ethereum Virtual Machine) while setting important benchmarks for upcoming functionalities.

Client Upgrade

• v1.2.3 → v1.2.4

Substrate and Frontier Upgrade

• v0.9.39 → v0.9.43

Runtime Upgrade Schedules

• TESTNET : v454 → v455
  • upgraded at block #9472900
• MAINNET : v2015 → v2016
  • TBD

Please note that upgrading your Bifrost Node client is mandatory for Full Nodes after a runtime upgrade occurs. If you’re operating a full node or a relayer on our Mainnet or Testnet please check the runtime upgrade schedule below. If the client has not been upgraded, precompiled contract interactions requested to your node will always fail.

• [Mandatory] Full Nodes
• [Recommend] Basic Nodes, RPC Nodes

High Impact

• [Substrate] Introduce Freezing and Holds to pallet_balances. Deprecate Currency.
  • PR: Deprecate `Currency`; introduce holds and freezing into `fungible` traits by gavofyork · Pull Request #12951 · paritytech/substrate · GitHub
• [Substrate] Integrate WebSocket and RPC server CLI options
  • PR: rpc server: break legacy CLI options and remove "backward compatible HTTP server" by niklasad1 · Pull Request #13384 · paritytech/substrate · GitHub
  • Due to this update the default WebSocket and RPC port will be set to 9944.
  • Side Effects
    • Relayer operators must update their Bifrost Node’s RPC endpoint to http://127.0.0.1:9944 in their configuration file and restart. Or add --rpc-port 9933 in your Node’s CLI and restart. (However, your Node’s WebSocket port will also be set to 9933)
    • If any proxy or load balancer is attached to your node, please update your port specifications.
  • CLI Changes
    • --rpc-max-payload (replaced by --rpc-max-request-size and --rpc-max-response-size)
    • --ws-max-out-buffer-capacity
    • --ws-external (replaced by --rpc-external)
    • --unsafe-ws-external (replaced by --unsafe-rpc-external)
    • --ipc-path
    • --ws-port (replaced by --rpc-port)
    • --ws-max-connections (replaced by --rpc-max-connections)
    • --rpc-http (replaced by --rpc-addr)
    • --rpc-ws (replaced by --rpc-addr)
• [Frontier] Introduce Weight V2 for EVM
  • PR: https://github.com/paritytech/frontier/pull/1039

Medium Impact

• [Substrate] Allow zero existential deposit (ED)
  • PR: Make ED of zero (kind of) work by gavofyork · Pull Request #13655 · paritytech/substrate · GitHub
• [Frontier] Fix gas estimation bug for Weight V2
  • PR: Fix bug estimate used gas and estimation for WeightV2 by tgmichel · Pull Request #1101 · paritytech/frontier · GitHub
• [Frontier] Support relational backend type for Frontier database
  • PR: https://github.com/paritytech/frontier/pull/883

Low Impact

• [Substrate] Remove and deprecate trait Store from all pallets
  • PR: Remove use of trait Store from all pallets and deprecate it. by vivekvpandya · Pull Request #13535 · paritytech/substrate · GitHub
• [Substrate] Deprecate Weight::from_ref_time and Weight::from_proof_size
  • PR: Deprecate `Weight::from_{ref_time, proof_size}` by ggwpez · Pull Request #13475 · paritytech/substrate · GitHub
• [Substrate] Support stable Rust version for compiling
  • PR: Support stable rust for compiling the runtime by bkchr · Pull Request #13580 · paritytech/substrate · GitHub
• [Frontier] Update EVM version to shanghai
  • PR: Update evm config to shanghai by tgmichel · Pull Request #1068 · paritytech/frontier · GitHub

Process to update node client

Please follow the steps below to update your node client.

Step 1.

First, stop your bifrost-node service and remove the installed executable binary file.

systemctl stop bifrost-node.service
rm /var/lib/bifrost-data/bifrost-node

Step 2.

Then, re-download the latest bifrost-node binary.

wget "https://github.com/bifrost-platform/bifrost-node/releases/latest/download/bifrost-node"

Step 3.

Now, the installed binary must be granted execution permission and moved to your chain data directory.

chmod +x bifrost-node
chown BIFROST_SERVICE bifrost-node
mv bifrost-node /var/lib/bifrost-data

Step 4.

At last, restart your bifrost-node service.

systemctl restart bifrost-node.service