Why ERC-7546 and where it is going.

Transcript

1. Why ERC-7546 and Where It Is Going ecdysis.xyz @shogochiai
2. Traditional Solidity Development - Immutable even if there are bugs Cons Pros - Simple - No overhead - Easy to learn - Lesser bugs
3. The era of “UUPS” - Upgradeable - OpenZeppelin Defender2.0 is available Pros Cons - Caring “Storage Conflict” is very hard - DevOps is harder - 24.576KB contract size limitation can be troublesome - Factory pattern is unavailable - Messy source code and files in folder.
8. In short… - Super duper easier for devs - Gains network effect of many more libraries - Enables try-and-error development (No one cares your proprietary monolithic codebase)
9. Deploy Flow of UCS
15. Security considerations and etc. - Peckshield’s “killswitch” - Dictionary can kill arbitrary implementation getter to stop malicious mempool tx - Local Composability via standardized data types - UCS recommends to align data types with similar-domain dapps - it helps you to build secure dapps easier. - DAOs as a first citizen - DAO development was always “do it later” until now. - UCS Ops can be compatible between EOAs, AAs, and DAOs - Any behavior can be imported to DAOs - MoneyLEGO is unleashed to DAOs as well - Like CurveDAO, more smooth DAO integration will be the new standard of dapps dev.
16. github.com/ecdysisxyz/ucs-contracts See our beta version of UCS and ask anything :)