Replies: 2 comments
-
I believe presets should be upgradeable and anyone can opt out of them by generating a non upgradeable contract with Wizard. Having both versions would defeat the purpose of minimality in terms of maintaining a single preset, opening the door to multiple preset flavors it's a slippery slope to maintain several others. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I'm also in the upgradable-by-default camp. It's easy to remove upgradability, even in a deployed contract, but it's impossible to add. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Even though upgradeability is usually an opt in feature, Starknet's development speed and breaking changes make upgrades almost mandatory for some if not most contracts.
And even though the spirit of our preset contracts is to be as minimal as possible and to redirect every customization request to Wizard for Cairo, the "ready-to-deploy" value proposition is not quite fulfilled if presets are not upgradeable. We received multiple requests for an upgradeable version of our presets, so I'm opening the discussion.
5 votes ·
Beta Was this translation helpful? Give feedback.
All reactions