Meanwhile I've realised that it cannot be used by evm2wasm due to the gas cost of call and it also doesn't matter anymore, because evm2wasm is runtime only and the output code size is irrelevant (mostly).
However, since keccak256 is such a widely used feature I think it deserves its well know address (at least for now).
Meanwhile I've realised that it cannot be used by evm2wasm due to the gas cost of
call
and it also doesn't matter anymore, because evm2wasm is runtime only and the output code size is irrelevant (mostly).However, since
keccak256
is such a widely used feature I think it deserves its well know address (at least for now).