NEP-509: Stateless validation stage 0 #509
Conversation
initial draft
|
Your Render PR Server URL is https://nomicon-pr-509.onrender.com. Follow its progress at https://dashboard.render.com/static/srv-ck51l1o21fec73aapqgg. |
Add validator role change section
frol
added
WG-protocol
|
Hi @walnut-the-cat – thank you for starting this proposal. As the moderator, I labeled this PR as "Needs author revision" because we assume you are still working on it since you submitted it in "Draft" mode. Please ping the @near/nep-moderators once you are ready for us to review it. We will review it again in early January, unless we hear from you sooner. We typically close NEPs that are inactive for more than two months, so please let us know if you need more time. |
| * More shards - this is covered in the resharding project. | ||
| * ZK integration. | ||
| * Underlying data structure change (e.g. verkle tree). | ||
| * Change to validator rewards. |
There was a problem hiding this comment.
may need to change this since we are incorporating new reward structure for chunk validator. cc. @Longarithm
| * The `tx_root` is based on the list of transactions proposed, which is at the discretion of the chunk producer. However, these transactions must be valid (i.e. the sender accounts have enough balance and the correct nonce, etc.). | ||
| * This `ChunkStateWitness` proves to anyone, including those who track only block data and no shards, that this chunk header is correct, meaning that the uniquely determined fields are exactly what should be expected, and the discretionary `tx_root` field corresponds to a valid set of transactions. | ||
| * The `ChunkStateWitness` is not part of the chunk itself; it is distributed separately and is considered transient data. | ||
| * The chunk producer then distributes the `ChunkStateWitness` to a subset of *Chunk Validators* assigned for this shard. This is in addition to, and independent of, the existing chunk distribution logic (implemented by `ShardsManager`) today. |
There was a problem hiding this comment.
Should we talk about chunk witness compression, size limit, and reed-solomon encoding?
cc. @shreyan-gupta, @jancionear , @pugachAG
There was a problem hiding this comment.
please check below comment as well
| Each chunk validator's stake is divided into "mandates". There are full and partial mandates. The amount of stake for a full mandate is a fixed parameter determined by the stake distribution of all validators, and any remaining amount smaller than a full mandate is a partial mandate. A chunk validator therefore has zero or more full mandates plus up to one partial mandate. The list of full mandates and the list of partial mandates are then separately shuffled and partitioned equally (as in, no more than one mandate in difference between any two shards) across the shards. Any mandate assigned to a shard means that the chunk validator who owns the mandate is assigned to validate that shard. Because a chunk validator may have multiple mandates, it may be assigned multiple shards to validate. | ||
|
|
||
| We have done research to show that the security of this algorithm is sufficient with a reasonable number of chunk validators and a reasonable number of shards, assuming a reasonable bound for the total stake of malicious nodes. TODO: Include or link to that research here. | ||
|
|
There was a problem hiding this comment.
I think it's worth having a separate section for followings:
- state witness compression + size limit
- state witness breakdown with reed solomon encoding
- network optimization needed for each node
- reward calculation change
cc. @pugachAG , @Longarithm , @saketh-are , @shreyan-gupta , @jancionear
|
|
||
| ## Reference Implementation | ||
|
|
||
| TODO: This is essentially going to be describing the exact structure of `ChunkStateWitness`, `ChunkEndorsement`, and describing the exact algorithm to be used for the chunk validator shuffling. |
There was a problem hiding this comment.
this needs to be done
|
|
||
| The section should return to the examples given in the previous section, and explain more fully how the detailed proposal makes those examples work.] | ||
|
|
||
| ## Validator Role Change |
There was a problem hiding this comment.
cc. @Longarithm
| | block validation | Y | Y | N | | ||
| | chunk validation | Y | Y | N | | ||
|
|
||
| ## Security Implications |
There was a problem hiding this comment.
cc. @jancionear @pugachAG
WIP