fix(contracts): use currect messenger proxy name

99c0693a · ben-chain · Kelvin Fichter · c73d36f1 · 99c0693a
Commit 99c0693a authored Oct 22, 2021 by ben-chain Committed by Kelvin Fichter Nov 10, 2021
Hide whitespace changes
Inline Side-by-side

Showing with 8 additions and 4 deletions

120-initialize-Proxy__L1CrossDomainMessenger.ts ...ts/deploy/120-initialize-Proxy__L1CrossDomainMessenger.ts +8 -4

No files found.
--- a/packages/contracts/deploy/120-initialize-Proxy__L1CrossDomainMessenger.ts
+++ b/packages/contracts/deploy/120-initialize-Proxy__L1CrossDomainMessenger.ts
@@ -11,10 +11,14 @@ const deployFn: DeployFunction = async (hre) => {
  // There is a risk that on a fresh deployment we could get front-run,
  // and the Proxy would be bricked. But that feels unlikely, and we can recover from it.
  console.log(`Initializing Proxy__L1CrossDomainMessenger...`)
-  const proxy = await getLiveContract(hre, 'Proxy__L1CrossDomainMessenger', {
+  const proxy = await getLiveContract(
-    iface: 'L1CrossDomainMessenger',
+    hre,
-    signerOrProvider: deployer,
+    'Proxy__OVM_L1CrossDomainMessenger',
-  })
+    {
+      iface: 'L1CrossDomainMessenger',
+      signerOrProvider: deployer,
+    }
+  )
  const libAddressManager = await getLiveContract(hre, 'Lib_AddressManager')
  await proxy.initialize(libAddressManager.address)