(1/6) Proxy contracts are used all the time in @solidity_lang for many different reasons.
In this post I explain the concept of ‘storage collisions’ and how to avoid them when it comes to proxy contracts.
May your storage be collision resistant from this day forth 💥 🧼 🧽
In this post I explain the concept of ‘storage collisions’ and how to avoid them when it comes to proxy contracts.
May your storage be collision resistant from this day forth 💥 🧼 🧽
(2/6) Storage collisions suck.
They’ll cause all kinds of bugs in your application. 🐜
Many libraries like @OpenZeppelin handle a lot of the internal details for you; but understanding what’s going on under the hood is great to improve your @solidity_lang skills.
They’ll cause all kinds of bugs in your application. 🐜
Many libraries like @OpenZeppelin handle a lot of the internal details for you; but understanding what’s going on under the hood is great to improve your @solidity_lang skills.
(3/6) I know there’s a lot to digest in this diagram but many of the concepts are topics that we’ve already covered.
For example:
Delegatecall ☎️
For example:
Delegatecall ☎️
https://twitter.com/blainemalone/status/1586744968546340864
(4/6) and the fallback function 🕳
https://twitter.com/blainemalone/status/1589817692831514624
(5/6) In later posts I’ll dive into what I looks like to upgrade a @solidity_lang contract.
Yes, they’re immutable but there are clever ways of achieving upgradability which piggybacks on the architecture introduced above.
Yes, they’re immutable but there are clever ways of achieving upgradability which piggybacks on the architecture introduced above.
(6/6) As always, if you like this content follow me for more coming soon!
• • •
Missing some Tweet in this thread? You can try to
force a refresh
