We can see how addresses are created in the Ethereum Yellow paper's Appendix F. Signing Transactions. First, it is assumed that the sender has a 32-byte private key. Given that we are discussing bytes rather than characters, first option is therefore already incorrect. A 64-byte key, also known as a public key, is produced when we run ECSDAPUBKEY. Therefore, second option is the correct one. The 160 rightmost bits of the public key's Keccack hash constitute the address. To put it another way, the hash's final 40 hex characters, or the right 20 bytes, as 1 byte is 8 bits and 20 bytes are equivalent to 160 bits
Division rounds to zero in solidity. Consequently, it is trancated. Accordingly, int256(-5) / int256(2) = int256 (-2). This time, the answer would be -2. The best answer is therefore the third option.
