Change Details

> One thing we still need to do is separate the parts of web that are meant to be downloaded from a keyserver, from the parts of web that are meant to be hosted on our cloud backend. > If it's easy, it would probably be best to put this code actually in landing for now… that might be a good way to start separating these things out. - [[ https://linear.app/comm/issue/ENG-1212#comment-728e9eee | ashoat, on linear ]]

The goal: to sign in with ethereum! to do that we need a signed message from the wallet to pass to the identity service (which is currently native code, not in the browser). This diff adds a top level routing page that includes RainbowKit's Connect Wallet button, as well as a function that will pass the signed message back from the webview to native where the identity service code lives. More context for why we're making these changes in landing and what other options have been considered can be found in [[ https://linear.app/comm/issue/ENG-1212/sign-in-with-ethereum | linear, issue 1212 ]].

> One thing we still need to do is separate the parts of web that are meant to be downloaded from a keyserver,The goal: to sign in with ethereum! from the parts of web that are meanto do that we need a signed message from the wallet to be hosted on our cloud backend. > If it's easypass to the identity service (which is currently native code, it would probably be best to put this code actually in landing for now… that might be a good way to start separating these things out. - [[ https://linear.app/comm/issue/ENG-1212#comment-728e9eee | ashoatnot in the browser). This diff adds a top level routing page that includes RainbowKit's Connect Wallet button, on linear ]]as well as a function that will pass the signed message back from the webview to native where the identity service code lives. More context for why we're making these changes in landing and what other options have been considered can be found in [[ https://linear.app/comm/issue/ENG-1212/sign-in-with-ethereum | linear, issue 1212 ]].