Does it makes any sense to develop tests for deployed contracts on hardhat stand alone node instead of the classic way of deploying then testing in the short ephemerous hardhat node?

i would think you can better represent the network on a mainnet forked hardhat node

Makes very little difference unless your contract have already deployed other contracts as dependencies

By very little difference, I meant the difference across evms, like for l2s

thanks!
By the way, could you see any reason why i am able to deploy on bsc testnet using pancakeSwapv3 deploy script but i get stopped midway on goerli with the following error:

ProviderError: INTERNAL_ERROR: could not replace existing tx
at HttpProvider.request (C:\Users\****\Desktop\pancakev3\pancake-v3-contracts\node_modules\hardhat\src\internal\core\providers\http.ts:88:21)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at EthersProviderWrapper.send (C:\Users\****\Desktop\pancakev3\pancake-v3-contracts\node_modules\@nomiclabs\hardhat-ethers\src\internal\ethers-provider-wrapper.ts:13:20)
error Command failed with exit code 1.

i checked the arguments and they are correct

I kind of suspect this has to do with the differences between blockchains but i have no idea why

INTERNAL_ERROR: could not replace existing tx

Probably have a pending tx on goerli. Try with a different wallet and rpc url

https://reflect-contract-doc.netlify.app/