-
Notifications
You must be signed in to change notification settings - Fork 216
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
beanstalk exploit #50
base: master
Are you sure you want to change the base?
Conversation
addresses[1] = address(aave); | ||
|
||
address[] memory tokens = new address[](3); | ||
tokens[0] = address(0x6B175474E89094C44Da98b954EedeAC495271d0F); //DAI |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we could re-arrange token addresses and any other relevant parameter as global variables for this exploit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that this highlights the importance of the order when calling add_liquidity which could be interesting for readers.
import {TestHarness} from "../../TestHarness.sol"; | ||
import "./Interfaces.sol"; | ||
|
||
contract Beanstattack { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
contract Beanstattack { | |
contract BeanstalkAttack { |
We could also log relevant values/balances during this attack to show how the tokens are flowing on each step |
No description provided.