1.31.0

Protocol Changes

• An empty protocol upgrade to facilitate migration of the network interfaces in the next version.

Non-protocol changes

• Enable TIER1 network. Participants of the BFT consensus (block & chunk producers) now can establish direct TIER1 connections
  between each other, which will optimize the communication latency and minimize the number of dropped chunks.
  To configure this feature, see advanced_configuration/networking. #8141, #8085, #7759
• /status response has now two more fields: node_public_key and
  validator_public_key. The node_key field is now deprecated and should not
  be used since it confusingly holds validator key. #7828
• Added near_node_protocol_upgrade_voting_start Prometheus metric whose value
  is timestamp when voting for the next protocol version starts. #7877
• neard cmd can now verify proofs from JSON files. #7840
• In storage configuration, the value trie_cache_capacities now is no longer
  a hard limit but instead sets a memory consumption limit. For large trie nodes,
  the limits are close to equivalent. For small values, there can now fit more
  in the cache than previously. #7749
• New options store.trie_cache and store.view_trie_cache in config.json
  to set limits on the trie cache. Deprecates the never announced
  store.trie_cache_capacities option which was mentioned in previous change. #7578
• New option store.background_migration_threads in config.json. Defines
  number of threads to execute background migrations of storage. Currently used
  for flat storage migration. Set to 8 by default, can be reduced if it slows down
  block processing too much or increased if you want to speed up migration. #8088,
• Tracing of work across actix workers within a process: #7866, #7819, #7773.
• Scope of collected tracing information can be configured at run-time: #7701.
• Attach node's chain_id, node_id, and account_id values to tracing
  information: #7711.
• Change exporter of tracing information from opentelemetry-jaeger to
  opentelemetry-otlp: #7563.
• Tracing of requests across processes: #8004.

Protocol Upgrade Voting

Voting for upgrading to protocol version 58 will start on 2023-02-13 15:00:00 UTC

Database Upgrade

The release needs a database upgrade, which takes about 1 minute for an RPC node, and about 2 hour and 10 minutes for an Archival node.

Config update note

Please note that you may need to update config.json file.
Please ensure that config.json doesn't mention fields db_migration_snapshot_path or use_db_migration_snapshot.
Recommended to enable DB-migration snapshots like this:

"store": {
    "migration_snapshot": true
}

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

1.31.0-rc.4

Fixes

• Security fix from 1.30.1
• Rollback #8440 to fix the issue of validators missing chunks

This release doesn't have a protocol upgrade, but 1.31.0-rc.3 introduced a protocol upgrade which is scheduled to start after 2023-02-02 15:00:00 UTC.

CODE_COLOR: CODE_YELLOW_TESTNET
RELEASE_VERSION: 1.31.0-rc.4
PROTOCOL_UPGRADE: FALSE
DATABASE_UPGRADE: FALSE
SECURITY_UPGRADE: TRUE

1.30.1

Notice

This release of nearcore is a security release. It incorporates a patch that addresses a vulnerability related to slashing of stake, which was disabled by design, but imperfectly implemented. The vulnerability, if exploited, could have caused mainnet to crash and its state to be corrupted.

Prior to publishing this release, over 2/3 of mainnet block producers silently deployed the same patch that is incorporated into this release, thus securing mainnet from attacks related to the vulnerability.

It is strongly recommended that all node operators who have not directly patched their nodes do so immediately.

This release contains no additional code or code changes beyond the patch that addresses the security vulnerability.

Fixes

address a vulnerability related to slashing of stake

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

1.31.0-rc.3

Fixes

• Exit with nonzero code on init cmd error (#8334)
• Add back support for receiving StateResponse (#8377)
• Revert "Tx status query not waiting for refunds" (#8388)
• Fixed broadcasting AccountData after node restart. (#8407)

Protocol Upgrades

• Protocol upgrade doesn't introduce new features, but makes it possible to deprecate some network messages in the next protocol version.

Voting for the protocol upgrade is scheduled to start after 2023-02-02 15:00:00 UTC.

CODE_COLOR: CODE_YELLOW_TESTNET
RELEASE_VERSION: 1.31.0-rc.3
PROTOCOL_UPGRADE: TRUE
DATABASE_UPGRADE: FALSE
SECURITY_UPGRADE: FALSE

1.31.0-rc.2

Fixes

• Un-deprecate AnnounceAccounts (undo #8182 )

CODE_COLOR: CODE_GREEN_TESTNET
RELEASE_VERSION: 1.31.0-rc.2
PROTOCOL_UPGRADE: FALSE
DATABASE_UPGRADE: FALSE
SECURITY_UPGRADE: FALSE

1.31.0-rc.1

Non-protocol changes

• Enable TIER1 network. Participants of the BFT consensus (block & chunk producers) now can establish direct TIER1 connections
  between each other, which will optimize the communication latency and minimize the number of dropped chunks.
  To configure this feature, see advanced_configuration/networking. #8141, #8085, #7759
• /status response has now two more fields: node_public_key and
  validator_public_key. The node_key field is now deprecated and should not
  be used since it confusingly holds validator key. #7828
• Added near_node_protocol_upgrade_voting_start Prometheus metric whose value
  is timestamp when voting for the next protocol version starts. #7877
• neard cmd can now verify proofs from JSON files. #7840
• In storage configuration, the value trie_cache_capacities now is no longer
  a hard limit but instead sets a memory consumption limit. For large trie nodes,
  the limits are close to equivalent. For small values, there can now fit more
  in the cache than previously. #7749
• New options store.trie_cache and store.view_trie_cache in config.json
  to set limits on the trie cache. Deprecates the never announced
  store.trie_cache_capacities option which was mentioned in previous change. #7578
• New option store.background_migration_threads in config.json. Defines
  number of threads to execute background migrations of storage. Currently used
  for flat storage migration. Set to 8 by default, can be reduced if it slows down
  block processing too much or increased if you want to speed up migration. #8088,
• Tracing of work across actix workers within a process: #7866, #7819, #7773.
• Scope of collected tracing information can be configured at run-time: #7701.
• Attach node's chain_id, node_id, and account_id values to tracing
  information: #7711.
• Change exporter of tracing information from opentelemetry-jaeger to
  opentelemetry-otlp: #7563.
• Tracing of requests across processes: #8004.

CODE_COLOR: CODE_GREEN_TESTNET
RELEASE_VERSION: 1.31.0-rc.1
PROTOCOL_UPGRADE: FALSE
DATABASE_UPGRADE: TRUE
SECURITY_UPGRADE: FALSE

1.30.0

Features:

• account_id_in_function_call_permission enforces that account id in function call permission is indeed a valid account id #7569
• Add proof to ViewState response and include_proof argument to ViewState request #7603 #7593
• Move the check for is_height_processed forward before process_block_header (#7831)
• [Debug UI] Show github link for version on debug page
• [Debug UI] Improve last-blocks debug page
• Add hash to PeerChainInfo
• Change debug page to display error messages in block processing

Fixes

• do not enter sync mode if peer is at an invalid hash
  mark block as invalid in preprocess_block
• Deprecate GCCount column #7632
• near-vm-runner: fix m1 build #7587

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

1.29.3

Fixes

• adjustments to gas computations

CODE_COLOR: CODE_RED_MAINNET
RELEASE_VERSION: 1.29.3
PROTOCOL_UPGRADE: FALSE
DATABASE_UPGRADE: FALSE
SECURITY_UPGRADE: TRUE

1.30.0-rc.6

Fixes

• adjustments to gas computations

CODE_COLOR: CODE_RED_TESTNET
RELEASE_VERSION: 1.30.0-rc.6
PROTOCOL_UPGRADE: FALSE
DATABASE_UPGRADE: FALSE
SECURITY_UPGRADE: TRUE

1.29.2

Fixes:

• Rosetta RPC predecessor_id is now set on each state change

CODE_COLOR: CODE_GREEN_MAINNET
RELEASE_VERSION: 1.29.2
PROTOCOL_UPGRADE: FALSE
DATABASE_UPGRADE: FALSE
SECURITY_UPGRADE: FALSE