Skip to content

1.35.0
Compare
Choose a tag to compare
@marcelo-gonzalez marcelo-gonzalez released this 25 Jul 16:43
· 1437 commits to master since this release
1.35.0
1e781bc 
CODE_COLOR: CODE_YELLOW_MAINNET
RELEASE_VERSION: 1.35.0
PROTOCOL_UPGRADE: TRUE
DATABASE_UPGRADE: TRUE
SECURITY_UPGRADE: FALSE

Protocol Changes

  • Upgrade the contract preparation code to use finite-wasm, which guarantees deterministic limits on execution time and space of compiled contracts

Non-protocol Changes

  • Dump state by multiple nodes, each node will refer to s3 for which parts need to be dumped. #9049
  • Small values in the flat storage trie are inlined for faster accesses #9029
  • A current protocol version metric is added to the prometheus metrics under near_current_protocol_version #9030
  • The transaction pool size is tracked, and if the transaction_pool_size_limit config option is set, we now avoid storing more than the specified size of transactions in each shard's transaction pool #8970 and #9036

Split Storage Feature

Split storage allows nodes to improve storage costs and block production performance on archival nodes by splitting storage into hot and cold databases. Hot database stores all of the data from the past several epochs, and cold database stores all historical data from a limited list of columns.
In split storage mode Client only works with a smaller hot database to produce blocks, which results in increased performance.
Cold database is not accessed for reads during normal block production and is only read when historical data is specifically requested. Thus, we recommend keeping the cold database on HDD and only optimize speed for the hot database, which is 10 times smaller.
Split storage can be enabled with a config change and a migration that requires manual steps. You can learn more about the migration process here: https://near-nodes.io/archival/split-storage-archival

Protocol Upgrade Voting

This release contains a protocol upgrade. Voting for upgrading to protocol version 62 will start on 2023-08-01 15:00:00 UTC.

Database Upgrade

This release includes a db upgrade, which migrates entries in the FlatStateChanges, the size of which should not exceed several dozens of entries

Assets 2