rosetta-sdk-typescript

/** * Rosetta * Build Once. Integrate Your Blockchain Everywhere. * * The version of the OpenAPI document: 1.4.10 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). * https://openapi-generator.tech * Do not edit the class manually. */ import { ConstructionCombineRequest, ConstructionCombineResponse, ConstructionDeriveRequest, ConstructionDeriveResponse, ConstructionHashRequest, ConstructionMetadataRequest, ConstructionMetadataResponse, ConstructionParseRequest, ConstructionParseResponse, ConstructionPayloadsRequest, ConstructionPayloadsResponse, ConstructionPreprocessRequest, ConstructionPreprocessResponse, ConstructionSubmitRequest, TransactionIdentifierResponse } from '../models'; import * as runtime from '../runtime'; export interface ConstructionCombineOperationRequest { constructionCombineRequest: ConstructionCombineRequest; } export interface ConstructionDeriveOperationRequest { constructionDeriveRequest: ConstructionDeriveRequest; } export interface ConstructionHashOperationRequest { constructionHashRequest: ConstructionHashRequest; } export interface ConstructionMetadataOperationRequest { constructionMetadataRequest: ConstructionMetadataRequest; } export interface ConstructionParseOperationRequest { constructionParseRequest: ConstructionParseRequest; } export interface ConstructionPayloadsOperationRequest { constructionPayloadsRequest: ConstructionPayloadsRequest; } export interface ConstructionPreprocessOperationRequest { constructionPreprocessRequest: ConstructionPreprocessRequest; } export interface ConstructionSubmitOperationRequest { constructionSubmitRequest: ConstructionSubmitRequest; } /** * ConstructionApi - controller interface for the server side implementation. * * @export * @interface ConstructionApiController */ export declare class ConstructionApiController<Req extends { body: any; } = { body: any; }> { private readonly service; /** * * @param service - The service that implements */ constructor(service: ConstructionApiService); /** * Combine creates a network-specific transaction from an unsigned transaction and an array of provided signatures. The signed transaction returned from this method will be sent to the `/construction/submit` endpoint by the caller. * Create Network Transaction from Signatures * * @param req - The request object, where the body is a ConstructionCombineRequest */ constructionCombine(req: Req): Promise<any>; /** * Derive returns the AccountIdentifier associated with a public key. Blockchains that require an on-chain action to create an account should not implement this method. * Derive an AccountIdentifier from a PublicKey * * @param req - The request object, where the body is a ConstructionDeriveRequest */ constructionDerive(req: Req): Promise<any>; /** * TransactionHash returns the network-specific transaction hash for a signed transaction. * Get the Hash of a Signed Transaction * * @param req - The request object, where the body is a ConstructionHashRequest */ constructionHash(req: Req): Promise<any>; /** * Get any information required to construct a transaction for a specific network. Metadata returned here could be a recent hash to use, an account sequence number, or even arbitrary chain state. The request used when calling this endpoint is created by calling `/construction/preprocess` in an offline environment. You should NEVER assume that the request sent to this endpoint will be created by the caller or populated with any custom parameters. This must occur in `/construction/preprocess`. It is important to clarify that this endpoint should not pre-construct any transactions for the client (this should happen in `/construction/payloads`). This endpoint is left purposely unstructured because of the wide scope of metadata that could be required. * Get Metadata for Transaction Construction * * @param req - The request object, where the body is a ConstructionMetadataRequest */ constructionMetadata(req: Req): Promise<any>; /** * Parse is called on both unsigned and signed transactions to understand the intent of the formulated transaction. This is run as a sanity check before signing (after `/construction/payloads`) and before broadcast (after `/construction/combine`). * Parse a Transaction * * @param req - The request object, where the body is a ConstructionParseRequest */ constructionParse(req: Req): Promise<any>; /** * 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. * Generate an Unsigned Transaction and Signing Payloads * * @param req - The request object, where the body is a ConstructionPayloadsRequest */ constructionPayloads(req: Req): Promise<any>; /** * Preprocess is called prior to `/construction/payloads` to construct a request for any metadata that is needed for transaction construction given (i.e. account nonce). The `options` object returned from this endpoint will be sent to the `/construction/metadata` endpoint UNMODIFIED by the caller (in an offline execution environment). If your Construction API implementation has configuration options, they MUST be specified in the `/construction/preprocess` request (in the `metadata` field). * Create a Request to Fetch Metadata * * @param req - The request object, where the body is a ConstructionPreprocessRequest */ constructionPreprocess(req: Req): Promise<any>; /** * Submit a pre-signed transaction to the node. This call should not block on the transaction being included in a block. Rather, it should return immediately with an indication of whether or not the transaction was included in the mempool. The transaction submission response should only return a 200 status if the submitted transaction could be included in the mempool. Otherwise, it should return an error. * Submit a Signed Transaction * * @param req - The request object, where the body is a ConstructionSubmitRequest */ constructionSubmit(req: Req): Promise<any>; } /** * ConstructionApi - service interface for the server side implementation. * * * @export * @interface ConstructionApiService */ export interface ConstructionApiService { /** * Combine creates a network-specific transaction from an unsigned transaction and an array of provided signatures. The signed transaction returned from this method will be sent to the `/construction/submit` endpoint by the caller. * Create Network Transaction from Signatures * * requestParameters - the body of the RPC style request. */ constructionCombine(requestParameters: ConstructionCombineRequest): Promise<ConstructionCombineResponse>; /** * Derive returns the AccountIdentifier associated with a public key. Blockchains that require an on-chain action to create an account should not implement this method. * Derive an AccountIdentifier from a PublicKey * * requestParameters - the body of the RPC style request. */ constructionDerive(requestParameters: ConstructionDeriveRequest): Promise<ConstructionDeriveResponse>; /** * TransactionHash returns the network-specific transaction hash for a signed transaction. * Get the Hash of a Signed Transaction * * requestParameters - the body of the RPC style request. */ constructionHash(requestParameters: ConstructionHashRequest): Promise<TransactionIdentifierResponse>; /** * Get any information required to construct a transaction for a specific network. Metadata returned here could be a recent hash to use, an account sequence number, or even arbitrary chain state. The request used when calling this endpoint is created by calling `/construction/preprocess` in an offline environment. You should NEVER assume that the request sent to this endpoint will be created by the caller or populated with any custom parameters. This must occur in `/construction/preprocess`. It is important to clarify that this endpoint should not pre-construct any transactions for the client (this should happen in `/construction/payloads`). This endpoint is left purposely unstructured because of the wide scope of metadata that could be required. * Get Metadata for Transaction Construction * * requestParameters - the body of the RPC style request. */ constructionMetadata(requestParameters: ConstructionMetadataRequest): Promise<ConstructionMetadataResponse>; /** * Parse is called on both unsigned and signed transactions to understand the intent of the formulated transaction. This is run as a sanity check before signing (after `/construction/payloads`) and before broadcast (after `/construction/combine`). * Parse a Transaction * * requestParameters - the body of the RPC style request. */ constructionParse(requestParameters: ConstructionParseRequest): Promise<ConstructionParseResponse>; /** * 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. * Generate an Unsigned Transaction and Signing Payloads * * requestParameters - the body of the RPC style request. */ constructionPayloads(requestParameters: ConstructionPayloadsRequest): Promise<ConstructionPayloadsResponse>; /** * Preprocess is called prior to `/construction/payloads` to construct a request for any metadata that is needed for transaction construction given (i.e. account nonce). The `options` object returned from this endpoint will be sent to the `/construction/metadata` endpoint UNMODIFIED by the caller (in an offline execution environment). If your Construction API implementation has configuration options, they MUST be specified in the `/construction/preprocess` request (in the `metadata` field). * Create a Request to Fetch Metadata * * requestParameters - the body of the RPC style request. */ constructionPreprocess(requestParameters: ConstructionPreprocessRequest): Promise<ConstructionPreprocessResponse>; /** * Submit a pre-signed transaction to the node. This call should not block on the transaction being included in a block. Rather, it should return immediately with an indication of whether or not the transaction was included in the mempool. The transaction submission response should only return a 200 status if the submitted transaction could be included in the mempool. Otherwise, it should return an error. * Submit a Signed Transaction * * requestParameters - the body of the RPC style request. */ constructionSubmit(requestParameters: ConstructionSubmitRequest): Promise<TransactionIdentifierResponse>; } /** * ConstructionApi - interface * * @export * @interface ConstructionApiInterface */ export interface ConstructionApiInterface { /** * Combine creates a network-specific transaction from an unsigned transaction and an array of provided signatures. The signed transaction returned from this method will be sent to the `/construction/submit` endpoint by the caller. * @summary Create Network Transaction from Signatures * @param {ConstructionCombineRequest} constructionCombineRequest * @param {*} [options] Override http request option. * @throws {RequiredError} * @memberof ConstructionApiInterface */ constructionCombineRaw(requestParameters: ConstructionCombineOperationRequest, initOverrides?: RequestInit): Promise<runtime.ApiResponse<ConstructionCombineResponse>>; /** * Combine creates a network-specific transaction from an unsigned transaction and an array of provided signatures. The signed transaction returned from this method will be sent to the `/construction/submit` endpoint by the caller. * Create Network Transaction from Signatures */ constructionCombine(requestParameters: ConstructionCombineOperationRequest, initOverrides?: RequestInit): Promise<ConstructionCombineResponse>; /** * Derive returns the AccountIdentifier associated with a public key. Blockchains that require an on-chain action to create an account should not implement this method. * @summary Derive an AccountIdentifier from a PublicKey * @param {ConstructionDeriveRequest} constructionDeriveRequest * @param {*} [options] Override http request option. * @throws {RequiredError} * @memberof ConstructionApiInterface */ constructionDeriveRaw(requestParameters: ConstructionDeriveOperationRequest, initOverrides?: RequestInit): Promise<runtime.ApiResponse<ConstructionDeriveResponse>>; /** * Derive returns the AccountIdentifier associated with a public key. Blockchains that require an on-chain action to create an account should not implement this method. * Derive an AccountIdentifier from a PublicKey */ constructionDerive(requestParameters: ConstructionDeriveOperationRequest, initOverrides?: RequestInit): Promise<ConstructionDeriveResponse>; /** * TransactionHash returns the network-specific transaction hash for a signed transaction. * @summary Get the Hash of a Signed Transaction * @param {ConstructionHashRequest} constructionHashRequest * @param {*} [options] Override http request option. * @throws {RequiredError} * @memberof ConstructionApiInterface */ constructionHashRaw(requestParameters: ConstructionHashOperationRequest, initOverrides?: RequestInit): Promise<runtime.ApiResponse<TransactionIdentifierResponse>>; /** * TransactionHash returns the network-specific transaction hash for a signed transaction. * Get the Hash of a Signed Transaction */ constructionHash(requestParameters: ConstructionHashOperationRequest, initOverrides?: RequestInit): Promise<TransactionIdentifierResponse>; /** * Get any information required to construct a transaction for a specific network. Metadata returned here could be a recent hash to use, an account sequence number, or even arbitrary chain state. The request used when calling this endpoint is created by calling `/construction/preprocess` in an offline environment. You should NEVER assume that the request sent to this endpoint will be created by the caller or populated with any custom parameters. This must occur in `/construction/preprocess`. It is important to clarify that this endpoint should not pre-construct any transactions for the client (this should happen in `/construction/payloads`). This endpoint is left purposely unstructured because of the wide scope of metadata that could be required. * @summary Get Metadata for Transaction Construction * @param {ConstructionMetadataRequest} constructionMetadataRequest * @param {*} [options] Override http request option. * @throws {RequiredError} * @memberof ConstructionApiInterface */ constructionMetadataRaw(requestParameters: ConstructionMetadataOperationRequest, initOverrides?: RequestInit): Promise<runtime.ApiResponse<ConstructionMetadataResponse>>; /** * Get any information required to construct a transaction for a specific network. Metadata returned here could be a recent hash to use, an account sequence number, or even arbitrary chain state. The request used when calling this endpoint is created by calling `/construction/preprocess` in an offline environment. You should NEVER assume that the request sent to this endpoint will be created by the caller or populated with any custom parameters. This must occur in `/construction/preprocess`. It is important to clarify that this endpoint should not pre-construct any transactions for the client (this should happen in `/construction/payloads`). This endpoint is left purposely unstructured because of the wide scope of metadata that could be required. * Get Metadata for Transaction Construction */ constructionMetadata(requestParameters: ConstructionMetadataOperationRequest, initOverrides?: RequestInit): Promise<ConstructionMetadataResponse>; /** * Parse is called on both unsigned and signed transactions to understand the intent of the formulated transaction. This is run as a sanity check before signing (after `/construction/payloads`) and before broadcast (after `/construction/combine`). * @summary Parse a Transaction * @param {ConstructionParseRequest} constructionParseRequest * @param {*} [options] Override http request option. * @throws {RequiredError} * @memberof ConstructionApiInterface */ constructionParseRaw(requestParameters: ConstructionParseOperationRequest, initOverrides?: RequestInit): Promise<runtime.ApiResponse<ConstructionParseResponse>>; /** * Parse is called on both unsigned and signed transactions to understand the intent of the formulated transaction. This is run as a sanity check before signing (after `/construction/payloads`) and before broadcast (after `/construction/combine`). * Parse a Transaction */ constructionParse(requestParameters: ConstructionParseOperationRequest, initOverrides?: RequestInit): Promise<ConstructionParseResponse>; /** * 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. * @summary Generate an Unsigned Transaction and Signing Payloads * @param {ConstructionPayloadsRequest} constructionPayloadsRequest * @param {*} [options] Override http request option. * @throws {RequiredError} * @memberof ConstructionApiInterface */ constructionPayloadsRaw(requestParameters: ConstructionPayloadsOperationRequest, initOverrides?: RequestInit): Promise<runtime.ApiResponse<ConstructionPayloadsResponse>>; /** * 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. * Generate an Unsigned Transaction and Signing Payloads */ constructionPayloads(requestParameters: ConstructionPayloadsOperationRequest, initOverrides?: RequestInit): Promise<ConstructionPayloadsResponse>; /** * Preprocess is called prior to `/construction/payloads` to construct a request for any metadata that is needed for transaction construction given (i.e. account nonce). The `options` object returned from this endpoint will be sent to the `/construction/metadata` endpoint UNMODIFIED by the caller (in an offline execution environment). If your Construction API implementation has configuration options, they MUST be specified in the `/construction/preprocess` request (in the `metadata` field). * @summary Create a Request to Fetch Metadata * @param {ConstructionPreprocessRequest} constructionPreprocessRequest * @param {*} [options] Override http request option. * @throws {RequiredError} * @memberof ConstructionApiInterface */ constructionPreprocessRaw(requestParameters: ConstructionPreprocessOperationRequest, initOverrides?: RequestInit): Promise<runtime.ApiResponse<ConstructionPreprocessResponse>>; /** * Preprocess is called prior to `/construction/payloads` to construct a request for any metadata that is needed for transaction construction given (i.e. account nonce). The `options` object returned from this endpoint will be sent to the `/construction/metadata` endpoint UNMODIFIED by the caller (in an offline execution environment). If your Construction API implementation has configuration options, they MUST be specified in the `/construction/preprocess` request (in the `metadata` field). * Create a Request to Fetch Metadata */ constructionPreprocess(requestParameters: ConstructionPreprocessOperationRequest, initOverrides?: RequestInit): Promise<ConstructionPreprocessResponse>; /** * Submit a pre-signed transaction to the node. This call should not block on the transaction being included in a block. Rather, it should return immediately with an indication of whether or not the transaction was included in the mempool. The transaction submission response should only return a 200 status if the submitted transaction could be included in the mempool. Otherwise, it should return an error. * @summary Submit a Signed Transaction * @param {ConstructionSubmitRequest} constructionSubmitRequest * @param {*} [options] Override http request option. * @throws {RequiredError} * @memberof ConstructionApiInterface */ constructionSubmitRaw(requestParameters: ConstructionSubmitOperationRequest, initOverrides?: RequestInit): Promise<runtime.ApiResponse<TransactionIdentifierResponse>>; /** * Submit a pre-signed transaction to the node. This call should not block on the transaction being included in a block. Rather, it should return immediately with an indication of whether or not the transaction was included in the mempool. The transaction submission response should only return a 200 status if the submitted transaction could be included in the mempool. Otherwise, it should return an error. * Submit a Signed Transaction */ constructionSubmit(requestParameters: ConstructionSubmitOperationRequest, initOverrides?: RequestInit): Promise<TransactionIdentifierResponse>; } /** * */ export declare class ConstructionApi extends runtime.BaseAPI implements ConstructionApiInterface { /** * Combine creates a network-specific transaction from an unsigned transaction and an array of provided signatures. The signed transaction returned from this method will be sent to the `/construction/submit` endpoint by the caller. * Create Network Transaction from Signatures */ constructionCombineRaw(requestParameters: ConstructionCombineOperationRequest, initOverrides?: RequestInit): Promise<runtime.ApiResponse<ConstructionCombineResponse>>; /** * Combine creates a network-specific transaction from an unsigned transaction and an array of provided signatures. The signed transaction returned from this method will be sent to the `/construction/submit` endpoint by the caller. * Create Network Transaction from Signatures */ constructionCombine(requestParameters: ConstructionCombineOperationRequest, initOverrides?: RequestInit): Promise<ConstructionCombineResponse>; /** * Derive returns the AccountIdentifier associated with a public key. Blockchains that require an on-chain action to create an account should not implement this method. * Derive an AccountIdentifier from a PublicKey */ constructionDeriveRaw(requestParameters: ConstructionDeriveOperationRequest, initOverrides?: RequestInit): Promise<runtime.ApiResponse<ConstructionDeriveResponse>>; /** * Derive returns the AccountIdentifier associated with a public key. Blockchains that require an on-chain action to create an account should not implement this method. * Derive an AccountIdentifier from a PublicKey */ constructionDerive(requestParameters: ConstructionDeriveOperationRequest, initOverrides?: RequestInit): Promise<ConstructionDeriveResponse>; /** * TransactionHash returns the network-specific transaction hash for a signed transaction. * Get the Hash of a Signed Transaction */ constructionHashRaw(requestParameters: ConstructionHashOperationRequest, initOverrides?: RequestInit): Promise<runtime.ApiResponse<TransactionIdentifierResponse>>; /** * TransactionHash returns the network-specific transaction hash for a signed transaction. * Get the Hash of a Signed Transaction */ constructionHash(requestParameters: ConstructionHashOperationRequest, initOverrides?: RequestInit): Promise<TransactionIdentifierResponse>; /** * Get any information required to construct a transaction for a specific network. Metadata returned here could be a recent hash to use, an account sequence number, or even arbitrary chain state. The request used when calling this endpoint is created by calling `/construction/preprocess` in an offline environment. You should NEVER assume that the request sent to this endpoint will be created by the caller or populated with any custom parameters. This must occur in `/construction/preprocess`. It is important to clarify that this endpoint should not pre-construct any transactions for the client (this should happen in `/construction/payloads`). This endpoint is left purposely unstructured because of the wide scope of metadata that could be required. * Get Metadata for Transaction Construction */ constructionMetadataRaw(requestParameters: ConstructionMetadataOperationRequest, initOverrides?: RequestInit): Promise<runtime.ApiResponse<ConstructionMetadataResponse>>; /** * Get any information required to construct a transaction for a specific network. Metadata returned here could be a recent hash to use, an account sequence number, or even arbitrary chain state. The request used when calling this endpoint is created by calling `/construction/preprocess` in an offline environment. You should NEVER assume that the request sent to this endpoint will be created by the caller or populated with any custom parameters. This must occur in `/construction/preprocess`. It is important to clarify that this endpoint should not pre-construct any transactions for the client (this should happen in `/construction/payloads`). This endpoint is left purposely unstructured because of the wide scope of metadata that could be required. * Get Metadata for Transaction Construction */ constructionMetadata(requestParameters: ConstructionMetadataOperationRequest, initOverrides?: RequestInit): Promise<ConstructionMetadataResponse>; /** * Parse is called on both unsigned and signed transactions to understand the intent of the formulated transaction. This is run as a sanity check before signing (after `/construction/payloads`) and before broadcast (after `/construction/combine`). * Parse a Transaction */ constructionParseRaw(requestParameters: ConstructionParseOperationRequest, initOverrides?: RequestInit): Promise<runtime.ApiResponse<ConstructionParseResponse>>; /** * Parse is called on both unsigned and signed transactions to understand the intent of the formulated transaction. This is run as a sanity check before signing (after `/construction/payloads`) and before broadcast (after `/construction/combine`). * Parse a Transaction */ constructionParse(requestParameters: ConstructionParseOperationRequest, initOverrides?: RequestInit): Promise<ConstructionParseResponse>; /** * 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. * Generate an Unsigned Transaction and Signing Payloads */ constructionPayloadsRaw(requestParameters: ConstructionPayloadsOperationRequest, initOverrides?: RequestInit): Promise<runtime.ApiResponse<ConstructionPayloadsResponse>>; /** * 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. * Generate an Unsigned Transaction and Signing Payloads */ constructionPayloads(requestParameters: ConstructionPayloadsOperationRequest, initOverrides?: RequestInit): Promise<ConstructionPayloadsResponse>; /** * Preprocess is called prior to `/construction/payloads` to construct a request for any metadata that is needed for transaction construction given (i.e. account nonce). The `options` object returned from this endpoint will be sent to the `/construction/metadata` endpoint UNMODIFIED by the caller (in an offline execution environment). If your Construction API implementation has configuration options, they MUST be specified in the `/construction/preprocess` request (in the `metadata` field). * Create a Request to Fetch Metadata */ constructionPreprocessRaw(requestParameters: ConstructionPreprocessOperationRequest, initOverrides?: RequestInit): Promise<runtime.ApiResponse<ConstructionPreprocessResponse>>; /** * Preprocess is called prior to `/construction/payloads` to construct a request for any metadata that is needed for transaction construction given (i.e. account nonce). The `options` object returned from this endpoint will be sent to the `/construction/metadata` endpoint UNMODIFIED by the caller (in an offline execution environment). If your Construction API implementation has configuration options, they MUST be specified in the `/construction/preprocess` request (in the `metadata` field). * Create a Request to Fetch Metadata */ constructionPreprocess(requestParameters: ConstructionPreprocessOperationRequest, initOverrides?: RequestInit): Promise<ConstructionPreprocessResponse>; /** * Submit a pre-signed transaction to the node. This call should not block on the transaction being included in a block. Rather, it should return immediately with an indication of whether or not the transaction was included in the mempool. The transaction submission response should only return a 200 status if the submitted transaction could be included in the mempool. Otherwise, it should return an error. * Submit a Signed Transaction */ constructionSubmitRaw(requestParameters: ConstructionSubmitOperationRequest, initOverrides?: RequestInit): Promise<runtime.ApiResponse<TransactionIdentifierResponse>>; /** * Submit a pre-signed transaction to the node. This call should not block on the transaction being included in a block. Rather, it should return immediately with an indication of whether or not the transaction was included in the mempool. The transaction submission response should only return a 200 status if the submitted transaction could be included in the mempool. Otherwise, it should return an error. * Submit a Signed Transaction */ constructionSubmit(requestParameters: ConstructionSubmitOperationRequest, initOverrides?: RequestInit): Promise<TransactionIdentifierResponse>; }