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

Solving the level is not possible without knowing the available config options #176

Merged
merged 1 commit into from
Dec 7, 2022
Merged

Solving the level is not possible without knowing the available config options #176

merged 1 commit into from
Dec 7, 2022

Conversation

ChmielewskiKamil
Copy link
Contributor

My biggest struggle with this level was passing the echidna-test: Deploying the contract 0x00a329c0648769A73afAc7F9381E08FB43dBEA72 failed (revert, out-of-gas, sending ether to an non-payable constructor, etc.) error.

It is caused by not passing the initial Ether to the test contract via balanceContract in the config file.

This is pretty obvious to me now, but I think I either missed it while reviewing the materials, or it wasn't showcased.

This PR:

  • adds a small hint that will guide the person to explore the available config options on their own and does not spoil the solution

@ggrieco-tob
Copy link
Member

This looks good to merge.

@montyly
Copy link
Member

montyly commented Dec 7, 2022

Thanks @ChmielewskiKamil, that's a great hint

@montyly montyly merged commit 2a91e6c into crytic:master Dec 7, 2022
@ChmielewskiKamil
Copy link
Contributor Author

@ggrieco-tob @montyly, just a quick question: should I create an issue first and then PR, or is it okay to go straight for the pull request?

@ChmielewskiKamil ChmielewskiKamil deleted the patch-2 branch December 7, 2022 20:20
@montyly
Copy link
Member

montyly commented Dec 7, 2022

If you don't need recommendations, you can directly open a PR ;)

@ChmielewskiKamil
Copy link
Contributor Author

If you don't need recommendations, you can directly open a PR ;)

Awesome! Thanks 🤝

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

Successfully merging this pull request may close these issues.

3 participants