Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: format changelog #12696

Merged
merged 1 commit into from
Jan 7, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@
### Non-protocol Changes
**No Changes**

## [2.4.0]
## 2.4.0

### Protocol Changes

Expand All @@ -25,7 +25,7 @@ and only fallback to downloading from GCS if that fails. Please note that in ord
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. [#12004](https://github.com/near/nearcore/issues/12004)

## [2.3.0]
## 2.3.0

### 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.
Expand All @@ -35,7 +35,7 @@ since they're hard links to database files that get cleaned up on every epoch. [
* **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.
* Enabled state snapshots on every epoch to allow the nodes to take part in decentralized state sync in future releases.

### 2.2.1
## 2.2.1

This release patches a bug found in the 2.2.0 release

Expand All @@ -52,7 +52,7 @@ It's possible to recover a stalled node by clearing the compiled contract cache

After that the node should be able to recover and sync with the rest of the network.

### 2.2.0
## 2.2.0

### Protocol Changes
* The minimum validator stake has been set to a lower value. The small-stake validators that were kicked out during the shift to stateless validation will be able to rejoin the network.
Expand Down
Loading