evm: Add tests for proxy

[cuongquangnam]

Summary

• Add functional tests related to proxy smart contracts

Implications

• Storage

  • None

• Consensus

  • None

[canonbrother]

Looks good overall

current: proxy -> implementation

expect to see
request: caller -> proxy -> implementtion

[cuongquangnam]

what do you mean by caller -> proxy -> implementation? @canonbrother
the current way is Externally Owned address -> proxy contract -> implementation contract

[canonbrother]

what do you mean by caller -> proxy -> implementation? @canonbrother

a NIT since we don't have this kind of interaction test

another caller contract to call proxy to call implementation

contract ProxyCaller {

    ProxyContract proxy;

    function Caller(address _proxyAdr) public {
        proxy = ProxyContract(_proxyAdr);
    }

    function doSomething() public {
       proxy.<method>();
    }
}

[cuongquangnam]

What do you mean by NIT?
And IMO, we don't need this kind of contract -> proxy -> implementation test when we already have EOA -> proxy -> implementation test

[canonbrother]

What do you mean by NIT?

NIT: not important

[shohamc1]

What do you mean by NIT?
And IMO, we don't need this kind of contract -> proxy -> implementation test when we already have EOA -> proxy -> implementation test

I think there is some value in having a test that checks functionality for different levels of internal calls.