-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
registry: Add ProveFreshness consensus layer transaction #4916
Conversation
a29b8ba
to
8dd294c
Compare
8dd294c
to
95f4fcf
Compare
Codecov Report
@@ Coverage Diff @@
## master #4916 +/- ##
==========================================
+ Coverage 66.60% 66.69% +0.09%
==========================================
Files 464 464
Lines 50981 51028 +47
==========================================
+ Hits 33955 34033 +78
+ Misses 12834 12818 -16
+ Partials 4192 4177 -15
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly looks good, I would just avoid adding the CLI subcommands to oasis-node.
95f4fcf
to
146ab37
Compare
146ab37
to
7a87fdb
Compare
Add ProveFreshness consensus layer transaction
This is needed for
Client node TEE freshness verification
and should be implemented in the following manner.We can add a (carefully parameter-gated) new transaction (e.g.
registry.ProveFreshness
) that accepts a fixed-size binary blob of 32 bytes and always succeeds without doing any processing or state changes. It should cost a reasonable amount of gas.The enablement parameter should be part of the existing
tee_features
consensus parameter group and be a boolean calledfreshness_proofs
. If it is set to true the new transaction is processed otherwise it is handled as a non-existing transaction (e.g. exactly as currently to avoid breaking consensus before the activation proposal passes).The existing
consensus-tee-pcs
migration should be updated to enable thefreshness_proofs
feature and configure the default gas cost.Test
Tested locally (sub-command
gen_prove_freshness
will be added latter to the CLI repository).If proofs are not enabled, I get the following error.