SignMessage
Last updated
Was this helpful?
Last updated
Was this helpful?
After connecting to Solflare, an app can request that the user sign a message. Applications can create their own messages, which will be displayed to users from Solflare's signature prompt. Message signatures do not incur network fees and are a convenient way for apps to verify address ownership.
In order to send a message for the user to sign, an application must:
Provide a hex or UTF-8 encoded string as a Uint8Array and then base58-encoded it.
Request that the encoded message is signed via the user's Solflare wallet.
dapp_encryption_public_key
(required): The original encryption public key used from the app side for an existing session.
nonce
(required): A nonce used for encrypting the request, encoded in base58.
redirect_link
(required): The URI where Solflare should redirect the user upon completion. Please review for more details. URL-encoded.
payload
(required): An encrypted JSON string with the following fields:
message
(required): The message that should be signed by the user, encoded in base58. Solflare will display this message to the user when they are prompted to sign.
session
(required): The session token received from the method. Please see Handling Sessions for more details.
display
(optional): How you want us to display the string to the user. Defaults to utf8
nonce
: A nonce used for encrypting the response, encoded in base58.
An errorCode
and errorMessage
as query parameters.
data
: An encrypted JSON string. Refer to to learn how apps can decrypt data
using a shared secret. Encrypted bytes are encoded in base58.
signature
: The message signature, encoded in base58. For more information on how to verify the signature of a message, please refer to .
Please refer to for a full list of possible error codes.
Please refer to the method implemented in our demo application.