RT @DDX_Official: DerivaDEX is using the Diamond Standard for managing our smart contracts. The Diamond Standard is a pattern for upgradeability that overcomes existing limitations around storage and contract size, and provides exceptional modularity. https://t.co/dixb5iPG4z
Wow, this feels like smart contracts just took a huge leap forward in maturity. I didn’t even realize that this was possible but now that I see it every contract that needs to be upgradeable should use this.
I think I saw that they currently might be too expensive to use (on twitter) but if that could be resolved this strategy of a team holding on to an administration key with the promise of eventually removing that administration feature feels very crude and downright irresponsible. And any team that wants to do that must have a very good reason to do it.
So, let’s keep our fingers crossed that it can be resolved.
\> Wow, this feels like smart contracts just took a huge leap forward in maturity.
\> I think I saw that they currently might be too expensive to use (on twitter)
Diamonds are not too expensive to use. The discussion on twitter is about a proposal that could make diamonds more expensive to use in the future if some care is not taken.
So the diamond fixes some pitfalls with proxy contracts like local state variable positions. I am considering using this but does anyone know if there is anything stopping me from creating multiple diamonds as facets in my “root” or “bootstrap” diamond? If not I’m considering just a normal proxy contract that will direct to whichever diamond I need.
Wow, that's a neat idea. Using diamonds as your facets to another diamond. I never thought of that before, interesting. Sure you could do it, nothing stopping you. And yea, you could create them from the constructor function of your root diamond.
I invite you to the Diamond Standard discord: [https://discord.gg/kQewPw2](https://discord.gg/kQewPw2)