Output transaction sequence for reaching vulnerable state

Description

Add an option that outputs the transactions for reaching each vulnerable state.

Background

We already have all the data we need from the solver. It should be trivial to reformat this output for various purposes:

• As a Truffle test;
• As an executable exploit;
• As a script that deploys the contract to Ganache and attempts to exploit the issue.

Scope

Compose the call data for each message call in the transaction sequence. For example, running an assert test on the following example should produce three transactions:

contract Token{

    mapping(address => uint) public balances;
    function airdrop() public{
        balances[msg.sender] = 1000;
    }

    function consume() public{ 
        require(balances[msg.sender]>0);
        balances[msg.sender] -= 1;
    }

    function backdoor() public{
        balances[msg.sender] += 1;
    }
 
   function test_invariants() {
      assert(balances[msg.sender] <= 1000);
  }
}

[nbanmp]

I’m here @gitcoinbot

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

The funding of 2.2 ETH (463.0 USD @ $210.45/ETH) attached to this issue has been approved & issued to @nbanmp.

• Learn more on the Gitcoin Issue Details page
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $59,251.82 more funded OSS Work available on the Gitcoin Issue Explorer