Lesson 5 - response vs receipt

[alkali333]

I'm struggling to understand the difference between the transaction response and transaction receipt, especially in the code below:

const transactionResponse =  await contract.store("333");
const transactionReceipt = await transactionResponse.wait(1);`

I understand the first line, but what is the second line for?

[krakxn]

Firstly, refer this for context: #1218

Ans.: Put simply, think of transactionReceipt as a variable which has all the details (hash, to, nonce, gasLimit etc.) of the transaction. The naming here is not compulsory, you can name it xyz too. It is just that transactionReceipt is a descriptive and relevant name for it.

A technical description below:

TransactionResponse, inherits Transaction object (elaborated below)

A TransactionResponse includes all properties of a Transaction as well as several properties that are useful once it has been mined.

Transaction

A generic object to represent a transaction.

transaction.hash ⇒ string< DataHexString< 32 > >
The transaction hash, which can be used as an identifier for transaction. This is the keccak256 of the serialized RLP encoded representation of transaction.

transaction.to ⇒ string< Address >
The address transaction is to.

transaction.from ⇒ string< Address >
The address transaction is from.

transaction.nonce ⇒ number
The nonce for transaction. Each transaction sent to the network from an account includes this, which ensures the order and non-replayability of a transaction. This must be equal to the current number of transactions ever sent to the network by the from address.

transaction.gasLimit ⇒ BigNumber
The gas limit for transaction. An account must have enough ether to cover the gas (at the specified gasPrice). Any unused gas is refunded at the end of the transaction, and if there is insufficient gas to complete execution, the effects of the transaction are reverted, but the gas is fully consumed and an out-of-gas error occurs.

transaction.gasPrice ⇒ null | BigNumber
The price (in wei) per unit of gas for transaction.

For EIP-1559 transactions, this will be null.

transaction.maxFeePerGas ⇒ BigNumber
The maximum price (in wei) per unit of gas for transaction.

For transactions that are not EIP-1559 transactions, this will be null.

transaction.maxPriorityFeePerGas ⇒ BigNumber
The priority fee price (in wei) per unit of gas for transaction.

For transactions that are not EIP-1559 transactions, this will be null.

transaction.data ⇒ BytesLike
The data for transaction. In a contract this is the call data.

transaction.value ⇒ BigNumber
The value (in wei) for transaction.

transaction.chainId ⇒ number
The chain ID for transaction. This is used as part of EIP-155 to prevent replay attacks on different networks.

For example, if a transaction was made on ropsten with an account also used on homestead, it would be possible for a transaction signed on ropsten to be executed on homestead, which is likely unintended.

There are situations where replay may be desired, however these are very rare and it is almost always recommended to specify the chain ID.

transaction.r ⇒ string< DataHexString< 32 > >
The r portion of the elliptic curve signatures for transaction. This is more accurately, the x coordinate of the point r (from which the y can be computed, along with v).

transaction.s ⇒ string< DataHexString< 32 > >
The s portion of the elliptic curve signatures for transaction.

transaction.v ⇒ number
The v portion of the elliptic curve signatures for transaction. This is used to refine which of the two possible points a given x-coordinate can have, and in EIP-155 is additionally used to encode the chain ID into the serialized transaction.

[pacelliv]

@krakxn TransactionReceipt is only available after the block is mined and TransactionResponse contains transaction details before the block is mined?

[krakxn]

As above, "A TransactionResponse includes all properties of a Transaction as well as several properties that are useful once it has been mined."

TransactionReceipt is similar, it has all the essential properties (as above) of the said transaction. Also, IIRC this is not really an object unlike TransactionResponse, rather just a function for the receipt.