Updating a Node
As a decentralized network, every update to NEAR Protocol needs some coordination between end users, platforms, developers, and validators.
nearup provides scripts to launch NEAR Protocol
betanet nodes. Unless it is executed with the switch
nearup will automatically update the local binaries if NEAR's boot nodes fork the network and change the genesis checksum.
For security-critical applications and for validators,
nearup can run a locally compiled binary of
nearcore, but such updates have to be done manually. Since validators are responsible for creating new blocks, coordination in this process is necessary to avoid any network stall.
NEAR merges node updates from nearcore releases as follows:
betanetevery Monday at 00:00 UTC. The release tag is mapped with
testnetevery Monday at 00:00 UTC. The release tag is mapped with
mainnetis not yet subject to planned releases
mainnet: Restricted is live, planned updates to
mainnet will come via coordination with validators.
betanetprovides cutting-edge testing grounds for validators, with weekly updates and frequent hard-forks.
betanetis using the
nearcore, which is merged every Wednesday at 00:00 UTC and deployed on NEAR boot nodes shortly after.
We may issue a
[CODE_YELLOW_MAINNET] if the network is suffering minor issues, or a new software release introduces incompatibilities and requires additional testing.
NEAR Protocol team will use the tag
[CODE_RED_MAINNET] in the Validator Announcement channel on Discord, followed by email instructions for coordination. Some updates may follow a confidential process, as explained on nearcore/SECURITY.md docs.
NEAR's team will be mostly active on Github, and with limited participation on Discord and Telegram.
Got a question?
Ask it on StackOverflow!