Why and when should we use tx.wait()

[0xClouds]

There are many times when Patrick uses transactionResponse.wait(1)
Can anyone explain why and when we should be waiting, I removed this function and all of the scripts still ran smoothly.

[iangechuki]

Am not an expert in this but I think its kind of a good convention to use transactionResponse.wait(1) to wait for the promise to resolve.Where I noticed it was important is when we want to obtain something from the receipt like const txReceipt=await txReponse.wait(1) .Lets say its a suscriptionId const subscriptionId=txReceipt.events[0].args.subId.When you get to the later lessons you will see this.

[zeroxvee]

For 2 reasons:

1. We can get the transaction receipt
2. Transaction confirmation, because of the Ethereum consensus mechanism.

https://ethereum.org/en/developers/docs/consensus-mechanisms/
Short video on the subject: https://www.youtube.com/watch?v=gP5zcHD8tJU

Now, nodes have to validate miners work and agree which chain of blocks continues as the main one. On average it's considered at least 6 block to be enough for a transaction to be confirmed.
https://ethereum.org/en/developers/docs/consensus-mechanisms/pow/#pow-and-mining

After the merge it will be a finalized block at or after which your transaction can be considered confirmed, such a block has to be accepted as canonical by >2/3 of validators