Skip to content

Commit

Permalink
update the CHANGELOG for 1.35.0 (near#9238)
Browse files Browse the repository at this point in the history
  • Loading branch information
marcelo-gonzalez authored Jul 25, 2023
1 parent 8550972 commit 31f12f1
Showing 1 changed file with 14 additions and 1 deletion.
15 changes: 14 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,11 +7,24 @@


### Non-protocol Changes
* Dump state by multiple nodes, each node will refer to s3 for which parts need to be dumped. [#9049](https://github.com/near/nearcore/pull/9049)

* New option `transaction_pool_size_limit` in `config.json` allows to limit the size of the node's transaction pool.
By default the limit is set to 100 MB. [#3284](https://github.com/near/nearcore/issues/3284)
* Database snapshots at the end of an epoch. This lets a node obtain state parts using flat storage. [#9090](https://github.com/near/nearcore/pull/9090)

## 1.35.0

### Protocol Changes

* Upgrade the contract preparation code to use [finite-wasm](https://github.com/near/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](https://github.com/near/nearcore/pull/9049)
* Small values in the flat storage trie are inlined for faster accesses [#9029](https://github.com/near/nearcore/pull/9029)
* A current protocol version metric is added to the prometheus metrics under near_current_protocol_version [#9030](https://github.com/near/nearcore/pull/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](https://github.com/near/nearcore/pull/8970) and [#9036](https://github.com/near/nearcore/pull/9036)

## 1.34.0

### Protocol Changes
Expand Down

0 comments on commit 31f12f1

Please sign in to comment.