-
Notifications
You must be signed in to change notification settings - Fork 3.8k
confidential proof update #16565
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
base: main
Are you sure you want to change the base?
confidential proof update #16565
Conversation
⏱️ 32m total CI duration on this PR
|
@@ -1056,6 +1057,15 @@ module aptos_experimental::confidential_proof { | |||
) | |||
} | |||
|
|||
native fun verify_batch_range_proof_internal( |
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.
Ah!
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.
And you would just map this to the same Rust function, right?
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.
And we would never enable batch bulletproofs in ristretto255_bulletproofs
?
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.
we can also "always abort" there, and reuse the feature flag for protecting this new native.
@@ -113,5 +114,10 @@ pub fn all_natives( | |||
); | |||
} | |||
|
|||
add_natives_from_module!( |
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.
I don't see anything here that indicates confidential_proof
lies in 0x7
or aptos_experimental
...
Even so, will this work on testnet
and mainnet
? Since 0x7
is experimental and not deployed there.
This issue is stale because it has been open 45 days with no activity. Remove the |
Description
How Has This Been Tested?
Key Areas to Review
Type of Change
Which Components or Systems Does This Change Impact?
Checklist