Solidity Variables and Opcodes
The table below defines the mapping of Solidity variables and operation codes to Hedera.
The address is a mapping of shard.realm.number (0.0.10) into a 20 byte Solidity address. The address can be a Hedera account ID or contract ID in Solidity format.
The index of the record file (not recommended use
The transaction consensus timestamp.
The address of the Hedera contract ID or account ID in Solidity format that called this contract. For the root level or for delegate chains that go to root it is the account ID paying for the transaction.
The value associated to the transaction associated in tinybar.
The account ID paying for the transaction, regardless of depth.
Fixed (varies with the global fee schedule and exchange rate).
Address will not be reusable due to Hedera’s account numbering policies.
Precompile contract addresses will report no code, including HTS System contract.
Precompile contract addresses will report the empty code hash.
This opcode will operate as expected with no change from Ethereum Mainnet.
Contracts may no longer use
The JSON RPC Relay
msg.valueuses 18 decimals when it returns HBAR. This was to provide an equivalent decimal length for web3 tools used across multiple EVM chains. As a result, the
gasPricealso uses 18 decimal places since it is only utilized from the JSON RPC Relay. Refer to the HBAR page for a table of Hedera APIs and the decimal places they return.