2.11.0

CODE_COLOR: CODE_YELLOW_MAINNET
RELEASE_VERSION: 2.11.0
PROTOCOL_UPGRADE: TRUE
DATABASE_UPGRADE: TRUE
SECURITY_UPGRADE: FALSE

Protocol Changes

• Contract gas limit is increased from 300 TGas to 1 PGas.
• Yield/Resume improvements - from now on, calling promise_yield_resume after promise_yield_create will always work. Previously there were some cases where calling resume would fail if called too quickly after create. See the github issue for details. Strictly speaking, this could be a breaking change for contracts which expected the resume to fail in these situations, but it shouldn't affect normal use cases.
• A promise with a single DeleteAccount action and no input promises will be executed immediately after the receipt that created it, before any other receipts for this account.
• ETH implicit accounts now use a globally deployed contract instead of a contract embedded in the neard binary.
• Invalid transactions now generate execution outcomes, allowing indexers and RPC to report outcomes for all transactions including failed ones.
• Existing contract code is excluded from chunk state witnesses for deploy-contract and delete-account actions, reducing witness size by using internal trie nodes to check code size instead.
• Fix access key allowance being incorrectly decremented before validation checks that could fail. Previously, allowance was mutated in-place before storage stake and function call permission checks, so a failed transaction could incorrectly reduce the allowance.
• Include tokens burnt as part of global contract deploys in the corresponding execution outcome's tokens_burnt field.
• Fix deterministic account ID creation to allow creation by any incoming transfer (unless it's a refund) and correctly check whether the feature is enabled.
• Add nonce-based idempotency for global contract distribution receipts. Each distribution carries an auto-incremented nonce, and any distribution receipt with a stale nonce is dropped, preventing race conditions during multiple distribution attempts for the same contract.

Non-protocol Changes

• Replace polling for transaction status with event notifications to improve jsonrpc response latency
• Added a database migration to backfill trie data lost due to a bug in resharding. The migration runs automatically on node startup and takes approximately 5 minutes on an archival node. Non-archival nodes are not affected. (#15044)
• Fix sandbox_fast_forward RPC returning success before blocks are actually produced, by tracking target height explicitly instead of relying on the delta field which could be temporarily zero during processing. (#14899)
• Fix sandbox_patch_state RPC silently dropping patches when a block was being processed concurrently, by removing an unnecessary clear() call that raced with new patches. (#14893)
• Added experimental.tier3_public_addr network config option to manually override the auto-discovered Tier3 public address.

Protocol upgrade voting

This release upgrades the protocol version from 82 to 83.
Voting for protocol version 83 will start on Monday 2026-04-13 00:00:00 UTC.
To continue participating in consensus, you need to upgrade your node before this time.

If voting succeeds in one epoch, the protocol upgrade to version 83 is expected to happen 7-14 hours after the voting epoch ends.

2.11.0-rc.5

CODE_COLOR: CODE_GREEN_TESTNET
RELEASE_VERSION: 2.11.0-rc.5
PROTOCOL_UPGRADE: FALSE
DATABASE_UPGRADE: FALSE
SECURITY_UPGRADE: FALSE

This release includes #15465 and reverts #15007 on top of 2.11.0-rc.4.

2.11.0-rc.4

CODE_COLOR: CODE_GREEN_TESTNET
RELEASE_VERSION: 2.11.0-rc.4
PROTOCOL_UPGRADE: FALSE
DATABASE_UPGRADE: FALSE
SECURITY_UPGRADE: FALSE

This release includes #15430 and #15437 on top of 2.11.0-rc.3.

2.11.0-rc.3

CODE_COLOR: CODE_GREEN_TESTNET
RELEASE_VERSION: 2.11.0-rc.3
PROTOCOL_UPGRADE: FALSE
DATABASE_UPGRADE: FALSE
SECURITY_UPGRADE: FALSE

This release includes #15415 on top of 2.11.0-rc.2.

2.11.0-rc.2

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

This release includes a couple of minor fixes on top of 2.11.0-rc.1.

2.11.0-rc.1

CODE_COLOR: CODE_YELLOW_TESTNET
RELEASE_VERSION: 2.11.0-rc.1
PROTOCOL_UPGRADE: TRUE
DATABASE_UPGRADE: TRUE
SECURITY_UPGRADE: FALSE

Protocol Changes

• Contract gas limit is increased from 300 TGas to 1 PGas.
• Yield/Resume improvements - from now on, calling promise_yield_resume after promise_yield_create will always work. Previously there were some cases where calling resume would fail if called too quickly after create. See the github issue for details. Strictly speaking, this could be a breaking change for contracts which expected the resume to fail in these situations, but it shouldn't affect normal use cases.
• A promise with a single DeleteAccount action and no input promises will be executed immediately after the receipt that created it, before any other receipts for this account.
• ETH implicit accounts now use a globally deployed contract instead of a contract embedded in the neard binary.
• Invalid transactions now generate execution outcomes, allowing indexers and RPC to report outcomes for all transactions including failed ones.
• Existing contract code is excluded from chunk state witnesses for deploy-contract and delete-account actions, reducing witness size by using internal trie nodes to check code size instead.
• Fix access key allowance being incorrectly decremented before validation checks that could fail. Previously, allowance was mutated in-place before storage stake and function call permission checks, so a failed transaction could incorrectly reduce the allowance.
• Include tokens burnt as part of global contract deploys in the corresponding execution outcome's tokens_burnt field.
• Fix deterministic account ID creation to allow creation by any incoming transfer (unless it's a refund) and correctly check whether the feature is enabled.
• Add nonce-based idempotency for global contract distribution receipts. Each distribution carries an auto-incremented nonce, and any distribution receipt with a stale nonce is dropped, preventing race conditions during multiple distribution attempts for the same contract.

Non-protocol Changes

• Replace polling for transaction status with event notifications to improve jsonrpc response latency
• Added a database migration to backfill trie data lost due to a bug in resharding. The migration runs automatically on node startup and takes approximately 5 minutes on an archival node. Non-archival nodes are not affected. (#15044)
• Fix sandbox_fast_forward RPC returning success before blocks are actually produced, by tracking target height explicitly instead of relying on the delta field which could be temporarily zero during processing. (#14899)
• Fix sandbox_patch_state RPC silently dropping patches when a block was being processed concurrently, by removing an unnecessary clear() call that raced with new patches. (#14893)
• Added experimental.tier3_public_addr network config option to manually override the auto-discovered Tier3 public address.

Protocol upgrade voting

This release upgrades the protocol version from 82 to 83.
Voting for protocol version 83 will start on Thursday 2026-03-19 00:00:00 UTC.
To continue participating in consensus, you need to upgrade your node before this time.

If voting succeeds in one epoch, the protocol upgrade to version 83 is expected to happen 7-14 hours after the voting epoch ends.

2.10.7

CODE_COLOR: CODE_RED_MAINNET, CODE_RED_TESTNET
RELEASE_VERSION: 2.10.7
PROTOCOL_UPGRADE: FALSE
DATABASE_UPGRADE: FALSE
SECURITY_UPGRADE: TRUE

This release fixes critical flaws in nearcore code that could cause node crash.
Upgrade as soon as possible to avoid node downtime.

2.10.6

CODE_COLOR: CODE_RED_MAINNET, CODE_RED_TESTNET
RELEASE_VERSION: 2.10.6
PROTOCOL_UPGRADE: FALSE
DATABASE_UPGRADE: FALSE
SECURITY_UPGRADE: TRUE

This release fixes critical flaws in nearcore code that could cause node crash.
Upgrade as soon as possible to avoid node downtime.

2.10.5

CODE_COLOR: CODE_GREEN_MAINNET
RELEASE_VERSION: 2.10.5
PROTOCOL_UPGRADE: FALSE
DATABASE_UPGRADE: FALSE
SECURITY_UPGRADE: FALSE

This release includes the following on top of 2.10.4:

• State sync performance optimization: #14830
• Indexer fix for double hashing of code as part of DeployContract and DeployGlobalContract actions: #14840
• GlobalContractIdentifierView serialization fix: #14828

Even with a CODE_GREEN status, validators are encouraged to update for better state sync performance. Furthermore, nodes running indexers should use this release to ensure deploy contract actions are processed correctly.

2.10.4

CODE_COLOR: CODE_RED_MAINNET
RELEASE_VERSION: 2.10.4
PROTOCOL_UPGRADE: FALSE
DATABASE_UPGRADE: FALSE
SECURITY_UPGRADE: TRUE

This release fixes critical flaws in network code that could cause node crash.
Upgrade as soon as possible to avoid node downtime.