Skip to content

Commit

Permalink
move some summary to motivation
Browse files Browse the repository at this point in the history
  • Loading branch information
wacban authored Nov 19, 2024
1 parent 12fd994 commit 03eeeea
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions neps/nep-0568.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,12 +15,6 @@ LastUpdated: 2024-10-24
This proposal introduces a new resharding implementation and shard layout for
production networks.

Resharding V3 is a significantly redesigned approach, addressing limitations of
the previous versions, [Resharding V1][NEP-040] and [Resharding V2][NEP-508].
The earlier solutions became obsolete due to major protocol changes since
Resharding V2, including the introduction of Stateless Validation, Single Shard
Tracking, and Mem-Trie.

The primary objective of Resharding V3 is to increase chain capacity by
splitting overutilized shards. A secondary aim is to lay the groundwork for
supporting Dynamic Resharding, Instant Resharding and Shard Merging in future
Expand All @@ -30,6 +24,12 @@ updates.

The sharded architecture of the NEAR Protocol is a cornerstone of its design, enabling parallel and distributed execution that significantly boosts overall throughput. Resharding plays a pivotal role in this system, allowing the network to adjust the number of shards to accommodate growth. By increasing the number of shards, resharding ensures the network can scale seamlessly, alleviating existing congestion, managing the rising traffic demands, and welcoming new customers. This adaptability is essential for maintaining the protocol's performance, reliability, and capacity to support a thriving, ever-expanding ecosystem.

Resharding V3 is a significantly redesigned approach, addressing limitations of
the previous versions, [Resharding V1][NEP-040] and [Resharding V2][NEP-508].
The earlier solutions became obsolete due to major protocol changes since
Resharding V2, including the introduction of Stateless Validation, Single Shard
Tracking, and Mem-Trie.

## Specification

Resharding will be scheduled in advance by the NEAR developer team. The new
Expand Down

0 comments on commit 03eeeea

Please sign in to comment.