AptosRequestSubmitTransaction class

This endpoint accepts transaction submissions in two formats.To submit a transaction as JSON, you must submit a SubmitTransactionRequest. To build this request, do the following:

  1. Encode the transaction as BCS. If you are using a language that hasnative BCS support, make sure of that library. If not, you may takeadvantage of /transactions/encode_submission. When using thisendpoint, make sure you trust the node you're talking to, as it ispossible they could manipulate your request.2. Sign the encoded transaction and use it to create a TransactionSignature.
  2. Submit the request. Make sure to use the "application/json" Content-Type.To submit a transaction as BCS, you must submit a SignedTransactionencoded as BCS. See SignedTransaction in types/src/transaction/mod.rs.Make sure to use the application/x.aptos.signed_transaction+bcs Content-Type. aptos documation
Inheritance

Constructors

AptosRequestSubmitTransaction.new({required List<int> signedTransactionData})

Properties

body → List<int>
no setteroverride
hashCode → int
The hash code for this object.
no setterinherited
headers → Map<String, String>?
no setteroverride
method → String
no setteroverride
pathParameters → List<String>
no setterinherited
queryParameters → Map<String, String?>
no setterinherited
requestType → RequestServiceType
no setterinherited
runtimeType → Type
A representation of the runtime type of the object.
no setterinherited
signedTransactionData → List<int>
final

Methods

buildRequest(int requestID) → AptosRequestDetails
inherited
noSuchMethod(Invocation invocation) → dynamic
Invoked when a nonexistent method or property is accessed.
inherited
onResonse(Map<String, dynamic> result) → AptosApiPendingTransaction
override
toString() → String
A string representation of this object.
inherited

Operators

operator ==(Object other) → bool
The equality operator.
inherited