feat(state-bloat): cold balance + warm extcodesize

[weiihann]

♨️ Cold BALANCE + Warm EXTCODESIZE

Abuse warm cost forcing small BALANCE cold reads in distinct places and then call warm EXTCODESIZE to all the 24kb contracts: This should be the way to make a client read the most amount of data from DB possible.

Prerequisites

Depends on #41.

The contract-deploy scenario must be run prior to running this scenario in order to deploy as many 24kB contracts as possible. With 45M gas limit, we will touch roughly 10k contracts, so the network must already have that many contracts already.

How it works

1. The contract consists of a function to call BALANCE then EXTCODESIZE on a list of addresses.

contract BalanceThenExtCodeSize{
    function pokeBatch(address[] calldata addresses) external {
        for (uint i = 0; i < addresses.length; i++) {
            address a = addresses[i];
            assembly {
                let b := balance(a)
                let s := extcodesize(a)
                mstore(0x00, b)
            }
        }
    }
}

2. The scenario starts by reading the deployments.json file which is populated with contract addresses deployed with the contract-deploy scenario.
3. Based on the block gas limit, it estimates the amount of addresses to be called via pokeBatch
4. Transaction is sent sequentially, expecting 1 transaction per block.
5. Addresses are not repeated, unless, the deployments.json file doesn't have that many addresses, then it will start from the beginning once the end is reached.

Usage

Run

./bin/spamoor warm-extcodesize  --privkey=<PRIVATE_KEY> --rpchost="http://127.0.0.1:8545"