You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our case, we'd most likely set the Kernel contract to be the "manager" of a proxy, and users would have to access any "management" functionality through the Kernel (e.g. provide proxy address and calldata to the kernel).
However, this might be too much of a UX loss for a vulnerability that has a very, very low probability.
The text was updated successfully, but these errors were encountered:
See zeppelinos/zos-lib#36.
In our case, we'd most likely set the Kernel contract to be the "manager" of a proxy, and users would have to access any "management" functionality through the Kernel (e.g. provide proxy address and calldata to the kernel).
However, this might be too much of a UX loss for a vulnerability that has a very, very low probability.
The text was updated successfully, but these errors were encountered: