All Types

org.apache.tuweni.eth.Address

An Ethereum account address.

org.apache.tuweni.eth.Block

An Ethereum block.

org.apache.tuweni.eth.BlockBody

An Ethereum block body.

org.apache.tuweni.eth.BlockHeader

An Ethereum block header.

org.apache.tuweni.eth.Hash

An Ethereum hash.

org.apache.tuweni.eth.Log

A log entry is a tuple of a logger’s address (the address of the contract that added the logs), a series of 32-bytes log topics, and some number of bytes of data.

org.apache.tuweni.eth.LogsBloomFilter

Bloom filter implementation for storing persistent logs, describes a 2048-bit representation of all log entries of a transaction, except data. Sets the bits of the 2048 byte array, where indices are given by: The lower order 11-bits, of the first three double-bytes, of the SHA3, of each value. For instance the address "0x0F572E5295C57F15886F9B263E2F6D2D6C7B5EC6" results in the KECCAK256 hash "bd2b01afcd27800b54d2179edc49e2bffde5078bb6d0b204694169b1643fb108", of which the corresponding double-bytes are: bd2b, 01af, cd27, corresponding to the following bits in the bloom filter: 1323, 431, 1319

org.apache.tuweni.eth.Transaction

An Ethereum transaction.

org.apache.tuweni.eth.TransactionReceipt

A transaction receipt, containing information pertaining a transaction execution.

Transaction receipts have two different formats: state root-encoded and status-encoded. The difference between these two formats is that the state root-encoded transaction receipt contains the state root for world state after the transaction has been processed (e.g. not invalid) and the status-encoded transaction receipt instead has contains the status of the transaction (e.g. 1 for success and 0 for failure). The other transaction receipt fields are the same for both formats: logs, logs bloom, and cumulative gas used in the block. The TransactionReceiptType attribute is the best way to check which format has been used.