Skip to content

Commit

Permalink
fin
Browse files Browse the repository at this point in the history
  • Loading branch information
Longarithm committed Jun 13, 2024
1 parent 8c82a62 commit 87d6e97
Showing 1 changed file with 4 additions and 7 deletions.
11 changes: 4 additions & 7 deletions neps/nep-0509.md
Original file line number Diff line number Diff line change
Expand Up @@ -380,8 +380,8 @@ This way, everyone tracking block headers can compute chunk validator assignment

### Limits

One big issue which `ChunkStateWitness` introduces is that it is relatively large, and it must be distributed

[Chunks, receipts, transactions, endorsement tracker]
TODO

### Partial state witness distribution

Expand All @@ -391,10 +391,7 @@ TODO

[Explicitly outline any security concerns in relation to the NEP, and potential ways to resolve or mitigate them. At the very least, well-known relevant threats must be covered, e.g. person-in-the-middle, double-spend, XSS, CSRF, etc.]

### Limits

[Chunks, receipts, transactions, endorsement tracker]
TODO

## Alternatives

Expand All @@ -403,8 +400,8 @@ TODO

## Future possibilities

[Describe any natural extensions and evolutions to the NEP proposal, and how they would impact the project. Use this section as a tool to help fully consider all possible interactions with the project in your proposal. This is also a good place to "dump ideas"; if they are out of scope for the NEP but otherwise related. Note that having something written down in the future-possibilities section is not a reason to accept the current or a future NEP. Such notes should be in the section on motivation or rationale in this or subsequent NEPs. The section merely provides additional information.]
TODO
* Integration with ZK allowing to get rid of large state witness distribution. If we treat state witness as a proof and ZK-ify it, anyone can validate that state witness indeed proves the new chunk header with much lower effort. Complexity of actual proof generation and computation indeed increases, but it can be distributed among chunk producers, and we can have separate concept of finality while allowing generic users to query optimistic chunks.
* TODO [Describe any natural extensions and evolutions to the NEP proposal, and how they would impact the project. Use this section as a tool to help fully consider all possible interactions with the project in your proposal. This is also a good place to "dump ideas"; if they are out of scope for the NEP but otherwise related. Note that having something written down in the future-possibilities section is not a reason to accept the current or a future NEP. Such notes should be in the section on motivation or rationale in this or subsequent NEPs. The section merely provides additional information.]

## Consequences

Expand Down

0 comments on commit 87d6e97

Please sign in to comment.