Skip to content
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

implement commitment-carrying capability #338

Open
srinathsetty opened this issue Dec 16, 2024 · 2 comments
Open

implement commitment-carrying capability #338

srinathsetty opened this issue Dec 16, 2024 · 2 comments

Comments

@srinathsetty
Copy link
Collaborator

@Autoparallel
Copy link

@srinathsetty i see based on this and #339 there seems to be an inclination to support Nebula as well as adopt the ark ecosystem.

I've been curious about a Nebula implementation for both Nova and HyperNova (or NeutronNova) myself. It has some benefits that could be really excellent to use.

With both these said, there is a lot of work going on at Sonobe and in particular the is an issue for non-uniform IVC that points towards using Nebula for an NIVC switchboard.

I understand there is ownership in this repo here for you and your work, but I am curious about cross pollination between these two camps!


On a slightly related note, and my apologies if this question does not belong here, but I'm curious about the details between using Nebula inside of Nova versus using it with NIVC inside of HyperNova. In the case of Nova, you'd create a single master circuit, but disable certain constraints depending on the current step (or some other internal value) and only pay for the cost of the activated R1CS. In the case of HyperNova, you could have individual circuits and don't need a single master circuit. Would this be the main difference?

@srinathsetty
Copy link
Collaborator Author

Hi @Autoparallel

I am curious about cross pollination between these two camps!

We are always open to contributions to the repository, with new features, improvements. Essentially, anything to improve this codebase for use in real applications. Please feel free to open PRs and issues as necessary for cross pollination.

On a slightly related note, and my apologies if this question does not belong here, but I'm curious about the details between using Nebula inside of Nova versus using it with NIVC inside of HyperNova. In the case of Nova, you'd create a single master circuit, but disable certain constraints depending on the current step (or some other internal value) and only pay for the cost of the activated R1CS. In the case of HyperNova, you could have individual circuits and don't need a single master circuit. Would this be the main difference?

The switchboard construction can be used in both Nova and HyperNova in the exact same way. One could additionally make that the HyperNova's sum-check prover does not pay for unused circuits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants