SignAllTransactions

Once an app is connected, it is also possible to sign multiple transactions at once. Unlike SignAndSendTransaction, Solflare will not submit these transactions to the network.

Applications can submit signed transactions using web3.js's sendRawTransaction.

Base URL

https://solflare.com/ul/v1/signAllTransactions

Query String Parameters

• dapp_encryption_public_key (required): The original encryption public key used from the app side for an existing Connect 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 Specifying Redirects for more details. URL-encoded.

• payload (required): An encrypted JSON string with the following fields:

  {
    "transactions": [
      "...", // serialized transaction, bs58-encoded
      "...", // serialized transaction, bs58-encoded
    ],
    "session": "...", // token received from connect-method
  }

  • transactions (required): A serialized array of transactions, encoded in base58, that Solflare will sign.

  • session (required): The session token received from the Connect method. Please see Handling Sessions for more details.

Returns

Approve

• nonce: A nonce used for encrypting the response, encoded in base58.

• data: An encrypted JSON string. Refer to Encryption to learn how apps can decrypt data using a shared secret. Encrypted bytes are encoded in base58.

  // content of decrypted `data`-parameter
  {
      transactions: [
          "...", // signed serialized transaction, bs58-encoded
          "...", // signed serialized transaction, bs58-encoded
      ] 
  }

  • transactions: An array of signed, serialized transactions that are base58 encoded. Solflare will not submit these transactions. Applications can submit these transactions themselves via web3.js's sendRawTransaction.

Reject

An errorCode and errorMessage as query parameters.

Please refer to Errors for a full list of possible error codes.

{
  "errorCode": "...",
  "errorMessage": "..."
}

Example

Please refer to the signAllTransactions method implemented in our demo application.