Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to support user actually signs the message #13

Open
llllllluc opened this issue Apr 5, 2024 · 0 comments
Open

How to support user actually signs the message #13

llllllluc opened this issue Apr 5, 2024 · 0 comments

Comments

@llllllluc
Copy link

llllllluc commented Apr 5, 2024

Hi really like this tutorial, i think it really shows how easy it is to create a rollup, it's just like writing a web2 api server. One question I have is how to let users actually sign the message they send (e.g. user needs to connect metamask or keplr to sign a tx in order to send a message, or there could be some implicit flow like user automatically signs).

Currently in frontend, the sender is randomly generated. When the tx reaches sequencer, it's unsigned, then sequencer signs it with sequencer private key. Is this intentional or the standard flow of rollup app? I thought in order to make it more like a blockchain app, user (message sender) needs to sign as well, right?

If this messenger rollup is built with cosmos sdk, it would support user sign it, right?

@llllllluc llllllluc changed the title How to support users actually sign the message How to support user actually signs the message Apr 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant