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

Sphinx wishlist #107

Open
4 tasks
arthurpaulino opened this issue Jun 24, 2024 · 0 comments
Open
4 tasks

Sphinx wishlist #107

arthurpaulino opened this issue Jun 24, 2024 · 0 comments

Comments

@arthurpaulino
Copy link
Member

arthurpaulino commented Jun 24, 2024

While our proving pipeline is still evolving, let's use this issue to list things that don't spark joy on the Sphinx's prover.

Note: please, only mark items as resolved once the change is done on Sphinx and successfully integrated on this repo.

  • There shouldn't be a requirement for one chip to be called "CPU"
  • There shouldn't be a requirement for at least one chip to produce a preprocessed trace
  • ShardingConfig should not be required to be Default. The fact that Sphinx initializes a default instance (using env vars) is an obscure hack that leads to multiple headaches
  • Trace generation should not happen twice
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

1 participant