0xduality

Per @mds1 request on https://github.com/foundry-rs/foundry/issues/1078 here are some [additional precompiles](https://docs.avax.network/subnets/customize-a-subnet#precompiles) for Avalanche evm-based subnets. A list of such subnets is maintained [here](https://github.com/ava-labs/subnet-evm/tree/master/networks).

Avalanche subnets that use the evm have these precompiles - 0x0200000000000000000000000000000000000000 - 0x0200000000000000000000000000000000000001 - 0x0200000000000000000000000000000000000002 - 0x0200000000000000000000000000000000000003 More details on the interfaces are [here]( https://docs.avax.network/subnets/customize-a-subnet#restricting-smart-contract-deployers)

@mattsse I believe you can find all this information [here](https://docs.avax.network/subnets/customize-a-subnet#precompiles)

Wondering if it would be possible to support both early binding (all keys specified upfront) and late binding (no keys upfront). What would that mean? No keys specified basically means...