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
{{ message }}
Repository navigation
Commit 8d01d68
Browse filesBrowse the repository at this point in the historyBrowse files
Replace dual-impl deployment with version selector
Rather than deploying both V1 and V2 implementations, the script now
reads stark_exchange_migration.version from the config (1 or 2) and
deploys only the selected implementation. Config files updated to add
the version field; input configs set to version 2 (V2 not yet deployed),
deployed configs set to version 1 (V1 currently deployed).
Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
**Note:**Both`StarkExchangeMigration`and `StarkExchangeMigrationV2` are deployed as implementations only (no proxy). The existing StarkEx bridge proxy on-chain must be upgraded to point to an implementation separately (e.g., via governance), at which point `initialize` is called with the appropriate parameters.
92
+
**Note:**The`StarkExchangeMigration`is deployed as an implementation only (no proxy). The existing StarkEx bridge proxy on-chain must be upgraded to point to this implementation separately (e.g., via governance), at which point `initialize` is called with the appropriate parameters. Set `stark_exchange_migration.version` to `1` for `StarkExchangeMigration` or `2` for `StarkExchangeMigrationV2`.
94
93
95
94
### Step 4: Generate Asset Mappings (zkEVM)
96
95
@@ -192,8 +191,8 @@ Deploys the Ethereum contracts for the migration system.
0 commit comments