/**
 * Radix Gateway API - Babylon
 * This API is exposed by the Babylon Radix Gateway to enable clients to efficiently query current and historic state on the RadixDLT ledger, and intelligently handle transaction submission.  It is designed for use by wallets and explorers, and for light queries from front-end dApps. For exchange/asset integrations, back-end dApp integrations, or simple use cases, you should consider using the Core API on a Node. A Gateway is only needed for reading historic snapshots of ledger states or a more robust set-up.  The Gateway API is implemented by the [Network Gateway](https://github.com/radixdlt/babylon-gateway), which is configured to read from [full node(s)](https://github.com/radixdlt/babylon-node) to extract and index data from the network.  This document is an API reference documentation, visit [User Guide](https://docs.radixdlt.com/) to learn more about how to run a Gateway of your own.  ## Migration guide  Please see [the latest release notes](https://github.com/radixdlt/babylon-gateway/releases).  ## Integration and forward compatibility guarantees  All responses may have additional fields added at any release, so clients are advised to use JSON parsers which ignore unknown fields on JSON objects.  When the Radix protocol is updated, new functionality may be added, and so discriminated unions returned by the API may need to be updated to have new variants added, corresponding to the updated data. Clients may need to update in advance to be able to handle these new variants when a protocol update comes out.  On the very rare occasions we need to make breaking changes to the API, these will be warned in advance with deprecation notices on previous versions. These deprecation notices will include a safe migration path. Deprecation notes or breaking changes will be flagged clearly in release notes for new versions of the Gateway.  The Gateway DB schema is not subject to any compatibility guarantees, and may be changed at any release. DB changes will be flagged in the release notes so clients doing custom DB integrations can prepare.
 *
 * The version of the OpenAPI document: v1.10.1
 *
 *
 * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
 * https://openapi-generator.tech
 * Do not edit the class manually.
 */
import type { TransactionIntentStatus } from './TransactionIntentStatus';
import type { TransactionStatus } from './TransactionStatus';
import type { TransactionStatusResponseKnownPayloadItem } from './TransactionStatusResponseKnownPayloadItem';
/**
 *
 * @export
 * @interface TransactionStatusResponseAllOf
 */
export interface TransactionStatusResponseAllOf {
    /**
     *
     * @type {TransactionStatus}
     * @memberof TransactionStatusResponseAllOf
     */
    status: TransactionStatus;
    /**
     *
     * @type {TransactionIntentStatus}
     * @memberof TransactionStatusResponseAllOf
     */
    intent_status: TransactionIntentStatus;
    /**
     * An additional description to clarify the intent status.

     * @type {string}
     * @memberof TransactionStatusResponseAllOf
     */
    intent_status_description: string;
    /**
     *
     * @type {Array<TransactionStatusResponseKnownPayloadItem>}
     * @memberof TransactionStatusResponseAllOf
     */
    known_payloads: Array<TransactionStatusResponseKnownPayloadItem>;
    /**
     * If the intent was committed, this gives the state version when this intent was committed.

     * @type {number}
     * @memberof TransactionStatusResponseAllOf
     */
    committed_state_version?: number | null;
    /**
     * The epoch number at which the transaction is guaranteed to get permanently rejected by the Network due to exceeded epoch range defined when submitting transaction.
     * @type {number}
     * @memberof TransactionStatusResponseAllOf
     */
    permanently_rejects_at_epoch?: number | null;
    /**
     * The most relevant error message received, due to a rejection or commit as failure.
Please note that presence of an error message doesn't imply that the intent
will definitely reject or fail. This could represent a temporary error (such as out
of fees), or an error with a payload which doesn't end up being committed.

     * @type {string}
     * @memberof TransactionStatusResponseAllOf
     */
    error_message?: string | null;
}
/**
 * Check if a given object implements the TransactionStatusResponseAllOf interface.
 */
export declare function instanceOfTransactionStatusResponseAllOf(value: object): boolean;
export declare function TransactionStatusResponseAllOfFromJSON(json: any): TransactionStatusResponseAllOf;
export declare function TransactionStatusResponseAllOfFromJSONTyped(json: any, ignoreDiscriminator: boolean): TransactionStatusResponseAllOf;
export declare function TransactionStatusResponseAllOfToJSON(value?: TransactionStatusResponseAllOf | null): any;