Sending a Legacy Transaction
Last updated
Was this helpful?
Last updated
Was this helpful?
Once a web application is connected to Phantom, it can prompt the user for permission to send transactions on their behalf.
In order to send a transaction, a web application must:
Create an unsigned transaction.
Have the transaction be signed and submitted to the network by the user's Phantom wallet.
Optionally await network confirmation using a Solana JSON RPC connection.
For a sample Phantom transaction, check out our .
Once a transaction is created, the web application may ask the user's Phantom wallet to sign and send the transaction. If accepted, Phantom will sign the transaction with the user's private key and submit it via a Solana JSON RPC connection. By far the easiest and most recommended way of doing this is by using the signAndSendTransaction
method on the provider, but it is also possible to do with request
. In both cases, the call will return a for an object containing the signature
.
You can also specify a SendOptions
as a second argument into signAndSendTransaction
or as an options
parameter when using request
.
For a live demo of signAndSendTransaction
, please refer to the .
The following methods are also supported, but are not recommended over signAndSendTransaction
. It is safer for users, and a simpler API for developers, for Phantom to submit the transaction immediately after signing it instead of relying on the application to do so.
If you use the methods below, Phantom may display a warning message to users at the time of signing.
For legacy integrations, Phantom supports signing multiple transactions at once without sending them. This is exposed through the signAllTransactions
method on the provider. This method is not recommended for new integrations. Instead, developers should make use of signAndSendAllTransactions
.
It is also possible to sign and send multiple transactions at once. This is exposed through the signAndSendAllTransactions
method on the provider. This method accepts an array of Solana transactions, and will optionally accept a object as a second parameter. If successful, it will return a for an object containing the array of string signatures
and the publicKey
of the signer.
Once a transaction is created, a web application may ask the user's Phantom wallet to sign the transaction without also submitting it to the network. The easiest and most recommended way of doing this is via the signTransaction
method on the provider, but it is also possible to do via request
. In both cases, the call will return a for the signed transaction. After the transaction has been signed, an application may submit the transaction itself via .
Please refer to the for an example of signTransaction
.
For an example of signAllTransactions
, please refer to the .