Optionalopts: TransactionBlockhashCtorOptionalopts: TransactionNonceCtorOptionalopts: TransactionCtorFields_DEPRECATEDOptionalfeeThe transaction fee payer
The instructions to atomically execute
Optionallastthe last block chain can advance to before tx is declared expired
OptionalminIf this is a nonce transaction this represents the minimum slot from which to evaluate if the nonce has advanced when attempting to confirm the transaction. This protects against a case where the transaction confirmation logic loads the nonce account from an old slot and assumes the mismatch in nonce value implies that the nonce has been advanced.
OptionalnonceOptional Nonce information. If populated, transaction will use a durable Nonce hash instead of a recentBlockhash. Must be populated by the caller
OptionalrecentA recent transaction id. Must be populated by the caller
Signatures for the transaction. Typically created by invoking the
sign() method
The first (payer) Transaction signature
Buffer of payer's signature
Add one or more instructions to this Transaction
Instructions to add to the Transaction
Add an externally created signature to a transaction. The public key must correspond to either the fee payer or a signer account in the transaction instructions.
Public key that will be added to the transaction.
An externally created signature to add to the transaction.
Compile transaction data
Get the estimated fee associated with a transaction
Connection to RPC Endpoint.
The estimated fee for the transaction
Partially sign a transaction with the specified accounts. All accounts must correspond to either the fee payer or a signer account in the transaction instructions.
All the caveats from the sign method apply to partialSign
Array of signers that will sign the transaction
Serialize the Transaction in the wire format.
Optionalconfig: SerializeConfig
Config of transaction.
Signature of transaction in wire format.
Get a buffer of the Transaction data that need to be covered by signatures
Specify the public keys which will be used to sign the Transaction. The first signer will be used as the transaction fee payer account.
Signatures can be added with either partialSign or addSignature
Sign the Transaction with the specified signers. Multiple signatures may be applied to a Transaction. The first signature is considered "primary" and is used identify and confirm transactions.
If the Transaction feePayer is not set, the first signer will be used
as the transaction fee payer account.
Transaction fields should not be modified after the first call to sign,
as doing so may invalidate the signature and cause the Transaction to be
rejected.
The Transaction must be assigned a valid recentBlockhash before invoking this method
Array of signers that will sign the transaction
Verify signatures of a Transaction Optional parameter specifies if we're expecting a fully signed Transaction or a partially signed one. If no boolean is provided, we expect a fully signed Transaction by default.
OptionalrequireAllSignatures: boolean = true
Require a fully signed Transaction
StaticfromParse a wire transaction into a Transaction object.
Signature of wire Transaction
Transaction associated with the signature
StaticpopulatePopulate Transaction object from message and signatures
Message of transaction
List of signatures to assign to the transaction
The populated Transaction
Transaction class