-
Notifications
You must be signed in to change notification settings - Fork 11
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
feat: switch between mock and prod circuits #158
base: main
Are you sure you want to change the base?
Conversation
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.
Sorry ik this is WIP, just excited for this to merge :) great work
provers/celestia-prover/README.md
Outdated
|
||
If you update the circuits please regenerate the `elf` files: | ||
|
||
```shell | ||
~/.sp1/bin/cargo-prove prove build --elf-name mock-membership-elf | ||
``` |
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.
❤️ thanks for removing this
const ELF: &'static [u8] = include_bytes!("../../elf/mock-update-client-elf"); | ||
const ELF: &[u8] = include_elf!("mock-membership"); | ||
} | ||
|
||
impl SP1Program for MembershipProgram { | ||
const ELF: &'static [u8] = include_bytes!("../../elf/mock-membership-elf"); |
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.
👍
members = [ | ||
"../programs/sp1/mock-membership", | ||
"../programs/sp1/mock-update-client", | ||
] |
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.
[question] what does including these programs as members of the celestia-prover crate do? They're already members of the root level workspace here. I don't quite understand when/why to include them as members of this crate.
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 think if you want to share the packages that are defined in the parent package is one of the reasons. I don't fully understand either. I was trying to debug compiling the mock programs and was trying to see if any of these would help.
@@ -1,5 +1,5 @@ | |||
#![doc = include_str!("../../README.md")] | |||
#![deny(clippy::nursery, clippy::pedantic, warnings, missing_docs)] | |||
|
|||
pub mod programs; | |||
pub mod programs; |
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.
pub mod programs; | |
pub mod programs; |
Note to self, if this merges after https://github.com/celestiaorg/celestia-zkevm-ibc-demo/pull/153/files#diff-3e3eeb59d344e85d64268133b460af890852ed1aa94c6e049556a9dc3c2aa60cR74-R83 then we can remove those lines from the README b/c this PR auto rebuilds the ELFs |
87f5beb
to
d59d361
Compare
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.
still struggling to make celestia prover compile, due to my lack of knowledge of lifetimes and borrowed variables in rust
Closes #138
Closes #157