/* istanbul ignore file */ /* tslint:disable */ /* eslint-disable */ import type { BroadcastKMS } from '../models/BroadcastKMS'; import type { CallXdcReadSmartContractMethod } from '../models/CallXdcReadSmartContractMethod'; import type { CallXdcSmartContractMethod } from '../models/CallXdcSmartContractMethod'; import type { CallXdcSmartContractMethodKMS } from '../models/CallXdcSmartContractMethodKMS'; import type { Data } from '../models/Data'; import type { PrivKey } from '../models/PrivKey'; import type { PrivKeyRequest } from '../models/PrivKeyRequest'; import type { SignatureId } from '../models/SignatureId'; import type { TransactionHash } from '../models/TransactionHash'; import type { TransferXdcBlockchain } from '../models/TransferXdcBlockchain'; import type { TransferXdcBlockchainKMS } from '../models/TransferXdcBlockchainKMS'; import type { Wallet } from '../models/Wallet'; import type { XdcBlock } from '../models/XdcBlock'; import type { XdcTx } from '../models/XdcTx'; import type { CancelablePromise } from '../core/CancelablePromise'; import { request as __request } from '../core/request'; export class XinFinService { /** * Generate XDC wallet *
1 credit per API call
*Tatum supports BIP44 HD wallets. It is very convenient and secure, since it can generate 2^31 addresses from 1 mnemonic phrase.
* Mnemonic phrase consists of 24 special words in defined order and can restore access to all generated addresses and private keys.
*
* Each address is identified by 3 main values:
*
Tatum follows BIP44 specification and generates for XDC wallet with derivation path m'/44'/550'/0'/0. * More about BIP44 HD wallets can be found here - https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki. * Generate BIP44 compatible XDC wallet.
* * @param mnemonic Mnemonic to use for generation of extended public and private keys. * @returns Wallet OK * @throws ApiError */ public static xdcGenerateWallet( mnemonic?: string, ): CancelablePromise1 credit per API call
*Generate XDC account deposit address from Extended public key. Deposit address is generated for the specific * index - each extended public key can generate up to 2^31 addresses starting from index 0 until 2^31.
* * @param xpub Extended public key of wallet. * @param index Derivation index of desired address to be generated. * @returns any OK * @throws ApiError */ public static xdcGenerateAddress( xpub: string, index: number, ): CancelablePromise<{ /** * XDC address */ address?: string; }> { return __request({ method: 'GET', path: `/v3/xdc/address/${xpub}/${index}`, errors: { 400: `Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.`, 401: `Unauthorized. Not valid or inactive subscription key present in the HTTP Header.`, 500: `Internal server error. There was an error on the server during the processing of the request.`, }, }); } /** * Generate XDC private key *1 credit per API call
*Generate private key of address from mnemonic for given derivation path index. Private key is generated for the specific index - each mnemonic * can generate up to 2^31 private keys starting from index 0 until 2^31.
* * @param requestBody * @returns PrivKey OK * @throws ApiError */ public static xdcGenerateAddressPrivateKey( requestBody: PrivKeyRequest, ): CancelablePromise2 credits per API call
*This endpoint is deprecated. Use the HTTP-based JSON RPC driver instead.
Use this endpoint URL as a http-based web3 driver to connect directly to the XDC node provided by Tatum. * To learn more about XDC Web3, visit the XDC developer's guide.
* * @param xApiKey Tatum X-API-Key used for authorization. * @param requestBody * @returns any OK * @throws ApiError */ public static xdcWeb3Driver( xApiKey: string, requestBody: any, ): CancelablePromise1 credit per API call
*Get XDC current block number. This is the number of the latest block in the blockchain.
* * @returns number OK * @throws ApiError */ public static xdcGetCurrentBlock(): CancelablePromise1 credit per API call
*Get XDC block by block hash or block number.
* * @param hash Block hash or block number * @returns XdcBlock OK * @throws ApiError */ public static xdcGetBlock( hash: string, ): CancelablePromise1 credit per API call
*Get account balance in XDC. This method does not prints any balance of the ERC20 or ERC721 tokens on the account.
* * @param address Account address you want to get balance of * @returns any OK * @throws ApiError */ public static xdcGetBalance( address: string, ): CancelablePromise<{ /** * Balance in XDC */ balance?: string; }> { return __request({ method: 'GET', path: `/v3/xdc/account/balance/${address}`, errors: { 400: `Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.`, 401: `Unauthorized. Not valid or inactive subscription key present in the HTTP Header.`, 500: `Internal server error. There was an error on the server during the processing of the request.`, }, }); } /** * Get XDC Transaction *2 credits per API call
*Get XDC transaction by transaction hash.
* * @param hash Transaction hash * @returns XdcTx OK * @throws ApiError */ public static xdcGetTransaction( hash: string, ): CancelablePromise1 credit per API call
*Get a number of outgoing XDC transactions for the address. When a transaction is sent, there can be multiple outgoing transactions, * which are not yet processed by the blockchain. To distinguish between them, there is a counter called a nonce, which represents * the order of the transaction in the list of outgoing transactions.
* * @param address address * @returns number OK * @throws ApiError */ public static xdcGetTransactionCount( address: string, ): CancelablePromise2 credits per API call
*Send XDC or Tatum supported ERC20 token from account to account.
*
Signing a transaction
*When sending XDC, you are charged a fee for the transaction, and you must sign the transaction with the private key of the blockchain address from which the fee will be deducted.
*Providing the private key in the API is not a secure way of signing transactions, because the private key can be stolen or exposed. Your private keys should never leave your security perimeter. You should use the private keys only for testing a solution you are building on the testnet of a blockchain.
*For signing transactions on the mainnet, we strongly recommend that you use the Tatum Key Management System (KMS) and provide the signature ID instead of the private key in the API. Alternatively, you can use the Tatum JavaScript client.
* Alternatively, using the Tatum client library for supported languages. * * @param requestBody * @returns any OK * @throws ApiError */ public static xdcBlockchainTransfer( requestBody: (TransferXdcBlockchain | TransferXdcBlockchainKMS), ): CancelablePromise<(TransactionHash | SignatureId)> { return __request({ method: 'POST', path: `/v3/xdc/transaction`, body: requestBody, mediaType: 'application/json', errors: { 400: `Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.`, 401: `Unauthorized. Not valid or inactive subscription key present in the HTTP Header.`, 403: `Forbidden. The request is authenticated, but it is not possible to required perform operation due to logical error or invalid permissions.`, 500: `Internal server error. There was an error on the server during the processing of the request.`, }, }); } /** * Invoke a method in a smart contract on XinFin *2 credits per API call
*Invoke a method in an existing smart contract on XinFin.
*You can call a read-only or write method.
*Signing a transaction
*When invoking a method in a smart contract, you are charged a fee for the transaction, and you must sign the transaction with the private key of the blockchain address from which the fee will be deducted.
*Providing the private key in the API is not a secure way of signing transactions, because the private key can be stolen or exposed. Your private keys should never leave your security perimeter. You should use the private keys only for testing a solution you are building on the testnet of a blockchain.
*For signing transactions on the mainnet, we strongly recommend that you use the Tatum Key Management System (KMS) and provide the signature ID instead of the private key in the API. Alternatively, you can use the Tatum JavaScript client.
* * @param requestBody * @returns any OK * @throws ApiError */ public static xdcBlockchainSmartContractInvocation( requestBody: (CallXdcReadSmartContractMethod | CallXdcSmartContractMethod | CallXdcSmartContractMethodKMS), ): CancelablePromise<(TransactionHash | SignatureId | Data)> { return __request({ method: 'POST', path: `/v3/xdc/smartcontract`, body: requestBody, mediaType: 'application/json', errors: { 400: `Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.`, 401: `Unauthorized. Not valid or inactive subscription key present in the HTTP Header.`, 403: `Forbidden. The request is authenticated, but it is not possible to required perform operation due to logical error or invalid permissions.`, 500: `Internal server error. There was an error on the server during the processing of the request.`, }, }); } /** * Broadcast signed XDC transaction *2 credits per API call
*Broadcast signed transaction to XDC blockchain. This method is used internally from Tatum KMS or Tatum client libraries. * It is possible to create custom signing mechanism and use this method only for broadcasting data to the blockchian.
* * @param requestBody * @returns TransactionHash OK * @throws ApiError */ public static xdcBroadcast( requestBody: BroadcastKMS, ): CancelablePromise