8000 Releases · near/nearcore · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Releases: near/nearcore

2.6.3

16 May 09:07
@jancionear jancionear
2.6.3
8000
680b27e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
2.6.3 Latest
Latest 
CODE_COLOR: CODE_GREEN_MAINNET
RELEASE_VERSION: 2.6.3
PROTOCOL_UPGRADE: FALSE
DATABASE_UPGRADE: FALSE
SECURITY_UPGRADE: FALSE

Non-protocol Changes

  • Allow chunk-only validators (outside the top 100 validators, not chunk producers) to join the Tier 1 network. This reduces latency of messages sent and received by chunk validators and improves the chunk endorsement rate.
Assets 2
Loading

2.6.3-rc.2

15 May 12:33
@jancionear jancionear
2.6.3-rc.2
e7d5227
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
2.6.3-rc.2 Pre-release
Pre-release 
CODE_COLOR: CODE_GREEN_TESTNET
RELEASE_VERSION: 2.6.3-rc.2
PROTOCOL_UPGRADE: FALSE
DATABASE_UPGRADE: FALSE
SECURITY_UPGRADE: FALSE

Non-protocol Changes

  • Allow chunk-only validators (outside the top 100 validators, not chunk producers) to join the Tier 1 network. This reduces latency of messages sent and received by chunk validators and improves the chunk endorsement rate.
Loading

2.6.3-rc.1

14 May 13:07
@jancionear jancionear
2.6.3-rc.1
066689e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
2.6.3-rc.1 Pre-release
Pre-release 
CODE_COLOR: CODE_GREEN_TESTNET
RELEASE_VERSION: 2.6.3-rc.1
PROTOCOL_UPGRADE: FALSE
DATABASE_UPGRADE: FALSE
SECURITY_UPGRADE: FALSE

Non-protocol Changes

  • Allow chunk-only validators (outside the top 100 validators, not chunk producers) to join the Tier 1 network. This reduces latency of messages sent and received by chunk validators and improves the chunk endorsement rate.
Loading

2.6.2

10 May 16:56
@jancionear jancionear
2.6.2
2f9ddb7
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
2.6.2 
CODE_COLOR: CODE_GREEN_MAINNET
RELEASE_VERSION: 2.6.2
PROTOCOL_UPGRADE: FALSE
DATABASE_UPGRADE: FALSE
SECURITY_UPGRADE: FALSE

Non-protocol Changes

  • Enabled TCP_NODELAY on all peer connections to reduce latency. Improves chunk endorsement rate for validators.
Loading

2.6.2-rc.1

09 May 17:17
@jancionear jancionear
2.6.2-rc.1
3cabc0c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
2.6.2-rc.1 Pre-release
Pre-release 
CODE_COLOR: CODE_GREEN_TESTNET
RELEASE_VERSION: 2.6.2-rc.1
PROTOCOL_UPGRADE: FALSE
DATABASE_UPGRADE: FALSE
SECURITY_UPGRADE: FALSE

Non-protocol Changes

  • Enabled TCP_NODELAY on all peer connections to reduce latency. Improves chunk endorsement rate for validators.
Loading

2.6.1-rc.1

02 May 10:41
@jancionear jancionear
2.6.1-rc.1
eda51b5
This commit was signed with the committer’s verified signature.
jancionear Jan Malinowski
GPG key ID: D497C5E87A462735
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
2.6.1-rc.1 Pre-release
Pre-release 
CODE_COLOR: CODE_GREEN_TESTNET
RELEASE_VERSION: 2.6.1-rc.1
PROTOCOL_UPGRADE: FALSE
DATABASE_UPGRADE: FALSE
SECURITY_UPGRADE: FALSE

Protocol Changes

Nothing on top of 2.6.0-rc.2

Non-protocol Changes

  • Improved chunk distribution to speed up chunk validation and improve endorsement rate.

Protocol upgrade voting

No protocol upgrade scheduled.

Loading

2.6.1

01 May 06:24
@staffik staffik
2.6.1
60bb220
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
2.6.1 
CODE_COLOR: CODE_YELLOW_MAINNET
RELEASE_VERSION: 2.6.1
PROTOCOL_UPGRADE: TRUE
DATABASE_UPGRADE: TRUE
SECURITY_UPGRADE: FALSE

[2.6.1]

Protocol Changes

  • Implemented support for global contracts: NEP-591
  • Implemented Optimistic Block to remove doubled chunk execution latency from block & chunk production flow #10584
  • Changed receipt id computation to enable chunk execution based on Optimistic Block. More specifically, primitive create_hash_upgradable is changed to use block_height instead of extra_hash.

Non-protocol Changes

No Changes

Protocol upgrade voting

Voting for protocol version 77 will start on 2025-05-07 11:00 UTC.

Protocol upgrade to version 77 is expected to happen around 2025-05-08 7:30 UTC.

Required config upgrade after protocol upgrade

After the network upgrades to protocol 77 we will ask node operators to update some config values to make the chain produce blocks at a faster rate. We will share the exact instructions after the protocol upgrade. The instructions will be slightly different from the previous testnet ones.

Database migration

This release includes a database migration from version 43 to version 44.
When neard 2.6 is started for the first time, it will start the migration and convert the database to the new version. Please don’t interrupt the migration, if you interrupt it you will have to restore the database from a pre-migration snapshot.

On mainnet validator and rpc nodes the migration takes about 30 seconds.
On mainnet archival nodes the migration takes about 5 minutes.
No additional space is needed for the migration.

Rollback from 2.6 to 2.5

If a node experiences issues after updating from 2.5 to 2.6, it’s possible to roll it back to 2.5, but it requires manual action to undo the database migration.
Rolling back is only possible before the protocol upgrade - after the protocol upgrade the network will move to a new version that isn’t compatible with neard 2.5

The rollback procedure has been tested, but it’s fairly new and there’s still a possibility that something will go wrong. Please keep the logs from the rollback process in case you run into any issues.

To roll back a node from 2.6 to 2.5, do the following

  1. Stop the node
  2. Using a 2.6 neard binary, run ./neard database rollback-to25 and confirm the rollback. After confirmation the rollback process will start. Please don’t interrupt the rollback process, it could corrupt the database. Wait for the process to finish.
  3. Database will be rolled back to the version used by neard 2.5
  4. Start the node using neard 2.5 binary

Be patient, preparing a big archival database for rollback can take up to 5 minutes.

Loading

2.6.0

30 Apr 19:46
@staffik staffik
2.6.0
b5530e9
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
2.6.0 
CODE_COLOR: CODE_YELLOW_MAINNET
RELEASE_VERSION: 2.6.0
PROTOCOL_UPGRADE: TRUE
DATABASE_UPGRADE: TRUE
SECURITY_UPGRADE: FALSE

[2.6.0]

Protocol Changes

  • Implemented support for global contracts: NEP-591
  • Implemented Optimistic Block to remove doubled chunk execution latency from block & chunk production flow #10584
  • Changed receipt id computation to enable chunk execution based on Optimistic Block. More specifically, primitive create_hash_upgradable is changed to use block_height instead of extra_hash.

Non-protocol Changes

No Changes

Protocol upgrade voting

Voting for protocol version 77 will start on 2025-05-07 11:00 UTC.

Protocol upgrade to version 77 is expected to happen around 2025-05-08 7:30 UTC.

Required config upgrade after protocol upgrade

After the network upgrades to protocol 77 we will ask node operators to update some config values to make the chain produce blocks at a faster rate. We will share the exact instructions after the protocol upgrade. The instructions will be slightly different from the previous testnet ones.

Database migration

This release includes a database migration from version 43 to version 44.
When neard 2.6 is started for the first time, it will start the migration and convert the database to the new version. Please don’t interrupt the migration, if you interrupt it you will have to restore the database from a pre-migration snapshot.

On mainnet validator and rpc nodes the migration takes about 30 seconds.
On mainnet archival nodes the migration takes about 5 minutes.
No additional space is needed for the migration.

Rollback from 2.6 to 2.5

If a node experiences issues after updating from 2.5 to 2.6, it’s possible to roll it back to 2.5, but it requires manual action to undo the database migration.
Rolling back is only possible before the protocol upgrade - after the protocol upgrade the network will move to a new version that isn’t compatible with neard 2.5

The rollback procedure has been tested, but it’s fairly new and there’s still a possibility that something will go wrong. Please keep the logs from the rollback process in case you run into any issues.

To roll back a node from 2.6 to 2.5, do the following

  1. Stop the node
  2. Using a 2.6 neard binary, run ./neard database rollback-to25 and confirm the rollback. After confirmation the rollback process will start. Please don’t interrupt the rollback process, it could corrupt the database. Wait for the process to finish.
  3. Database will be rolled back to the version used by neard 2.5
  4. Start the node using neard 2.5 binary

Be patient, preparing a big archival database for rollback can take up to 5 minutes.

Loading

2.6.0-rc.2

24 Apr 11:00
@jancionear jancionear
2.6.0-rc.2
8b59519
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
2.6.0-rc.2 Pre-release
Pre-release

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

Protocol Changes

Nothing on top of 2.6.0-rc.1

Non-protocol Changes

  • Fix view function calls and view code RPC requests for accounts using global contracts
  • Prevent indexer from dropping chunks after a missing block
  • Remove spammy logs about optimistic block and evicting partial witnesses
  • State sync bugfixes

Protocol upgrade voting

No protocol upgrade scheduled.

Loading

2.6.0-rc.1

07 Apr 14:08
@jancionear jancionear
2.6.0-rc.1
26e8630
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
2.6.0-rc.1 Pre-release
Pre-release 
CODE_COLOR: CODE_YELLOW_TESTNET
RELEASE_VERSION: 2.6.0-rc.1
PROTOCOL_UPGRADE: TRUE
DATABASE_UPGRADE: TRUE
SECURITY_UPGRADE: FALSE

Protocol Changes

  • Implemented support for global contracts: NEP-591
  • Implemented Optimistic Block to remove doubled chunk execution latency from block & chunk production flow #10584

Non-protocol Changes

No Changes

Protocol upgrade voting

Voting for protocol version 77 will start on Monday 2025-04-14 19:00:00 UTC

Protocol upgrade to version 77 is expected to happen 12-24 hours later on Tuesday 2025-04-15 between 7:00 and 19:00 UTC

Required config update after protocol upgrade

After the network upgrades to protocol 77 we will ask node operators to update some config values to make the chain produce blocks at a faster rate. We will share the exact instructions after the protocol upgrade.

Database migration

This release includes a database migration from version 43 to version 44.
When neard 2.6 is started for the first time, it will start the migration and convert the database to the new version. Please don’t interrupt the migration, if you interrupt it you will have to restore the database from a pre-migration snapshot.

On testnet validator and rpc nodes the migration takes about 5 seconds.
On testnet archival nodes the migration takes about 60 seconds
No additional disk space is needed for the migration.

Rollback from 2.6 to 2.5

If a node experiences issues after updating from 2.5 to 2.6, it’s possible to roll it back to 2.5, but it requires manual action to undo the database migration.
Rolling back is only possible before the protocol upgrade - after the protocol upgrade the network will move to a new version that isn’t compatible with neard 2.5

The rollback procedure has been tested, but it’s fairly new and there’s still a possibility that something will go wrong. Please keep the logs from the rollback process in case you run into any issues.

To roll back a node from 2.6 to 2.5, do the following

  1. Stop the node
  2. Using a 2.6 neard binary, run ./neard database rollback-to25 and confirm the rollback. After confirmation the rollback process will start. Please don’t interrupt the rollback process, it could corrupt the database. Wait for the process to finish.
  3. Database will be rolled back to the version used by neard 2.5
  4. Start the node using neard 2.5 binary

Be patient, preparing a big archival database for rollback can take up to 5 minutes.

Loading
0