Should a public contract be represented as a single bytecode blob where (as a heuristic) function selector lives in the first few bytes of calldata? Each contract would then start with a compiler-generated jump table that jumps to external contracts based on function selector.
Should a public contract be represented as a single bytecode blob where (as a heuristic) function selector lives in the first few bytes of calldata? Each contract would then start with a compiler-generated jump table that jumps to external contracts based on function selector.