scroll-tech / scroll-tech/scroll
[Feat request/coordinator] Record prover performance metrics into `prover_task` table
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 741
- Forks
- 632
- PR merge metrics
- No merged PRs in 30d
Description
This issue has no description.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue body names no files, tests, or entry points. Start by locating the prover coordinator and the prover_task table schema, then trace where prover performance data is available. Done means the requested performance metrics are recorded in prover_task and the relevant behavior is covered by the project’s existing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100