Eddie
Eddie
If this was not expected, then this should be sorted with LiFi. WETH was delivered on destination, swapped to ETH, and delivered to this address: https://arbiscan.io/address/0x2640fccb642028491fd80b7ba8b4cca19d425ab6
Seems like LiFi receiver contract, let's keep monitoring.
> I believe the way we are adding signers as optional param, We will be only covering the txs that are coming from connext bridge UI. And for that UI...
Reopening until we have NPM package available and the UI task done.
Want to update UIs to use this after we enable logs in #5612.
Test token on Blast-Sepolia: https://testnet.blastscan.io/address/0x52941fDC123eC1B8Ab731AC6EdCbB2192F1e5854/contract/168587773/writeContract
Renzo will deploy ezETH on Blast tomorrow.
Should resolve after updating their router based on new guide.
Examples of transactions impacted by routers not bidding: - https://app.zenhub.com/workspaces/core-engineering-6272a34e0368a200141cd949/issues/gh/connext/monorepo/5510 - https://app.zenhub.com/workspaces/core-engineering-6272a34e0368a200141cd949/issues/gh/connext/monorepo/5543 - https://app.zenhub.com/workspaces/core-engineering-6272a34e0368a200141cd949/issues/gh/connext/monorepo/5482 - https://app.zenhub.com/workspaces/core-engineering-6272a34e0368a200141cd949/issues/gh/connext/monorepo/5478
Scroll is on mainnet staging environment atm. Registry can be shared between staging/prod but adapter instance needs the specific Connext contract. Will be left as TODO in branch `scroll-audit-fixes`.