1.32.0

CODE_COLOR: CODE_YELLOW_MAINNET
RELEASE_VERSION: 1.32.0
PROTOCOL_UPGRADE: TRUE
DATABASE_UPGRADE: FALSE
SECURITY_UPGRADE: FALSE

Protocol Changes

• Stabilize ed25519_verify feature: introducing a host function to verify ed25519 signatures efficiently.
  #8098
  NEP-364
• Added STUN-based self-discovery to make configuration of TIER1 network easier in the simplest validator setups.
  #8472
• Stabilize zero balance account feature: allows account to not hold balance under certain conditions and enables a more smooth onboarding experience where users don't have to first acquire NEAR tokens to pay for the storage of their accounts.
  #8378
  NEP-448
• Stabilize meta transactions on the protocol level.
  NEP-366,
  Tracking issue #8075,
  Stabilization #8601

Non-protocol Changes

• /debug page now has client_config linked. You can also check your client_config directly at /debug/client_config

• Added cold store loop - a background thread that copies data from hot to cold storage and a new json rpc endpoing - split_storage_info - that exposes debug info about the split storage.
  #8432

• ClientConfig can be updated while the node is running. dyn_config.json is no longer needed as its contents were merged into config.json.
  #8240

Protocol Upgrade Voting

This release contains a protocol upgrade. Voting for upgrading to protocol version 59 will start on 2023-03-26 15:00:00 UTC

Database Upgrade

This release does not contain a database upgrade.

Config update note

This release does not contain any config changes that need to be applied manually.

Breaking changes in Near Lake Framework

Meta Transactions

The Near Protocol is soon releasing Meta transactions across its various chains. This update will introduce a new action type that enables third-party accounts to initiate and pay transaction fee on behalf of the account. A more in depth explanation can be found in NEP-366 and release schedule found below.

Release schedule

	Testnet - 2023-03-06
	Mainnet - 2023-03-20

Upgrading

In anticipation of this release, we have prepared new versions of the JavaScript and Rust Lake Frameworks. It is important that consumers of these libraries upgrade to the latest version of the libraries, failing to do so will result in unexpected behaviour or even errors when encountering the new action within your indexer.

With both libraries, upgrading requires installing the required versions, and ensuring you are handling the new Delegate type correctly. Required versions and relevant types for each library can be found below.

JavaScript

• Required version - near-lake-framework-js@^2.0.0
• Relevant types - Action['DelegateAction'], DelegateAction

Rust

• Required version - near-lake-framework-rs@>=0.7.0
• Relevant types - ActionView::Delegate, DelegateAction