Skip to content

Commit

Permalink
2.3.0 (#12182)
Browse files Browse the repository at this point in the history
Bumps version strings and changelog messages for 2.3.0-rc.1
  • Loading branch information
marcelo-gonzalez authored Oct 2, 2024
1 parent 16db6ec commit 93073d7
Show file tree
Hide file tree
Showing 4 changed files with 107 additions and 92 deletions.
10 changes: 10 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,12 +2,22 @@

## [unreleased]

### Protocol Changes
**No Changes**

### Non-protocol Changes
**No Changes**

## 2.30

### Protocol Changes
* Sets `chunk_validator_only_kickout_threshold` to 70. Uses this kickout threshold as a cutoff threshold for contribution of endorsement ratio in rewards calculation: if endorsement ratio is above 70%, the contribution of endorsement ratio in average uptime calculation is 100%, otherwise it is 0%. Endorsements received are now included in `BlockHeader` to improve kickout and reward calculation for chunk validators.
* Changes the way receipts are stored in the state for the purpose of correct gas and size calculations in congestion control

### Non-protocol Changes
* Added [documentation](./docs/misc/archival_data_recovery.md) and a [reference](./scripts/recover_missing_archival_data.sh) script to recover the data lost in archival nodes at the beginning of 2024.
* **Archival nodes only:** Stop saving partial chunks to `PartialChunks` column in the Cold DB. Instead, archival nodes will reconstruct partial chunks from the `Chunks` column.
* Decentralized state sync: Before, nodes that needed to download state (either because they're several epochs behind the chain or because they're going to start producing chunks for a shard they don't currently track) would download them from a centralized GCS bucket. Now, nodes will attempt to download pieces of the state from peers in the network, and only fallback to downloading from GCS if that fails. Please note that in order to participate in providing state parts to peers, your node may generate snapshots of the state. These snapshots should not take too much space, since they're hard links to database files that get cleaned up on every epoch.

### 2.2.0

Expand Down
Loading

0 comments on commit 93073d7

Please sign in to comment.