Design Update: Maintain compatibility with existing standards, libraries, and systems

[mudgen]

I added a new section to the Design documentation of Compose about maintaining compatibility with existing standards, libraries and systems. Here: https://github.com/Perfect-Abstractions/Compose?tab=readme-ov-file#maintain-compatibility-with-existing-standards-libraries-and-systems

[pellyadolfo]

Just a quick comment now that there is a discussion board. OpenZeppelin contracts can be directly adapted by just removing the embedded storage in their variables. Only be aware of license. Just need to solve some key issues and Compose can take all EVM based chains.

[mudgen]

Yes, keeping in mind that we write our contracts much differently than OZ.

We want to maintain a certain, sensible compatibility with OZ contracts so existing users and systems are not surprised if our contracts behave differently.

But we want to write our contracts Compose style (with Solidity feature ban etc.) which is much different than how OZ contracts are written.

[pellyadolfo]

indeed indeed, rules are different than OZ's. Transparency and trusted security are much needed in blockchain. Compose's vision can change everything.