SignAllTransactions
Last updated
Was this helpful?
Last updated
Was this helpful?
Once an app is connected, it is also possible to sign multiple transactions at once. Unlike , Phantom will not submit these transactions to the network. Applications can submit signed transactions using .
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 Phantom should redirect the user upon completion. Please review for more details. URL-encoded.
payload (required): An encrypted JSON string with the following fields:
transactions (required): An array of that Phantom will sign, serialized and encoded in base58.
session (required): The session token received from the method. Please see for more details.
nonce: A nonce used for encrypting the response, encoded in base58.
data: An encrypted JSON string. Refer to to learn how apps can decrypt data using a shared secret. Encrypted bytes are encoded in base58.
transactions: An array of signed, serialized transactions that are base58 encoded. Phantom will not submit these transactions. Applications can submit these transactions themselves via .
An errorCode and errorMessage as query parameters. Please refer to for a full list of possible error codes.
Please refer to the .