/* istanbul ignore file */ /* tslint:disable */ /* eslint-disable */ import type { AccountSettingsXrpBlockchain } from '../models/AccountSettingsXrpBlockchain'; import type { AccountSettingsXrpBlockchainKMS } from '../models/AccountSettingsXrpBlockchainKMS'; import type { BroadcastKMS } from '../models/BroadcastKMS'; import type { SignatureId } from '../models/SignatureId'; import type { TransactionHash } from '../models/TransactionHash'; import type { TransferXrpBlockchain } from '../models/TransferXrpBlockchain'; import type { TransferXrpBlockchainAsset } from '../models/TransferXrpBlockchainAsset'; import type { TransferXrpBlockchainAssetKMS } from '../models/TransferXrpBlockchainAssetKMS'; import type { TransferXrpBlockchainKMS } from '../models/TransferXrpBlockchainKMS'; import type { TrustLineXrpBlockchain } from '../models/TrustLineXrpBlockchain'; import type { TrustLineXrpBlockchainKMS } from '../models/TrustLineXrpBlockchainKMS'; import type { XrpAccount } from '../models/XrpAccount'; import type { XrpAccountBalance } from '../models/XrpAccountBalance'; import type { XrpAccountTx } from '../models/XrpAccountTx'; import type { XrpFee } from '../models/XrpFee'; import type { XrpInfo } from '../models/XrpInfo'; import type { XrpLedger } from '../models/XrpLedger'; import type { XrpTx } from '../models/XrpTx'; import type { XrpWallet } from '../models/XrpWallet'; import type { CancelablePromise } from '../core/CancelablePromise'; import { request as __request } from '../core/request'; export class XrpService { /** * Generate XRP account *
Generate XRP account. Tatum does not support HD wallet for XRP, only specific address and private key can be generated.
* * @returns XrpWallet OK * @throws ApiError */ public static xrpWallet(): CancelablePromiseGet XRP Blockchain last closed ledger index and hash.
* @returns XrpInfo OK * @throws ApiError */ public static xrpGetLastClosedLedger(): CancelablePromiseGet XRP Blockchain fee. Standard fee for the transaction is available in the drops.base_fee section and is 10 XRP drops by default. * When there is a heavy traffic on the blockchain, fees are increasing according to current traffic.
* * @returns XrpFee OK * @throws ApiError */ public static xrpGetFee(): CancelablePromiseList all Account transactions.
* @param account Address of XRP account. * @param min Ledger version to start scanning for transactions from. * @param marker Marker from the last paginated request. It is stringified JSON from previous response. * @returns XrpAccountTx OK * @throws ApiError */ public static xrpGetAccountTx( account: string, min?: number, marker?: string, ): CancelablePromiseGet ledger by sequence.
* @param i Sequence of XRP ledger. * @returns XrpLedger OK * @throws ApiError */ public static xrpGetLedger( i: number, ): CancelablePromiseGet XRP Transaction by transaction hash.
* @param hash Transaction hash * @returns XrpTx OK * @throws ApiError */ public static xrpGetTransaction( hash: string, ): CancelablePromiseGet XRP Account info.
* @param account Account address you want to get balance of * @returns XrpAccount OK * @throws ApiError */ public static xrpGetAccountInfo( account: string, ): CancelablePromiseGet XRP Account Balance. Obtain balance of the XRP and other assets on the account.
* @param account Account address you want to get balance of * @returns XrpAccountBalance OK * @throws ApiError */ public static xrpGetAccountBalance( account: string, ): CancelablePromiseSend XRP from account to account.
* This operation needs the private key of the blockchain address. Every time the funds are transferred, the transaction must be signed with the corresponding private key.
* No one should ever send it's own private keys to the internet because there is a strong possibility of stealing keys and loss of funds. In this method, it is possible to enter privateKey
* or signatureId. PrivateKey should be used only for quick development on testnet versions of blockchain when there is no risk of losing funds. In production,
* Tatum KMS should be used for the highest security standards, and signatureId should be present in the request.
* Alternatively, using the Tatum client library for supported languages.
*
*
Create / Update / Delete XRP trust line between accounts to transfer private assets.
* By creating trustline for the first time, the asset is created automatically and can be used in the transactions.
* Account setting rippling must be enabled on the issuer account before the trust line creation to asset work correctly.
* Creating a trust line will cause an additional 5 XRP to be blocked on the account.
* This operation needs the private key of the blockchain address. Every time the funds are transferred, the transaction must be signed with the corresponding private key.
* No one should ever send it's own private keys to the internet because there is a strong possibility of stealing keys and loss of funds. In this method, it is possible to enter privateKey
* or signatureId. PrivateKey should be used only for quick development on testnet versions of blockchain when there is no risk of losing funds. In production,
* Tatum KMS should be used for the highest security standards, and signatureId should be present in the request.
* Alternatively, using the Tatum client library for supported languages.
*
Modify XRP account settings. If an XRP account should be an issuer of the custom asset, this accounts should have rippling enabled to true.
* In order to support off-chain processing, required destination tag should be set on the account.
* This operation needs the private key of the blockchain address. Every time the funds are transferred, the transaction must be signed with the corresponding private key.
* No one should ever send it's own private keys to the internet because there is a strong possibility of stealing keys and loss of funds. In this method, it is possible to enter privateKey
* or signatureId. PrivateKey should be used only for quick development on testnet versions of blockchain when there is no risk of losing funds. In production,
* Tatum KMS should be used for the highest security standards, and signatureId should be present in the request.
* Alternatively, using the Tatum client library for supported languages.
*
Broadcast signed transaction to XRP blockchain. This method is used internally from Tatum KMS, Tatum Middleware or Tatum client libraries. * It is possible to create custom signing mechanism and use this method only for broadcasting data to the blockchain.
* * @param requestBody * @returns TransactionHash OK * @throws ApiError */ public static xrpBroadcast( requestBody: BroadcastKMS, ): CancelablePromise