Skip to content

Investigate switching from a custom prover to SP1 for BlobstreamX #315

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

Closed
rach-id opened this issue Jun 13, 2024 · 1 comment
Closed

Investigate switching from a custom prover to SP1 for BlobstreamX #315

rach-id opened this issue Jun 13, 2024 · 1 comment
Assignees

Comments

@rach-id
Copy link
Member

rach-id commented Jun 13, 2024

We should investigate the transition from the current BlobstreamX prover to using SP1. This investigation should include:

  • How easy it is to switch
  • If the existing tooling is sufficient
  • If the generated proof will require to be wrapped.
  • Is the EVM verifier the same or different
@rach-id rach-id self-assigned this Jun 13, 2024
@rach-id rach-id added this to core/app Jun 13, 2024
@github-project-automation github-project-automation bot moved this to Needs Triage in core/app Jun 13, 2024
@rach-id rach-id moved this from Needs Triage to Todo in core/app Jun 13, 2024
@evan-forbes
Copy link
Member

my understanding of this is that we are are pursuing the sp1 refactor, and audits can be scheduled after all of the changes for the bitmap are added.

Is this the case? if yes, can we close this issue, if no, can we add further context here around what information is missing to make a decision?

@rach-id rach-id closed this as completed Jul 15, 2024
@github-project-automation github-project-automation bot moved this from Todo to Done in core/app Jul 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

2 participants