/**
 * 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.
 */
/**
 * These are the Scrypto SBOR `ValueKind`s, but with `Bytes` added as an alias for `Vec`, to display such values as hex-encoded strings.

 * @export
 */
export declare const ProgrammaticScryptoSborValueKind: {
    readonly Bool: "Bool";
    readonly I8: "I8";
    readonly I16: "I16";
    readonly I32: "I32";
    readonly I64: "I64";
    readonly I128: "I128";
    readonly U8: "U8";
    readonly U16: "U16";
    readonly U32: "U32";
    readonly U64: "U64";
    readonly U128: "U128";
    readonly String: "String";
    readonly Enum: "Enum";
    readonly Array: "Array";
    readonly Bytes: "Bytes";
    readonly Map: "Map";
    readonly Tuple: "Tuple";
    readonly Reference: "Reference";
    readonly Own: "Own";
    readonly Decimal: "Decimal";
    readonly PreciseDecimal: "PreciseDecimal";
    readonly NonFungibleLocalId: "NonFungibleLocalId";
};
export type ProgrammaticScryptoSborValueKind = typeof ProgrammaticScryptoSborValueKind[keyof typeof ProgrammaticScryptoSborValueKind];
export declare function ProgrammaticScryptoSborValueKindFromJSON(json: any): ProgrammaticScryptoSborValueKind;
export declare function ProgrammaticScryptoSborValueKindFromJSONTyped(json: any, ignoreDiscriminator: boolean): ProgrammaticScryptoSborValueKind;
export declare function ProgrammaticScryptoSborValueKindToJSON(value?: ProgrammaticScryptoSborValueKind | null): any;