- Ethereum
- Smart Contract
- dApp(Decentralized Application)
- Turing-Completeness
- the DAO
- Ether
- Gas
- State
- Transaction
- Message
- EOA
- CA
- ECDSA
- Address
- Geth
- Solidity
- EVM
- ABI
- Opcode
- DAG
- Ethash
- Web3
- Parity
- Bootstrap Node
- Mining
- Merkle Patricia Trie
- Bloom Filter
- GasLimit
- Uncle Block
- Receipt
- GHOST Protocol
- RLP
- Difficulty
- MixHash
- Nonce
- Finality
- Scalability
- Sharding
- Plasma
- Casper
- Zero Knoweldge Proof
- Raiden Network
- Whisper
- Swarm
- IPFS
- Metamask
- Etherscan
- EEA
- EIP
- ERC20
- ERC721
- Mnemonic code
- Mist
Message
The message does not need to be stored separately as a virtual object that exists only in the Ethereum runtime environment, and is an object that the contract delivers to other contracts. It looks very similar to a transaction, but it's actually quite different from a transaction. A transaction is characterized by an Externally Owned Account(EOA) calling, while a message is distinct from a transaction and is generated by a contract, not by EOA. You can call the contract from the contract or, depending on the contract, send a message when you transfer the ether from the contract to EOA.
The message contains the following values:
- Message originator (from)
- Message destination (to)
- Ether that is passed along with the message (value)
- Optional data fields (data)
- STARTGAS (gasLimit)