Saving the candy machine public key to the cache before sending the deploy transaction allows the cli to automatically detect if the deploy succeeded even if the transaction times out.
Behviour change:
Providing a valid public key that is not a candy machine in the cache results in a warning message and new candy machine being deployed.
The old behaviour was to print the message Candy machine from cache does't exist on chain!
I really like the idea!
Quite simple workaround but will ease the live of cm creators on congestion days. And it will also reduce some super questions and confusion in discord.
Thank you Kartik!
Saving the candy machine public key to the cache before sending the deploy transaction allows the cli to automatically detect if the deploy succeeded even if the transaction times out.
Behviour change: Providing a valid public key that is not a candy machine in the cache results in a warning message and new candy machine being deployed. The old behaviour was to print the message
Candy machine from cache does't exist on chain!