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

[FEATURE] Receive a user's address when wallet is asked to sign arbitrary message #1788

Open
cybercent opened this issue Oct 10, 2023 · 1 comment
Labels

Comments

@cybercent
Copy link
Contributor

Issue to be solved

I'm looking for a way to determine the wallet address that is expected to sign the message.

Suggest A Solution

In the demo below, an ADDRESS param would be expected along with MSG.

import * as fcl from "@onflow/fcl"

const signMessage = async () => {
  const MSG = Buffer.from("FOO").toString("hex")
  try {
    return await fcl.currentUser.signUserMessage(MSG)
  } catch (error) {
    console.log(error)
  }
}

What are you currently working on that this is blocking?

In the context of a multi account wallet, I'm looking for a way to know what account does the app expect the user to sign a message with.

@cybercent cybercent changed the title [FEATURE] Receive a user's address when wallet is asked to sign a arbitrary message [FEATURE] Receive a user's address when wallet is asked to sign arbitrary message Oct 10, 2023
@cybercent
Copy link
Contributor Author

Apparently the wallet address is already sent when requesting the signature of a TX but not sent when requesting the signature of an arbitrary messages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant