Last updated
Last updated
A Networkish may be any of the following:
a object
the name of a common network as a string (e.g. "mainnet"
)
the chain ID a network as a number; if the chain ID is that of a common network, the name
will be populated, otherwise, the default name "unknown"
is used
A Network represents a Hedera network.
The human-readable name of the network, such as mainnet
. If the network name is unknown, this will be "unknown"
.
The Chain ID of the network.
Used thoroughly in the hethers library to represent accounts/contracts/addresses in various forms.
The address to filter by, or null
to match any address.
The topics to filter by or null
to match any topics.
Each entry represents an AND condition that must match, or may be null
to match anything. If a given entry is an Array, then that entry is treated as an OR for any value in the entry.
See Filters for more details and examples on specifying complex filters.
The starting timestamp (inclusive) to search for logs matching the filter criteria.
The end timestamp (inclusive) to search for logs matching the filter criteria.
The index of this log in the transaction.
The address of the contract that generated this log.
The data included in this log.
The list of topics (indexed properties) for this log.
The transaction hash of the transaction of this log.
The index of this log in the transaction.
The index of this log in the transaction.
A transaction request describes a transaction that is to be sent to the network or otherwise processed.
All fields are optional and may be a promise which resolves to the required type.
The address this transaction it to.
The address this transaction is from.
The transaction data.
The amount (in tinybars) this transaction is sending.
The maximum amount of gas this transaction is permitted to use.
The chain ID this transaction is authorized on.
Types will always be 0
in Hedera since envelope types are not supported as of now.
Currently not supported in Hedera.
Any custom data as key-value pairs.
inherits Transaction
A TransactionResponse includes all properties of a Transaction as well as several properties that are useful once it has been mined.
The timestamp of the transaction. If the transaction has not been mined, this is null
.
The serialized transaction. This may be null as some backends do not rpopulate it. If this is required, it can be computed from a TransactionResponse.
Resolves to the TransactionReceipt once the transaction has been mined. If timeout is not provided, and the transaction has not been mined, null
is returned.
If the transaction execution failed (i.e. the receipt status is 0
), a CALL_EXCEPTION
error will be rejected with the following properties:
error.transaction
- the original transaction
error.transactionHash
- the hash of the transaction
error.receipt
- the actual receipt, with the status of 0
The address this transaction is to. This is null
if the transaction was an init transaction, used to deploy a contract.
The address this transaction is from.
If this transaction has a null
to address, it is an init transaction used to deploy a contract, in which case this is the address created by that contract.
To compute a contract address, the getContractAddress utility function can also be used with a TransactionResponse object, which requires the transaction nonce and the address of the sender.
Types will always be 0
in Hedera since envelope types are not supported as of now.
The amount of gas actually used by this transaction.
The transaction hash of this transaction.
All the logs emitted by this transaction.
This is the sum of the gas used by the transaction, equals the gasUsed
property.
This is generally of little interest to developers.
A , which includes all the addresses and topics included in any log in this transaction.
This is true if the block is in a block.
The status of a transaction is 1 is successful or 0 if it was reverted. Only transactions included in blocks have this property.