You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm now thinking that with universal NFT/FT we can streamline the deploy process by adding universal contract address as one of the constructor parameters with deploying a connected contract. The idea is you should always deploy the universal contract first, because it's a single required component, and then deploy connected contracts. This way connected-set-universal task will no longer be required. It still makes sense to keep it as contract addresses may change, but you wouldn't need to set manually it after deploying a connected contract.
Remove constructor, use initialize, instead.
The text was updated successfully, but these errors were encountered: