Skip to content

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

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

confidential proof update #16565

wants to merge 2 commits into from

Conversation

zjma
Copy link
Contributor

@zjma zjma commented May 8, 2025

Description

How Has This Been Tested?

Key Areas to Review

Type of Change

  • New feature
  • Bug fix
  • Breaking change
  • Performance improvement
  • Refactoring
  • Dependency update
  • Documentation update
  • Tests

Which Components or Systems Does This Change Impact?

  • Validator Node
  • Full Node (API, Indexer, etc.)
  • Move/Aptos Virtual Machine
  • Aptos Framework
  • Aptos CLI/SDK
  • Developer Infrastructure
  • Move Compiler
  • Other (specify)

Checklist

  • I have read and followed the CONTRIBUTING doc
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I identified and added all stakeholders and component owners affected by this change as reviewers
  • I tested both happy and unhappy path of the functionality
  • I have made corresponding changes to the documentation

Copy link

trunk-io bot commented May 8, 2025

⏱️ 32m total CI duration on this PR
Job Cumulative Duration Recent Runs
rust-targeted-unit-tests 24m 🟩
rust-cargo-deny 3m 🟩🟩
general-lints 2m 🟩🟩
check-dynamic-deps 1m 🟩
semgrep/ci 57s 🟩🟩
file_change_determinator 27s 🟩🟩
permission-check 5s 🟩🟩
permission-check 2s 🟩

settingsfeedbackdocs ⋅ learn more about trunk.io

@@ -1056,6 +1057,15 @@ module aptos_experimental::confidential_proof {
)
}

native fun verify_batch_range_proof_internal(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah!

Copy link
Contributor

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?

Copy link
Contributor

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?

Copy link
Contributor Author

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!(
Copy link
Contributor

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.

Copy link
Contributor

This issue is stale because it has been open 45 days with no activity. Remove the stale label, comment or push a commit - otherwise this will be closed in 15 days.

@github-actions github-actions bot added the Stale label Jun 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants