Why do we need to separate storage and logic layers for proxy patterns?

Question

I'm recently learning proxy patterns (https://blog.openzeppelin.com/proxy-patterns/) and understand that although it is not possible to upgrade the code of your already deployed smart contract, it is possible to set-up a proxy contract architecture that will allow you to use new deployed contracts as if your main logic had been upgraded. My question is:

Why do we need to separate storage and logic layers for proxy patterns?
What does separating storage and logic layers have relations to contracts being upgradable?

score 0 · Answer 1 · answered Jan 16 '23 at 20:47

0

Why do we need to separate storage and logic layers for proxy patterns?

Most proxies today use DELEGATECALL pattern.

Smart contract loads implementation (code) from one address
Another smart contract address stores data
When the smart contract is upgraded, the address where the code is loaded is changed
The storage address stays the same

answered Jan 16 '23 at 20:47

Mikko Ohtamaa

22,269
6
62
127

You mentioned "smart contract" several times in your post, which "smart contracts" are you referring to for each bullet point? – Will-Up-Vote-If-Good Jan 16 '23 at 20:54
Two smart contracts used in the delegacall proxy pattern. – Mikko Ohtamaa Jan 16 '23 at 20:56
I'm asking which is the proxy and which is the logic contract? – Will-Up-Vote-If-Good Jan 16 '23 at 21:06
Please see the linked answer for details. – Mikko Ohtamaa Jan 17 '23 at 07:56

Why do we need to separate storage and logic layers for proxy patterns?

1 Answers1