Difference between revisions of "Ethereum address"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
* [[Ethereum Node Records (ENR)]] | * [[Ethereum Node Records (ENR)]] | ||
| + | |||
| + | Ethereum addresses are composed of the prefix "0x" (a common identifier for hexadecimal) concatenated with the rightmost 20 bytes of the [[Keccak-256]] hash of the [[ECDSA]] public key (the curve used is the so-called secp256k1). In hexadecimal, two digits represent a byte, and so addresses contain 40 hexadecimal digits, e.g. 0xb794f5ea0ba39494ce839613fffba74279579268. Contract addresses are in the same format, however, they are determined by sender and creation transaction [[nonce]]. | ||
== See also == | == See also == | ||
Revision as of 13:29, 10 May 2023
Ethereum addresses are composed of the prefix "0x" (a common identifier for hexadecimal) concatenated with the rightmost 20 bytes of the Keccak-256 hash of the ECDSA public key (the curve used is the so-called secp256k1). In hexadecimal, two digits represent a byte, and so addresses contain 40 hexadecimal digits, e.g. 0xb794f5ea0ba39494ce839613fffba74279579268. Contract addresses are in the same format, however, they are determined by sender and creation transaction nonce.
See also
- Ethereum Node Records (ENR), Ethereum address
- Ethereum, Ethereum 2.0, smart contract, EVM, ethash, DAG, Ethereum Classic, Polygon, BAT, Solidity, Gas, Chainlink, Vitalik Buterin, Gavin Wood, Ethereum Foundation, EIPs, ERC, Lighthouse ethereum client, Prysm, Ethereum clients, Ethereum Gossip Protocol, sETH, ETH1 address, Ganache, Aave, Harmony, Account abstraction, Ethereum node, gwei, NatSpec, Precompiles, Dencun, Eth-keyfile
Advertising:
