Lesson 5: Brownie SimpleStorage

[ManiBharathiSS]

We are waiting one block to conform when we are calling the store function. But why we don't tx.
wait(1) after deploying a contract since it's also transaction?

And why we don't tx.wait(1) after calling store function before assert in testing? @PatrickAlphaC

[cromewar]

Hello @ManiBharathiSS
Nice question, this depends a lot on the network we are deploying/testing.

On the test we use accounts[0] which is a local ganache account, as the blockchain is locally running on your computer your transaction will not have to wait till the process is done as is instant, so no need to tx.wait().

Regarding why we don't don't wait when deploying, the reason is because the deploy transaction is "special", when you assign
simple_storage = SimpleStorage.deploy(), you won't be able to use the functions on the contract unless the contract is deployed, for example trying to use the store function when the contract does not exists on the blockchain.

So when you deploy a contract with brownie this happens:

if the address exists, it means the transaction was successful, so again.. no need to tx.wait().

We use Wait on already deployed contracts, because the change of the state of a variable, mapping or whatever.. can take some time, and the tx.wait() ensures new blocks were added to the blockchain, if new blocks were added it means the transaction was correct.

[ManiBharathiSS]

Thanks @cromewar for explaining it so clear . Understood perfectly 👍