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
@JagoFigueroa we require QA on this 🙏🏻 . The way to test it would be to deploy a Safe v1.1.1 and v1.3.0 (not L2) on Polygon, use the command update_to_l2 0x1Ba30910CE8Eb45b276aa7c89C38FC52228B85CB (that's the address for the not official migration contract in Polygon deployed by me) and then use the Safe with our official UI and check transactions show as expected
Hola team! Working nicely for me, I updated 2 safes on Polygon one from 1.1.1 and another from 1.3.0 and was able to transact with them without any issues once updated from the CLI. Also tried tx-service mode and was able to update on UI from the queue.
What is needed?
Add command or include in upgrade command, support to migrate a non L2 Safe to L2 Safe
Related issues
safe-global/safe-transaction-service#1703
The text was updated successfully, but these errors were encountered: