SDK not working for Mode withdraws

[jtfirek]

SDK not working for Mode withdraws

[jtfirek]

I have found a diff between the mode deployment and other OP stack chains:

Other OP stack chains have 0x4200000000000000000000000000000000000007 as the L2CrossDomainMessenger address and Mode's is deployed at:
L2CrossDomainMessenger 0xC0d3c0d3c0D3c0D3C0d3C0D3C0D3c0d3c0d30007

Is it possible that this diff is what is causing the SDK to not work for Mode?

[tynes]

I have found a diff between the mode deployment and other OP stack chains:

Other OP stack chains have 0x4200000000000000000000000000000000000007 as the L2CrossDomainMessenger address and Mode's is deployed at: L2CrossDomainMessenger 0xC0d3c0d3c0D3c0D3C0d3C0D3C0D3c0d3c0d30007

Is it possible that this diff is what is causing the SDK to not work for Mode?

0xC0d3c0d3c0D3c0D3C0d3C0D3C0D3c0d3c0d30007 is the implementation and not the proxy. You should interact with 0x4200000000000000000000000000000000000007.

I am not sure why this problem would exist on mode and not other chains. It is likely a bug in the sdk. cc @smartcontracts. Perhaps something with an off by one

You should consider using viem for this as the sdk has been deprecated and is no longer maintained

[jtfirek]

Do you have any code examples for constructing the proof for withdraws via viem @tynes ?

[tynes]

Do you have any code examples for constructing the proof for withdraws via viem @tynes ?

https://github.com/wevm/viem/blob/d6ae8fa770679306d1eb86b5fb24d3bf2c764aa6/site/pages/op-stack/guides/withdrawals.md

This took a quick search thru their docs page to find

[jtfirek]

Thanks