Skip to content

Conversation

@donequis
Copy link
Contributor

No description provided.

addresses[1] = address(aave);

address[] memory tokens = new address[](3);
tokens[0] = address(0x6B175474E89094C44Da98b954EedeAC495271d0F); //DAI
Copy link
Collaborator

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.

Copy link
Contributor Author

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 {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
contract Beanstattack {
contract BeanstalkAttack {

@nine-december
Copy link
Collaborator

We could also log relevant values/balances during this attack to show how the tokens are flowing on each step

@donequis donequis changed the title (WIP) beanstalk exploit beanstalk exploit Feb 13, 2023
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