From fdeb982e7865f7243b3b4f1a8bd059c6b56b9072 Mon Sep 17 00:00:00 2001 From: Waclaw Banasik Date: Mon, 18 Nov 2024 13:24:32 +0000 Subject: [PATCH] motivation --- neps/nep-0568.md | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/neps/nep-0568.md b/neps/nep-0568.md index 04aacf072..8f12af3f4 100644 --- a/neps/nep-0568.md +++ b/neps/nep-0568.md @@ -28,15 +28,11 @@ updates. ## Motivation -```text -[Explain why this proposal is necessary, how it will benefit the NEAR protocol or community, and what problems it solves. Also describe why the existing protocol specification is inadequate to address the problem that this NEP solves, and what potential use cases or outcomes.] -``` +The sharded nature of the NEAR protocol is one of its defining features. It allows parallel and distributed execution which in turns greatly increases the total througput. Resharding is a critical component of sharding, providing the ability to increase the number of shards and hence total throughput. Resharding is needed to handle the relieve the existing congestion, handle the ever growing traffic and onboard new clients . -## Specification +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. -```text -[Explain the proposal as if you were teaching it to another developer. This generally means describing the syntax and semantics, naming new concepts, and providing clear examples. The specification needs to include sufficient detail to allow interoperable implementations getting built by following only the provided specification. In cases where it is infeasible to specify all implementation details upfront, broadly describe what they are.] -``` +## Specification Resharding will be scheduled in advance by the NEAR developer team. The new shard layout will be hardcoded into the neard binary and linked to the protocol