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

Add local fuzz testing for all supported pools #1614

Open
3 of 5 tasks
slundqui opened this issue Jul 17, 2024 · 4 comments
Open
3 of 5 tasks

Add local fuzz testing for all supported pools #1614

slundqui opened this issue Jul 17, 2024 · 4 comments
Assignees

Comments

@slundqui
Copy link
Contributor

slundqui commented Jul 17, 2024

We currently do local fuzz testing for erc4626 and steth pools. Ideally we would add all supported pools to the list of pools we're fuzzing.

One issue is that local fuzz testing is dependent on mock yield sources. Ideally we would use existing yield sources, likely from a mainnet fork.

Additional pools needed to support:

  • aave
  • ezeth
  • lseth
  • morpho-blue
  • reth
@slundqui slundqui self-assigned this Jul 17, 2024
@slundqui
Copy link
Contributor Author

We decided to deploy the current solidity tests as contract themselves to expose various functions needed by python for fuzz testing:
delvtech/hyperdrive#1108

@jalextowle
Copy link
Contributor

Infra Tasks:

  • Set up a dedicated Alchemy URL for mainnet fork fuzzing

Agent0 Tasks:

  • Integrate with fuzz harness

@slundqui
Copy link
Contributor Author

slundqui commented Aug 6, 2024

Due to issues with the fuzzing harness, we've decided to move to fuzzing directly on testnet pools. #1637 adds support for this.

Still need more work to (1) fuzz across initial pool config conditions, and (2) simulate advancing time.

@slundqui
Copy link
Contributor Author

slundqui commented Aug 6, 2024

Need aave and lseth deployed on testnet to fuzz. @mcclurejt

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

2 participants