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

Investigate BlobstreamX contracts refactoring #317

Open
rach-id opened this issue Jun 13, 2024 · 2 comments
Open

Investigate BlobstreamX contracts refactoring #317

rach-id opened this issue Jun 13, 2024 · 2 comments
Assignees

Comments

@rach-id
Copy link
Member

rach-id commented Jun 13, 2024

We should investigate if it is possible to simplify the BlobstreamX smart contracts architecture so that they're easy to deploy for new chains.

@rach-id rach-id self-assigned this Jun 13, 2024
@evan-forbes
Copy link
Member

@rach-id when you get the chance, do mind adding / updating the acceptance criteria here to be more specific? Do we know what else is needed here before making a decision? do we know what we need from any refactors to make this worth it? Will switching to sp1 help this?

@rach-id
Copy link
Member Author

rach-id commented Jul 15, 2024

Before SP1, we had the following contracts:

  1. Circuit Verifier: verifies the proofs
  2. SuccinctGateway: which is a registry for circuit verifiers and used to access control the verifiers
  3. BlobstreamX contract

With SP1, we will have:

  1. SP1 universal verifier: which verifies SP1 proofs. So we no longer need to deploy a verifier per circuit
  2. BlobstreamX: where the logic in SuccinctGateway got moved to BlobstreamX

I don't think we can simplify the contracts anymore after moving to SP1. So I think we can close this.

Let me know if you agree so that I close.

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

No branches or pull requests

2 participants