You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently starlight is sensitive to the sequence in which interactions with the smart contract are submitted. For certain operations can we allow the prover to be agnostic as to the order they are submitted (possibly using homomorphic commitments, virtual machines)?
Tasks
Investigate possibly solutions to sequencing in starlight. Is it possible to fix the sequencing issue without building our own L2?
Investigate Zkay.
Optional
The shape of the task will be quite different depending on what was decided with respect to building our own L2 in #351.
Definition of done
A solution or convincing argument as to why not to do this is presented to the rest of the team in a show & tell. If we decide to go ahead, create implementation issues for work in a future PI.
Overview
Currently starlight is sensitive to the sequence in which interactions with the smart contract are submitted. For certain operations can we allow the prover to be agnostic as to the order they are submitted (possibly using homomorphic commitments, virtual machines)?
Tasks
Investigate possibly solutions to sequencing in starlight. Is it possible to fix the sequencing issue without building our own L2?
Investigate Zkay.
Optional
The shape of the task will be quite different depending on what was decided with respect to building our own L2 in #351.
Definition of done
A solution or convincing argument as to why not to do this is presented to the rest of the team in a show & tell. If we decide to go ahead, create implementation issues for work in a future PI.
Links
(https://github.com/eth-sri/zkay)
Blocked by #351
The text was updated successfully, but these errors were encountered: