Karim Agha

EVM runtime: Map FVM context info to EVM opcodes

2

Implement opcodes that query the transaction context: - `ORIGIN` - `CALLVALUE` - `ADDRESS` - `BLOCK_NUMBER` - `TIMESTAMP` - `CALLER` - `BLOCKHASH` - `CHAINID` - `BASEFEE` - `DIFFICULTY` - `GASLIMIT`

First the EVM constructor code runs on the bridge, the bridge creates a temporary `Hamt` that is used as the state store for the constructor. When the constructor runs to...

EVM runtime: Implement value transfers

2

Sending tokens between two accounts without invoking any contract. This should be all implemented on the bridge level.

EVM runtime: Implement DELEGATECALL

15

Running an EVM bytecode in the context of another actor's state CID.

1. Deploy an EVM contract. 2. Invoke a method on the contract using Solidity calling conventions. 3. Inspect and verify returned values. 4. Ensure that state changes are persisted across...

EVM runtime: Implement FVM storage mappings for EVM OPCODES

4

Implement opcodes `SSTORE`, `SLOAD`, ~~`CREATE`, `CREATE2`~~ as IPLD operations.

Related: https://github.com/filecoin-project/ref-fvm/issues/728