List of hacks for perf testing
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Yearn 2025 (2800 steps)
0x78921ce8d0361193b0d34bc76800ef4754ba9151a1837492f17c559f23771c43
Balancer 2025 (1700 steps)
0x53fe7ef190c34d810c50fb66f0fc65a1ceedc10309cf4b4013d64042a0331156
Euler 2023 (151 calls)
0xc310a0affe2169d1f6feec1c63dbc7f7c62a887fa48795d327d4d2da2d6b111d
Solv protocol (2395 calls)
0x44e637c7d85190d376a52d89ca75f2d208089bb02b7c4708ad2aaae3a97a958d
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
The issue provides four protocol labels and transaction hashes for performance testing, but names no file, test, or entry point. First locate where performance-test inputs are stored or consumed; the issue does not define the required change or what completion should look like.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100