Skip to content

Decide behaviour when overwriting state during migration #173

@palango

Description

@palango

When a collition happens during copying the L2 contracts into the state we currently overwrite the existing state.

log.Warn("Account already exists with different code and is not whitelisted, overwriting...", "address", k, "oldCode", db.GetCode(k), "newCode", v.Code)

This might not be what we want to do during mainnet migration though. Alternative options include stopping the migration when this happens or logging a warning (although this risks a broken state after migration).

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions