cowprotocol / cowprotocol/solana-programs
Once deploying the final program, make sure the state bump is low
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2
- Forks
- 1
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 32
Description
Interestingly, in https://github.com/cowprotocol/solana-programs/pull/111 we see that the benchmarks are significantly decreasing by just bumping the version. This is likely because we were unlucky in the state PDA generation (the diff is exactly 3k CU, two bumps).
This may be unneeded in the future once we store the bump in the PDA. This issue is a reminder to eventually check that we aren't affected by this after releasing the finalized programs.
Contributor guide
No contributing guide indexed for this repository
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
Start by reviewing pull request 111 and its benchmark results, then inspect how the finalized programs generate the state PDA and choose its bump. Compare deployment benchmarks to confirm whether the released programs are affected by the version-dependent bump. Done means documenting that the final deployment uses a low bump or recording the remaining impact and follow-up needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100