All generic types (block number, time stamp...) that are loaded into/from contract memory should be the Ethereum native type instead of being configurable. #5574
They should use whatever type they are in EVM and the runtime is responsible for conversion and erroring out on overflow.
This also includes topics which are right now read as a SCALE encoded Vec. We don't want to rely on SCALE here. Instead, they should just be packed next to each other in memory. We merely pass the number of topics to the host function.
They should use whatever type they are in EVM and the runtime is responsible for conversion and erroring out on overflow.
This also includes topics which are right now read as a SCALE encoded Vec. We don't want to rely on SCALE here. Instead, they should just be packed next to each other in memory. We merely pass the number of topics to the host function.