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
When upgrading our contracts, we need to take special care with structs that are used in arrays in storage. Special care should be taken with:
Changing the struct size or layout, since it can lead to memory misalignment issues.
Introducing new fields can only be done in unassigned space within the struct
At the very least, this will affect the Participant and Ritual structs in the Coordinator, but we need to audit all contracts for instances of this problem
Forgot to mention that since we already have contracts deployed, we need acceptance tests to validate that any contract change is backwards compatible on this regard.
When upgrading our contracts, we need to take special care with structs that are used in arrays in storage. Special care should be taken with:
At the very least, this will affect the
Participant
andRitual
structs in the Coordinator, but we need to audit all contracts for instances of this problemSee https://docs.soliditylang.org/en/latest/internals/layout_in_storage.html for reference on storage layout.
The text was updated successfully, but these errors were encountered: