RIW2021_RFC_Optimistic ZKC(S)P #15
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
daviddias
commented
Feb 12, 2021
|
|
||
| In this RFC, we propose a way to rely on the ZKCP only for resolving a dispute when one of the parties decides to go rogue at the end, only incurring the cost of issuing the proofs in case of misbehavior. | ||
|
|
||
| Note: Watch the full recording with Davidad’s presentation as it is a very complete description (LINK HERE) |
There was a problem hiding this comment.
@davidad would you be ok in sharing presentation for this RFC?
There was a problem hiding this comment.
I just watched the recording of this talk on OZKCP. I’m happy to say I’m actually proud of it and would be happy for it to be published on YouTube or wherever as appropriate. (Btw big thanks to @daviddias for graciously letting me run almost 50% longer than the assigned slot!)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.