fe

Yeah looking at elements.rs, it appears that they have the translation layer I alluded to: https://github.com/ethereum/fe/blob/bfeffe82b4f8623330c1ebb1... It's not obvious to me though and I couldn't find documentation for ABI compatibility. For example, does delegatecall to solidity work? That requires that Fe also use the same "binary" layout for storage in which slot index is used to generate the storage hash: https://docs.soliditylang.org/en/v0.8.10/internals/layout_in...

For those not familiar with Solidity, there is a peculiarity in the "ABI" that makes it painful to interop between languages. In solidity, there are types called "contracts" which are like classes in other languages. When you call a function in a different contract, the dispatch is routed using the first few bytes of the has of the signature [1]. For example, to transfer ERC-20 tokens you dispatch using `hash(transfer(address, uint256))[:4]`, meaning that you put those first four bytes at the beginning of the data that you pass to the receiving contract. Just like the native world, this causes a problem when you try to interface between different languages. In Fe, the types have different names so this hashing scheme can't work without a translation layer. From some of the issues it looks like interoperability may be a problem [2]. That's