Generate an Unsigned Transaction and Signing Payloads
Payloads is called with an array of operations and the response from /construction/metadata
. It returns an unsigned transaction blob and a collection of payloads that must be signed by particular AccountIdentifiers using a certain SignatureType. The array of operations provided in transaction construction often times can not specify all “effects” of a transaction (consider invoked transactions in Ethereum). However, they can deterministically specify the “intent” of the transaction, which is sufficient for construction. For this reason, parsing the corresponding transaction in the Data API (when it lands on chain) will contain a superset of whatever operations were provided during construction.
Body
ConstructionPayloadsRequest is the request to /construction/payloads
. It contains the network, a slice of operations, and arbitrary metadata that was returned by the call to /construction/metadata
. Optionally, the request can also include an array of PublicKeys associated with the AccountIdentifiers returned in ConstructionPreprocessResponse.
Response
Expected response to a valid request
ConstructionTransactionResponse is returned by /construction/payloads
. It contains an unsigned transaction blob (that is usually needed to construct the a network transaction from a collection of signatures) and an array of payloads that must be signed by the caller.