Skip to content
This repository has been archived by the owner on Oct 31, 2023. It is now read-only.

CRS should fetch only what is needed #162

Closed
1 task done
phated opened this issue May 5, 2023 · 1 comment · Fixed by #139 or #165
Closed
1 task done

CRS should fetch only what is needed #162

phated opened this issue May 5, 2023 · 1 comment · Fixed by #139 or #165
Assignees
Labels
enhancement New feature or request

Comments

@phated
Copy link
Contributor

phated commented May 5, 2023

Problem

Currently, the backend fetches the entirety of transcript00, no less. This is a huge download for small circuits.

Proposed solution

Instead of fetching all of transcript00, we should instead fetch only the amount of the G1 that is needed for a given circuit.

Alternatives considered

No response

Additional context

This is being done in combination with #139

Submission Checklist

  • Once I hit submit, I will assign this issue to the Project Board with the appropriate tags.
@phated phated added the enhancement New feature or request label May 5, 2023
@github-project-automation github-project-automation bot moved this to 📋 Backlog in Noir May 5, 2023
@phated phated self-assigned this May 5, 2023
@phated phated moved this from 📋 Backlog to 🏗 In progress in Noir May 5, 2023
@phated phated changed the title CRS should fetch only what is needed and more than transcript00 if needed CRS should fetch only what is needed May 15, 2023
@phated
Copy link
Contributor Author

phated commented May 15, 2023

Splitting this into 2 issues, one for fetching the range and one for fetching more than transcript00

This was linked to pull requests May 15, 2023
@github-project-automation github-project-automation bot moved this from 🏗 In progress to ✅ Done in Noir May 19, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
Archived in project
1 participant