Why do we mine a new block to confirm Tx for NFT marketplace with Moralis server ?

[TilakMaddy]

All this while, in our deploy scripts we only used txReceipt = tx.wait(1) and that would wait till we have 1 block confirmations. ....Which implies block conformations happen automatically. Then why is it that when it comes to moralis local dev chain server we have to manually mine a block with evm_mine (the whole moveBlocks function that has ben created) for confirmation to become True. ? What is going on here @PatrickAlphaC ?

Also, on a side tangent, this course has been great so far!

[PatrickAlphaC]

Great question!

From what I've seen, it's what it's counting as a confirmation.

• Hardhat counts its own block as a confirmation.
• Moralis wants another block on top of the block it's in.

I think hardhat is the "correct" one, but it's sort of superfluous in any case.

[PatrickAlphaC]

Let me know if this answers your question.

[TilakMaddy]

Yup answers it !! (^-^)/ 🐟

[TilakMaddy]

But what do you mean by "correct" one ? I think moralis just needs too many block confirmations. So we do it manually.... https://docs.moralis.io/moralis-dapp/automatic-transaction-sync/historical-transactions#unconfirmed-transactions (maybe add that link in the notes)

[PatrickAlphaC]

Oooo, nevermind on what I said for "correct" then ahah.

Perhaps moralis has hardhat to be configured to 2 confirmations? This would be great to ask on their forum.