10 credits per API call
\nGet information about blocks (when they were added, how many NFTs and events were ingested and list of transaction hashes that were processed within them) on the following blockchains:
\nTo get started, provide a chain and specify one of the filters listed below (combination of these filters is not allowed):
\n20 credits per API call
\nGet all events on given addresses and / or in the requested block range on the following blockchains:
\nTo get started:
\nAs noted above, aside from general info and hashed event data, the API also decodes them for you in case you filter by one of the following supported event types:
\ntokenTransfer: All transfers of fungible tokens (including stablecoins) and NFTs as per ERC-20 and ERC-721 standard.multitokenTransfer: All transfers of multitokens (both single transfers and batch transfers) as per ERC-1155 standard.stablecoinTransfer: Refers to the transfer of specific stablecoins on the mainnet. Typically, the top 10 to 16 stablecoins on each chain according to CoinMarketCap are included. If the contractAddresses parameter is also used in the filter combination, any tokens specified in it will also be included in the list.uniswapTrade: Provides all swap events that occur on both Uniswap V2 and V3. In some cases, it may not be possible to map the swapped amounts to specific tokens. As a result, certain decoded data such as token amounts might be missing or in the original big number format. This will be indicated by the response parameter partiallyRaw: true.1 credit per API call
\nGet information about latest added block on the following blockchains:
\nTo get started, you can just provide a chain.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:07:05 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 09:07:05 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Data/introduction.md b/v0/Blockchain Data/introduction.md deleted file mode 100644 index 2ad2fd4a..00000000 --- a/v0/Blockchain Data/introduction.md +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: "Introduction" -slug: "introduction" -excerpt: "Blockchain Data is a comprehensive collection of products, designed for developers to easily access on-chain data such as token balances, NFT owners, metadata, and more, all through a suite of user-friendly APIs." -hidden: false -createdAt: "Tue Feb 06 2024 06:16:15 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Tue Feb 06 2024 07:42:50 GMT+0000 (Coordinated Universal Time)" ---- -Blockchain Data offers a reliable, cross chain, scalable, and cost-effective way for developers to access on-chain data, making it an essential tool for any blockchain project. - -Don't have an API key? -
Get one to start using Blockchain Data in your app today.
- Get started for free -1 credit per API call
\nCheck if wallet address owns any specified token (ERC-20, ERC-721 or ERC-1155) on the following blockchains:
\nTo get started:
\ntrue if provided wallet address owns them.false and status code is 200.tokenId.10 credits per API call
\nGet all NFTs (ERC-721 and ERC-1155) and multitokens (ERC-1155 only) of your favorite collections. Our API lets you search for all tokens on:
\nTo get started:
\nexcludeMetadata to true).tokenType.excludeMetadata and tokenType won't have any effect on filtering data.5 credits per API call
\nGet metadata of NFTs (ERC-721 and ERC-1155) or multitokens (ERC-1155 only) by IDs for a given token address! Our API lets you search for all tokens on:
\nTo get started:
\n20 credits per API call
\nGet all addresses that own your favorite token (ERC-20, ERC-721 or ERC-1155)! Our API lets you search for all token owners on:
\nTo get started:
\ntokenId. In case of multitoken, result is an array of addresses.1 credit per API call
\nGet information about your favorite token! Our API lets you search for all tokens on:
\nTo get started:
\ntokenId as a query parameter.10 credits per API call
\nEstimate the current fee for different types of transactions.
\nThis API is supported for the following blockchains:
\n1 credit per API call
\nGet the recommended fee/gas price for a blockchain.
\nFee is in satoshis(meaning currency(BTC, DOGE,... / 100 000 000) per byte\n
This API is supported for the following blockchains:
\n20 credits per API call
\nGet transactions on the following blockchains:
\nTo get started:
\ntransactionTypes and even transactionSubtype (incoming, outgoing, zero-transfer).addresses query parameter. Following query parameters won't have any effect on filtering data: transactionTypes, transactionSubtype, tokenId, blockTo.pageSize and offset query parameters. \ncursor query parameter, by filling in the value from prevPage or nextPage field in the response body.5 credits per API call
\nGet transactions by hash on the following blockchains:
\nTo get started:
\n50 credits per API call
\nGet balances of fungible tokens (ERC-20), NFTs (ERC-721 and ERC-1155) or multitokens (ERC-1155 only) for a specific wallet address on the following blockchains:
\nTo get started:
\nexcludeMetadata to true).tokenTypes.excludeMetadata.100 credits per API call
\nGet unspent UTXOs for a specific address up to a specific total amount.\nIf you want to prepare a transaction on UTXO-based chains like Bitcoin, you need to enter unspent UTXOs to be able to perform a transaction. By providing ```totalValue``` as a total, our API will return a list of UTXOs that will be enough to cover the transaction.
\nOur API lets you get the unpenst UTXOs for a specific address on:\nTo get started:
\nActivates an account.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:24:13 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/account/blockamount.md b/v0/Blockchain Utility InP/account/blockamount.md deleted file mode 100644 index a9bb5b8e..00000000 --- a/v0/Blockchain Utility InP/account/blockamount.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Block an amount in an account" -slug: "blockamount" -excerpt: "Blocks an amount in an account. Any number of distinct amounts can be blocked in one account.\nEvery new blockage has its own distinct ID, which is used as a reference. When the amount is blocked, it is debited from the available balance of the account.\nThe account balance remains the same. The account balance represents the total amount of funds in the account. The available balance represents the total amount of funds that can be used to perform transactions. When an account is frozen, the available balance is set to 0 minus all blockages for the account.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:24:15 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/account/createaccount.md b/v0/Blockchain Utility InP/account/createaccount.md deleted file mode 100644 index 0604f9ad..00000000 --- a/v0/Blockchain Utility InP/account/createaccount.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Create a virtual account" -slug: "createaccount" -excerpt: "2 credits per API call
\nCreate a new virtual account for a customer.
\nYou can create a virtual account for any supported cryptocurrency, fiat currency, Tatum virtual currency, or fungible tokens created within Tatum. Once the currency/asset is set for a virtual account, it cannot be changed.
\nVirtual account balance
\nA virtual account has its own balance. The balance can be logically presented by the account balance and available balance:
\naccountBalance) represents all assets on the account, both available and blocked.availableBalance) represents the account balance minus the blocked assets. Use the available balance to determine how much a customer can send or withdraw from their virtual account.Cryptocurrency virtual accounts
\nWhen you create a virtual account based on a cryptocurrency (for example, BTC or ETH), you have to provide the extended public key (xpub) of the blockchain wallet that will be connected to this account.
NOTE: Adding xpub to the virtual account does not connect any specific blockchain address to this account. xpub is a generator of addresses, not an address itself.
Not all blockchains provide xpub for wallets, or Tatum may not support wallets on some blockchains. In such cases, use the wallet address or the account address instead.
xpub provided; use address from the generated wallet instead.xpub from the generated wallet.xpub provided; use address from the generated wallet instead.xpub from the generated wallet instead.xpub from the generated wallet instead.xpub from the generated wallet.xpub from the generated wallet.xpub provided; use address from the generated blockchain address instead.xpub from the generated wallet.xpub from the generated wallet.xpub from the generated wallet.xpub from the generated wallet.xpub from the generated wallet.xpub from the generated wallet.xpub provided; use address from the generated wallet instead.xpub from the generated wallet.xpub from the generated wallet.xpub provided; use address from the generated account instead.xpub provided; use address from the generated account instead.Connect a virtual account to the blockchain
\nxpub, generate a new blockchain address for this account.xpub, assign an existing blockchain address to this account.You can connect multiple blockchain addresses to one virtual account.
\nDigital assets:
\n0x2791bca1f2de4661ed88a30c99a7a9449aa84174 on Polygon mainnet.0x3c499c542cef5e3811e1192ce70d8cc03d5c3359 on Polygon mainnet.Creates new accounts for the customer in a batch call.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:24:15 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/account/deactivateaccount.md b/v0/Blockchain Utility InP/account/deactivateaccount.md deleted file mode 100644 index d8e417c3..00000000 --- a/v0/Blockchain Utility InP/account/deactivateaccount.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Deactivate account" -slug: "deactivateaccount" -excerpt: "Deactivates an account. Only accounts with account and available balances of zero can be deactivated. Deactivated accounts are not visible in the list of accounts, it is not possible to send funds to these accounts or perform transactions. However, they are still present in the ledger and all transaction histories.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:23:37 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/account/deleteallblockamount.md b/v0/Blockchain Utility InP/account/deleteallblockamount.md deleted file mode 100644 index a56c014a..00000000 --- a/v0/Blockchain Utility InP/account/deleteallblockamount.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Unblock all blocked amounts in an account" -slug: "deleteallblockamount" -excerpt: "Unblocks previously blocked amounts in an account. Increases the available balance in the account where the amount was blocked.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:24:15 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/account/deleteblockamount.md b/v0/Blockchain Utility InP/account/deleteblockamount.md deleted file mode 100644 index 4a896607..00000000 --- a/v0/Blockchain Utility InP/account/deleteblockamount.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Unblock a blocked amount in an account" -slug: "deleteblockamount" -excerpt: "Unblocks a previously blocked amount in an account. Increases the available balance in the account where the amount was blocked.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:24:15 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/account/freezeaccount.md b/v0/Blockchain Utility InP/account/freezeaccount.md deleted file mode 100644 index 7041ed29..00000000 --- a/v0/Blockchain Utility InP/account/freezeaccount.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Freeze account" -slug: "freezeaccount" -excerpt: "Disables all outgoing transactions. Incoming transactions to the account are available. When an account is frozen, its available balance is set to 0. This operation will create a new blockage of type ACCOUNT_FROZEN, which is automatically deleted when the account is unfrozen.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:24:15 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/account/getaccountbalance.md b/v0/Blockchain Utility InP/account/getaccountbalance.md deleted file mode 100644 index 0ab216fe..00000000 --- a/v0/Blockchain Utility InP/account/getaccountbalance.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Get account balance" -slug: "getaccountbalance" -excerpt: "Get balance for the account.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:24:15 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/account/getaccountbyaccountid.md b/v0/Blockchain Utility InP/account/getaccountbyaccountid.md deleted file mode 100644 index 26f4d82e..00000000 --- a/v0/Blockchain Utility InP/account/getaccountbyaccountid.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Get account by ID" -slug: "getaccountbyaccountid" -excerpt: "Gets active account by ID. Displays all information regarding the given account.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:24:15 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/account/getaccounts.md b/v0/Blockchain Utility InP/account/getaccounts.md deleted file mode 100644 index bd3d7adf..00000000 --- a/v0/Blockchain Utility InP/account/getaccounts.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "List all accounts" -slug: "getaccounts" -excerpt: "Lists all accounts. Inactive accounts are also visible.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:24:15 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/account/getaccountsbycustomerid.md b/v0/Blockchain Utility InP/account/getaccountsbycustomerid.md deleted file mode 100644 index b4c175c6..00000000 --- a/v0/Blockchain Utility InP/account/getaccountsbycustomerid.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "List all customer accounts" -slug: "getaccountsbycustomerid" -excerpt: "Lists all accounts associated with a customer. Only active accounts are visible.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:24:15 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/account/getaccountscount.md b/v0/Blockchain Utility InP/account/getaccountscount.md deleted file mode 100644 index 16c9a23e..00000000 --- a/v0/Blockchain Utility InP/account/getaccountscount.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Count of found entities for get accounts request" -slug: "getaccountscount" -excerpt: "Count of accounts that were found from /v3/ledger/account
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:24:15 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/account/getblockamount.md b/v0/Blockchain Utility InP/account/getblockamount.md deleted file mode 100644 index c4c56a5f..00000000 --- a/v0/Blockchain Utility InP/account/getblockamount.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Get blocked amounts in an account" -slug: "getblockamount" -excerpt: "Gets blocked amounts for an account.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:23:38 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/account/getblockamountbyid.md b/v0/Blockchain Utility InP/account/getblockamountbyid.md deleted file mode 100644 index 465363e8..00000000 --- a/v0/Blockchain Utility InP/account/getblockamountbyid.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Get blocked amount by ID" -slug: "getblockamountbyid" -excerpt: "Gets blocked amount by id.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:24:15 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/account/unblockamountwithtransaction.md b/v0/Blockchain Utility InP/account/unblockamountwithtransaction.md deleted file mode 100644 index b98cee04..00000000 --- a/v0/Blockchain Utility InP/account/unblockamountwithtransaction.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Unblock an amount in an account and perform a transaction" -slug: "unblockamountwithtransaction" -excerpt: "Unblocks a previously blocked amount in an account and invokes a ledger transaction from that account to a different recipient.\nIf the request fails, the amount is not unblocked.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:23:38 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/account/unfreezeaccount.md b/v0/Blockchain Utility InP/account/unfreezeaccount.md deleted file mode 100644 index c37603f6..00000000 --- a/v0/Blockchain Utility InP/account/unfreezeaccount.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Unfreeze account" -slug: "unfreezeaccount" -excerpt: "Unfreezes a previously frozen account. Unfreezing a non-frozen account not affect the account.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:23:37 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/account/updateaccountbyaccountid.md b/v0/Blockchain Utility InP/account/updateaccountbyaccountid.md deleted file mode 100644 index 50884ff1..00000000 --- a/v0/Blockchain Utility InP/account/updateaccountbyaccountid.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Update account" -slug: "updateaccountbyaccountid" -excerpt: "Update account by ID. Only a small number of fields can be updated.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:23:38 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/customer.md b/v0/Blockchain Utility InP/customer.md deleted file mode 100644 index 6ea695f0..00000000 --- a/v0/Blockchain Utility InP/customer.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Customer" -slug: "customer" -excerpt: "" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:24:15 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/customer/activatecustomer.md b/v0/Blockchain Utility InP/customer/activatecustomer.md deleted file mode 100644 index d94e7d35..00000000 --- a/v0/Blockchain Utility InP/customer/activatecustomer.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Activate customer" -slug: "activatecustomer" -excerpt: "Activated customer is able to do any operation.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:24:14 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/customer/deactivatecustomer.md b/v0/Blockchain Utility InP/customer/deactivatecustomer.md deleted file mode 100644 index ada00ba9..00000000 --- a/v0/Blockchain Utility InP/customer/deactivatecustomer.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Deactivate customer" -slug: "deactivatecustomer" -excerpt: "Deactivate customer is not able to do any operation. Customer can be deactivated only when all their accounts are already deactivated.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:24:14 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/customer/disablecustomer.md b/v0/Blockchain Utility InP/customer/disablecustomer.md deleted file mode 100644 index 1bde8e07..00000000 --- a/v0/Blockchain Utility InP/customer/disablecustomer.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Disable customer" -slug: "disablecustomer" -excerpt: "Disabled customer cannot perform end-user operations, such as create new accounts or send transactions. Available balance on all accounts is set to 0. Account balance will stay untouched.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:24:14 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/customer/enablecustomer.md b/v0/Blockchain Utility InP/customer/enablecustomer.md deleted file mode 100644 index 882f3fe1..00000000 --- a/v0/Blockchain Utility InP/customer/enablecustomer.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Enable customer" -slug: "enablecustomer" -excerpt: "Enabled customer can perform all operations. By default all customers are enabled. All previously blocked account balances will be unblocked.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:24:14 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/customer/findallcustomers.md b/v0/Blockchain Utility InP/customer/findallcustomers.md deleted file mode 100644 index 493b66f2..00000000 --- a/v0/Blockchain Utility InP/customer/findallcustomers.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "List all customers" -slug: "findallcustomers" -excerpt: "List of all customers. Also inactive an disabled customers are present.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:24:14 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/customer/getcustomerbyexternalorinternalid.md b/v0/Blockchain Utility InP/customer/getcustomerbyexternalorinternalid.md deleted file mode 100644 index 8fadf556..00000000 --- a/v0/Blockchain Utility InP/customer/getcustomerbyexternalorinternalid.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Get customer details" -slug: "getcustomerbyexternalorinternalid" -excerpt: "Using anonymized external ID or internal customer ID you can access customer detail information. Internal ID is needed to call other customer related methods.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:24:14 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/customer/updatecustomer.md b/v0/Blockchain Utility InP/customer/updatecustomer.md deleted file mode 100644 index 603b11e1..00000000 --- a/v0/Blockchain Utility InP/customer/updatecustomer.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Update customer" -slug: "updatecustomer" -excerpt: "This method is helpful in case your primary system will change ID's or customer will change the country he/she is supposed to be in compliance with.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:24:14 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/deposit.md b/v0/Blockchain Utility InP/deposit.md deleted file mode 100644 index df04aaea..00000000 --- a/v0/Blockchain Utility InP/deposit.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Deposit" -slug: "deposit" -excerpt: "" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:24:15 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/deposit/getdeposits.md b/v0/Blockchain Utility InP/deposit/getdeposits.md deleted file mode 100644 index 7f050770..00000000 --- a/v0/Blockchain Utility InP/deposit/getdeposits.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "List all deposits for product" -slug: "getdeposits" -excerpt: "Lists all deposits for API key.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:23:37 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/deposit/getdepositscount.md b/v0/Blockchain Utility InP/deposit/getdepositscount.md deleted file mode 100644 index f431db63..00000000 --- a/v0/Blockchain Utility InP/deposit/getdepositscount.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Count of found entities for get deposits request" -slug: "getdepositscount" -excerpt: "Counts total entities found by get deposits request.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:23:37 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/transaction.md b/v0/Blockchain Utility InP/transaction.md deleted file mode 100644 index 151b4391..00000000 --- a/v0/Blockchain Utility InP/transaction.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Transaction" -slug: "transaction" -excerpt: "" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:24:15 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/transaction/gettransactions-1.md b/v0/Blockchain Utility InP/transaction/gettransactions-1.md deleted file mode 100644 index 791f4d86..00000000 --- a/v0/Blockchain Utility InP/transaction/gettransactions-1.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Find transactions within the ledger." -slug: "gettransactions-1" -excerpt: "Find transactions across whole ledger.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:24:14 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/transaction/gettransactionsbyaccountid.md b/v0/Blockchain Utility InP/transaction/gettransactionsbyaccountid.md deleted file mode 100644 index a6ebb327..00000000 --- a/v0/Blockchain Utility InP/transaction/gettransactionsbyaccountid.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Find transactions for account." -slug: "gettransactionsbyaccountid" -excerpt: "Finds transactions for the account identified by the given account ID.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:24:14 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/transaction/gettransactionsbycustomerid.md b/v0/Blockchain Utility InP/transaction/gettransactionsbycustomerid.md deleted file mode 100644 index bbea2471..00000000 --- a/v0/Blockchain Utility InP/transaction/gettransactionsbycustomerid.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Find transactions for a customer across all of the customer's accounts." -slug: "gettransactionsbycustomerid" -excerpt: "Finds transactions for all accounts of the customer identified by the given internal customer ID.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 09:09:15 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/transaction/gettransactionsbyreference.md b/v0/Blockchain Utility InP/transaction/gettransactionsbyreference.md deleted file mode 100644 index dbb12586..00000000 --- a/v0/Blockchain Utility InP/transaction/gettransactionsbyreference.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Find transactions with a given reference across all accounts." -slug: "gettransactionsbyreference" -excerpt: "Finds transactions for all accounts with the given reference.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:24:14 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/transaction/sendtransaction.md b/v0/Blockchain Utility InP/transaction/sendtransaction.md deleted file mode 100644 index 810dee07..00000000 --- a/v0/Blockchain Utility InP/transaction/sendtransaction.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Send payment" -slug: "sendtransaction" -excerpt: "Sends a payment within Tatum Private Ledger. All assets are settled instantly.
\nWhen a transaction is settled, 2 transaction records are created, 1 for each of the participants. These 2 records are connected via a transaction reference, which is the same for both of them.
\nThis method is only used for transferring assets between accounts within Tatum and will not send any funds to blockchain addresses.
\nIf there is an insufficient balance in the sender account, no transaction is recorded.
\nIt is possible to perform an anonymous transaction where the sender account is not visible for the recipient.
\nThe FIAT currency value of every transaction is calculated automatically. The FIAT value is based on the accountingCurrency of the account connected to the transaction and is available in the marketValue parameter of the transaction.
Sends the N payments within Tatum Private Ledger. All assets are settled instantly.
\nWhen a transaction is settled, 2 transaction records are created, 1 for each of the participants. These 2 records are connected via a transaction reference, which is the same for both of them.
\nThis method is only used for transferring assets between accounts within Tatum and will not send any funds to blockchain addresses.
\nIf there is an insufficient balance in the sender account, no transaction is recorded.
\nIt is possible to perform an anonymous transaction where the sender account is not visible for the recipient.
\nThe FIAT currency value of every transaction is calculated automatically. The FIAT value is based on the accountingCurrency of the account connected to the transaction and is available in the marketValue parameter of the transaction.
2 credits per API call
\nCreate new virtual currency with given supply stored in account. This will create Tatum internal virtual currency. Every virtual currency must be prefixed with VC_.
\nEvery virtual currency must be pegged to existing FIAT or supported cryptocurrency. 1 unit of virtual currency has then the same amount as 1 unit of the base currency it is pegged to. It is possible to set a custom base rate for the virtual currency. (baseRate = 2 => 1 VC unit = 2 basePair units)
\nTatum virtual currency acts as any other asset within Tatum. To create a fungible token, see the API for deploying a fungible token smart contract.
\nThis operation returns the newly created Tatum Ledger account with an initial balance set to the virtual currency's total supply. Total supply can be changed in the future.
\nDigital assets:
\n0x2791bca1f2de4661ed88a30c99a7a9449aa84174 on Polygon mainnet.0x3c499c542cef5e3811e1192ce70d8cc03d5c3359 on Polygon mainnet.1 credit per API call
\nGet detail of virtual currency.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:24:14 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/virtual-currency/mintcurrency.md b/v0/Blockchain Utility InP/virtual-currency/mintcurrency.md deleted file mode 100644 index 856995c7..00000000 --- a/v0/Blockchain Utility InP/virtual-currency/mintcurrency.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Create new supply of virtual currency" -slug: "mintcurrency" -excerpt: "2 credits per API call
\nCreate new supply of virtual currency linked on the given accountId. Method increases the total supply of the currency.
\nThis method creates Ledger transaction with operationType MINT with undefined counterAccountId.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:24:15 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain Utility InP/virtual-currency/revokecurrency.md b/v0/Blockchain Utility InP/virtual-currency/revokecurrency.md deleted file mode 100644 index ab429543..00000000 --- a/v0/Blockchain Utility InP/virtual-currency/revokecurrency.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Destroy supply of virtual currency" -slug: "revokecurrency" -excerpt: "Destroy supply of virtual currency linked on the given accountId. Method decreases the total supply of the currency.
\nThis method creates Ledger transaction with operationType REVOKE with undefined counterAccountId.
Change base pair and/or base rate of existing virtual currency.
" -hidden: false -createdAt: "Mon Feb 05 2024 09:09:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:23:38 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain operations/contracts-deployments.md b/v0/Blockchain operations/contracts-deployments.md deleted file mode 100644 index 3eef7c63..00000000 --- a/v0/Blockchain operations/contracts-deployments.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Contracts Deployments" -slug: "contracts-deployments" -excerpt: "" -hidden: false -createdAt: "Mon Feb 05 2024 11:37:18 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:37:18 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain operations/exchange-rate.md b/v0/Blockchain operations/exchange-rate.md deleted file mode 100644 index 4ebf2abb..00000000 --- a/v0/Blockchain operations/exchange-rate.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Exchange Rate" -slug: "exchange-rate" -excerpt: "" -hidden: false -createdAt: "Tue Feb 20 2024 06:59:36 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Tue Feb 20 2024 06:59:48 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain operations/execute-contract-functions.md b/v0/Blockchain operations/execute-contract-functions.md deleted file mode 100644 index bf71eefe..00000000 --- a/v0/Blockchain operations/execute-contract-functions.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Execute Contract Functions" -slug: "execute-contract-functions" -excerpt: "" -hidden: false -createdAt: "Mon Feb 05 2024 11:38:49 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:49 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain operations/fee-estimation.md b/v0/Blockchain operations/fee-estimation.md deleted file mode 100644 index 3a4dea42..00000000 --- a/v0/Blockchain operations/fee-estimation.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Fee Estimation" -slug: "fee-estimation" -excerpt: "" -hidden: false -createdAt: "Mon Feb 05 2024 11:52:55 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:52:55 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain operations/storage-logs.md b/v0/Blockchain operations/storage-logs.md deleted file mode 100644 index 3b4f99c9..00000000 --- a/v0/Blockchain operations/storage-logs.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Storage - Logs" -slug: "storage-logs" -excerpt: "" -hidden: false -createdAt: "Mon Feb 05 2024 11:56:44 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Tue Feb 06 2024 07:02:38 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain operations/strorage-ipfs.md b/v0/Blockchain operations/strorage-ipfs.md deleted file mode 100644 index 3c82f38a..00000000 --- a/v0/Blockchain operations/strorage-ipfs.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Strorage - IPFS" -slug: "strorage-ipfs" -excerpt: "" -hidden: false -createdAt: "Mon Feb 05 2024 11:53:45 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:53:50 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain operations/transact.md b/v0/Blockchain operations/transact.md deleted file mode 100644 index 186d192f..00000000 --- a/v0/Blockchain operations/transact.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Transact" -slug: "transact" -excerpt: "" -hidden: false -createdAt: "Tue Feb 20 2024 07:00:27 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Tue Feb 20 2024 07:00:33 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockchain operations/wallet-operations.md b/v0/Blockchain operations/wallet-operations.md deleted file mode 100644 index 7c182e6b..00000000 --- a/v0/Blockchain operations/wallet-operations.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Wallet Operations" -slug: "wallet-operations" -excerpt: "" -hidden: false -createdAt: "Mon Feb 05 2024 11:26:28 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:26:28 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockhain Abstraction/auction.md b/v0/Blockhain Abstraction/auction.md deleted file mode 100644 index ebeee282..00000000 --- a/v0/Blockhain Abstraction/auction.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Auction" -slug: "auction" -excerpt: "" -hidden: false -createdAt: "Mon Feb 05 2024 11:52:32 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:52:32 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockhain Abstraction/custodial.md b/v0/Blockhain Abstraction/custodial.md deleted file mode 100644 index d2649880..00000000 --- a/v0/Blockhain Abstraction/custodial.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Custodial Wallet" -slug: "custodial" -excerpt: "" -hidden: false -createdAt: "Mon Feb 05 2024 11:55:21 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Feb 07 2024 09:41:03 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockhain Abstraction/gas-pump.md b/v0/Blockhain Abstraction/gas-pump.md deleted file mode 100644 index 8214c8e5..00000000 --- a/v0/Blockhain Abstraction/gas-pump.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Gas Pump" -slug: "gas-pump" -excerpt: "" -hidden: false -createdAt: "Mon Feb 05 2024 11:51:39 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:51:39 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockhain Abstraction/kms.md b/v0/Blockhain Abstraction/kms.md deleted file mode 100644 index 51dcc03b..00000000 --- a/v0/Blockhain Abstraction/kms.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "KMS" -slug: "kms" -excerpt: "" -hidden: false -createdAt: "Mon Feb 05 2024 11:55:12 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:55:13 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockhain Abstraction/marketplace.md b/v0/Blockhain Abstraction/marketplace.md deleted file mode 100644 index 2919696f..00000000 --- a/v0/Blockhain Abstraction/marketplace.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Marketplace" -slug: "marketplace" -excerpt: "" -hidden: false -createdAt: "Mon Feb 05 2024 11:52:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:52:23 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockhain Abstraction/virtual-accounts-1.md b/v0/Blockhain Abstraction/virtual-accounts-1.md deleted file mode 100644 index aba699bd..00000000 --- a/v0/Blockhain Abstraction/virtual-accounts-1.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Virtual Accounts" -slug: "virtual-accounts-1" -excerpt: "" -hidden: false -createdAt: "Mon Feb 05 2024 11:55:33 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:55:34 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Blockhain Abstraction/virtual-accounts-1/accounts.md b/v0/Blockhain Abstraction/virtual-accounts-1/accounts.md deleted file mode 100644 index d31e5675..00000000 --- a/v0/Blockhain Abstraction/virtual-accounts-1/accounts.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Accounts" -slug: "accounts" -excerpt: "" -hidden: true -createdAt: "Mon Feb 19 2024 14:14:26 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 19 2024 14:14:27 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Documentation/getting-started.md b/v0/Documentation/getting-started.md deleted file mode 100644 index 918541ed..00000000 --- a/v0/Documentation/getting-started.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: "Getting Started with Tatum 🚀" -slug: "getting-started" -excerpt: "Welcome to Tatum SDK!" -hidden: false -createdAt: "Thu Jan 18 2024 08:41:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Jan 24 2024 17:04:07 GMT+0000 (Coordinated Universal Time)" ---- -Tatum's API and SDK are here to make your life easier when building blockchain applications! No more complicated setups, no need for previous blockchain experience. We've got you covered. - -# Why Tatum? 💡 - -1. **Super fast development:** Start building blockchain applications in no time. -2. **No previous blockchain experience required:** Perfect for beginners and experts alike. -3. **One line of code:** Perform complex tasks with minimal effort. - -# Key Features 🌟 - -- Monitor activity on a blockchain address 🕵️♂️ -- Perform RPC calls to various blockchains 📞 -- Read information about NFTs such as balances, transactions, or ownerships 🖼️ -- Get information about a specific wallet like balances or transaction history 💰 - -Ready to build fantastic blockchain applications? Check out the official documentation for more information and examples! - -Happy coding! 🎉 - -> 📘 **[Join our Discord](https://discord.com/invite/tatum) **to stay up to date with the latest updates from product news to upcoming events. -> -> You'll also be able to submit feedback and help shape future updates. Learn more about our community [here](https://tatum.io/community). diff --git a/v0/Documentation/getting-started/testing-this.md b/v0/Documentation/getting-started/testing-this.md deleted file mode 100644 index d97160ca..00000000 --- a/v0/Documentation/getting-started/testing-this.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: "Reusable Components" -slug: "testing-this" -excerpt: "" -hidden: true -createdAt: "Thu Jan 18 2024 11:13:56 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Jan 22 2024 13:05:04 GMT+0000 (Coordinated Universal Time)" ---- -Sign Up - -> 📘 **[Join our Discord](https://discord.com/invite/tatum) **to stay up to date with the latest updates from product news to upcoming events. -> -> You'll also be able to submit feedback and help shape future updates. Learn more about our community [here](https://tatum.io/community). diff --git a/v0/Guides/auth-api-keys-mainnet-vs-testnet.md b/v0/Guides/auth-api-keys-mainnet-vs-testnet.md deleted file mode 100644 index 3756a3f4..00000000 --- a/v0/Guides/auth-api-keys-mainnet-vs-testnet.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: "Auth API Keys: Mainnet vs Testnet" -slug: "auth-api-keys-mainnet-vs-testnet" -excerpt: "" -hidden: false -createdAt: "Mon Jan 29 2024 12:04:54 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 08:41:51 GMT+0000 (Coordinated Universal Time)" ---- -When you sign up in the [Tatum.io Dashboard](https://dashboard.tatum.io/login), you'll get one development (Testnet) Auth API key and one for production (Mainnet) API key. You can create more API keys as you need them. - -- **Mainnet** stands for "main network". This is where your production app will run. -- **Testnet** stands for "testing network". In most cases, has the same features and characteristics as the mainnet. The Testnet blockchain is completely isolated from the Mainnet blockchain. It doesn't have the same data, and it doesn't guarantee data persistence. On the other hand, all operations on the Testnet are free. This makes Testnet a great environment for developing and testing apps. - -> 🚧 All **Mainnet** transactions are final. If you send assets like BTC to the wrong address over Testnet it's fine since Testnet assets hold no value. However, if this happens in Mainnet, you'll lose real money! diff --git a/v0/Guides/blockchain-operations.md b/v0/Guides/blockchain-operations.md deleted file mode 100644 index aabef4ca..00000000 --- a/v0/Guides/blockchain-operations.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Blockchain Operations" -slug: "blockchain-operations" -excerpt: "" -hidden: false -createdAt: "Sat Jan 27 2024 18:03:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 08:42:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Guides/blockchain-operations/cancel-or-replace-a-blockchain-transaction.md b/v0/Guides/blockchain-operations/cancel-or-replace-a-blockchain-transaction.md deleted file mode 100644 index dc7fe70b..00000000 --- a/v0/Guides/blockchain-operations/cancel-or-replace-a-blockchain-transaction.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: "Cancel or Replace a blockchain transaction" -slug: "cancel-or-replace-a-blockchain-transaction" -excerpt: "" -hidden: false -createdAt: "Mon Jan 29 2024 10:11:40 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 08:42:10 GMT+0000 (Coordinated Universal Time)" ---- -In some cases, you may want to cancel or replace a transaction. - -- **Cancel**: for EVM chains (like Ethereum), it may be possible to replace a pending transaction in the mempool via another one with value zero (0) to your own address. UTXO transactions can't be "canceled". -- **Replace**: for UTXO chains (like Bitcoin), it may be possible to increase the fee of a pending transaction via [RBF](https://tatumdocs.readme.io/docs/bitcoin-replace-by-fee-and-stuck-transactions-in-the-mempool) (if enabled) or via [CPFP](https://tatumdocs.readme.io/docs/bitcoin-cpfp-and-stuck-transactions-in-the-mempool). For EVM chains, it may be possible to replace a pending transaction. - -## Cancelling a transaction - -EVM chains allow a bit of a trick to cancel a pending (unconfirmed) transaction in the mempool: - -1. Verify the transaction you want to cancel is not confirmed yet and is still pending in the mempool. Check an Explorer. -2. Verify the nonce value of the unconfirmed transaction you want to cancel. -3. Create a new transaction where the sender and receiver blockchain address is the same with a zero (0) amount. Use the same nonce value you got from step 2 and put a much higher fee. -4. Broadcast this transaction. Ideally, the miners will prioritize this new transaction over the original due to a higher fee. -5. If all worked well, your new transaction will get confirmed first and the original will be dropped due to invalid. - -## Replacing a transaction - -UTXO chains may allow [RBF](https://tatumdocs.readme.io/docs/bitcoin-replace-by-fee-and-stuck-transactions-in-the-mempool) or in some cases [CPFP](https://tatumdocs.readme.io/docs/bitcoin-cpfp-and-stuck-transactions-in-the-mempool) on pending (unconfirmed) transactions. - -EVM chains may allow replacing a transaction using the same method as if you were to cancel it: - -1. Verify the transaction you want to cancel is not confirmed yet and is still pending in the mempool. Check an Explorer. -2. Verify the nonce value of the unconfirmed transaction you want to replace. -3. Create a new transaction where the receiver blockchain address may or may not be the same as in the original to replace. Use the same nonce value you got from step 2 and put a much higher fee. -4. Broadcast this transaction. Ideally, the miners will prioritize this new transaction over the original due to a higher fee. -5. If all works well, your new transaction will get confirmed first and the original will be dropped due to invalid. - -## Good to know - -- Incorrectly executed transactions may result in the loss of funds. -- Blockchain transactions, once confirmed, are irreversible. There's no guarantee of success in canceling or replacing them. diff --git a/v0/Guides/blockchain-operations/evm-like-ethereum.md b/v0/Guides/blockchain-operations/evm-like-ethereum.md deleted file mode 100644 index 48c8ef3e..00000000 --- a/v0/Guides/blockchain-operations/evm-like-ethereum.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "EVM (like Ethereum)" -slug: "evm-like-ethereum" -excerpt: "" -hidden: false -createdAt: "Sat Jan 27 2024 18:04:29 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 08:42:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v0/Guides/blockchain-operations/mnemonic-derivation-path.md b/v0/Guides/blockchain-operations/mnemonic-derivation-path.md deleted file mode 100644 index b20ddfbe..00000000 --- a/v0/Guides/blockchain-operations/mnemonic-derivation-path.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: "Mnemonic Derivation Path" -slug: "mnemonic-derivation-path" -excerpt: "" -hidden: false -createdAt: "Mon Jan 29 2024 10:19:43 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 08:42:10 GMT+0000 (Coordinated Universal Time)" ---- -In blockchain technology, the **Derivation path** is a critical element of a wallet structure. The Derivation Path determines how exactly a wallet generates the XPUB, addresses, and Private Keys. - -To generate the expected Blockchain Addresses and Private Keys, the **Derivation Path must match 1:1**. Blockchain Addresses generated via other services external to the Tatum API and or KMS may or may not match the expected Derivation Path. For example, Wallet services like [MetaMask use a different derivation path](https://metamask.zendesk.com/hc/en-us/articles/360060331752). - -> 📘 Tatum wallets use specific Mnemonic derivation paths per chain. These derivation paths are the same for API, SDKs, and KMS. - -## Tatum Mnemonic Derivation Paths - -```Text JSON -//MAINNET - BTC: "m/44'/0'/0'/0", //SegWit (starts with a "bc1q") - LTC: "m/44'/2'/0'/0", - ETH: "m/44'/60'/0'/0", - DOGE: "m/44'/3'/0'/0", - CELO: "m/44'/52752'/0'/0", - POLYGON: "m/44'/966'/0'/0", - KCS: "m/44'/60'/0'/0", - HARMONY: "m/44'/1023'/0'/0", - KLAY: "m/44'/8217'/0'/0", - BSC: "m/44'/60'/0'/0", - BCH: "m/44'/145'/0'/0", - TRON: "m/44'/195'/0'/0", - EGLD: "m/44'/508'/0'/0'", - ALGO: '@TODO - TBD', - ADA: "m/1852'/1815'/0'", - FLOW: "m/44'/539'/0'/0", - NEO: "m/44'/888'/0'/0", - SOL: "m/44'/501'/0'/0'", - VET: "m/44'/818'/0'/0", - XDC: "m/44'/550'/0'/0", - XLM: "m/44'/148'/0'", - XRP: "m/44'/144'/0'/0", - BNB: "m/44'/714'/0'/0", - -//TESTNET - COMMON_TESTNET_DERIVATION_PATH = "m/44'/1'/0'/0" -``` - -> 📘 Additional information is available at [the following link](https://github.com/tatumio/tatum-js/blob/ad5471b726ae3c0e0578862b480264f89b69b11d/src/constants.ts). diff --git a/v0/Guides/blockchain-operations/testnet-faucets.md b/v0/Guides/blockchain-operations/testnet-faucets.md deleted file mode 100644 index 07503bc3..00000000 --- a/v0/Guides/blockchain-operations/testnet-faucets.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: "Testnet Faucets" -slug: "testnet-faucets" -excerpt: "" -hidden: false -createdAt: "Mon Jan 29 2024 12:00:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 08:42:10 GMT+0000 (Coordinated Universal Time)" ---- -Tatum has an official faucet for you to get Tesnet coins:Don't have an API key? -
Get one to start using Blockchain Data in your app today.
- Get started for free -1 credit per API call
\nCheck if wallet address owns any specified token (ERC-20, ERC-721 or ERC-1155) on the following blockchains:
\nTo get started:
\ntrue if provided wallet address owns them.false and status code is 200.tokenId.50 credits per API call
\nGet balances of fungible tokens (ERC-20), NFTs (ERC-721 and ERC-1155) or multitokens (ERC-1155 only) for a specific wallet address on the following blockchains:
\nTo get started:
\nexcludeMetadata to true).tokenTypes.excludeMetadata.10 credits per API call
\nGet information about blocks (when they were added, how many NFTs and events were ingested and list of transaction hashes that were processed within them) on the following blockchains:
\nTo get started, provide a chain and specify one of the filters listed below (combination of these filters is not allowed):
\n10 credits per API call
\nGet all NFTs (ERC-721 and ERC-1155) and multitokens (ERC-1155 only) of your favorite collections! Our API lets you search for all tokens on:
\nTo get started:
\nexcludeMetadata to true).tokenType.excludeMetadata and tokenType won't have any effect on filtering data.20 credits per API call
\nGet all events on given addresses and / or in the requested block range on the following blockchains:
\nTo get started:
\nAs noted above, aside from general info and hashed event data, the API also decodes them for you in case you filter by one of the following supported event types:
\ntokenTransfer: All transfers of fungible tokens (including stablecoins) and NFTs as per ERC-20 and ERC-721 standard.multitokenTransfer: All transfers of multitokens (both single transfers and batch transfers) as per ERC-1155 standard.stablecoinTransfer: Refers to the transfer of specific stablecoins on the mainnet. Typically, the top 10 to 16 stablecoins on each chain according to CoinMarketCap are included. If the contractAddresses parameter is also used in the filter combination, any tokens specified in it will also be included in the list.uniswapTrade: Provides all swap events that occur on both Uniswap V2 and V3. In some cases, it may not be possible to map the swapped amounts to specific tokens. As a result, certain decoded data such as token amounts might be missing or in the original big number format. This will be indicated by the response parameter partiallyRaw: true.1 credit per API call
\nGet information about latest added block on the following blockchains:
\nTo get started, you can just provide a chain.
" -category: 65e9ba6715ec3b004bc82075 -hidden: false -createdAt: "Mon Feb 05 2024 13:24:49 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 13:24:50 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain Data/data-api-old/getmetadataold.md b/v1.0/Blockchain Data/data-api-old/getmetadataold.md deleted file mode 100644 index aa057e7b..00000000 --- a/v1.0/Blockchain Data/data-api-old/getmetadataold.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get token metadata" -slug: "getmetadataold" -excerpt: "5 credits per API call
\nGet metadata of NFTs (ERC-721 and ERC-1155) or multitokens (ERC-1155 only) by IDs for a given token address! Our API lets you search for all tokens on:
\nTo get started:
\n20 credits per API call
\nGet all addresses that own your favorite token (ERC-20, ERC-721 or ERC-1155)! Our API lets you search for all token owners on:
\nTo get started:
\ntokenId. In case of multitoken, result is an array of addresses.1 credit per API call
\nGet information about your favorite token! Our API lets you search for all tokens on:
\nTo get started:
\ntokenId as a query parameter.5 credits per API call
\nGet transactions by hash on the following blockchains:
\nTo get started:
\n20 credits per API call
\nGet transactions on the following blockchains:
\nTo get started:
\ntransactionTypes and even transactionSubtype (incoming, outgoing, zero-transfer).addresses query parameter. Following query parameters won't have any effect on filtering data: transactionTypes, transactionSubtype, tokenId, blockTo.pageSize and offset query parameters. \ncursor query parameter, by filling in the value from prevPage or nextPage field in the response body.100 credits per API call
\nGet unspent UTXOs for a specific address up to a specific total amount.\nIf you want to prepare a transaction on UTXO-based chains like Bitcoin, you need to enter unspent UTXOs to be able to perform a transaction. By providing ```totalValue``` as a total, our API will return a list of UTXOs that will be enough to cover the transaction.
\nOur API lets you get the unpenst UTXOs for a specific address on:\nTo get started:
\n10 credits per API call
\nGet information about blocks (when they were added, how many NFTs and events were ingested and list of transaction hashes that were processed within them) on the following blockchains:
\nTo get started, provide a chain and specify one of the filters listed below (combination of these filters is not allowed):
\n20 credits per API call
\nGet all events on given addresses and / or in the requested block range on the following blockchains:
\nTo get started:
\nAs noted above, aside from general info and hashed event data, the API also decodes them for you in case you filter by one of the following supported event types:
\ntokenTransfer: All transfers of fungible tokens (including stablecoins) and NFTs as per ERC-20 and ERC-721 standard.multitokenTransfer: All transfers of multitokens (both single transfers and batch transfers) as per ERC-1155 standard.stablecoinTransfer: Refers to the transfer of specific stablecoins on the mainnet. Typically, the top 10 to 16 stablecoins on each chain according to CoinMarketCap are included. If the contractAddresses parameter is also used in the filter combination, any tokens specified in it will also be included in the list.uniswapTrade: Provides all swap events that occur on both Uniswap V2 and V3. In some cases, it may not be possible to map the swapped amounts to specific tokens. As a result, certain decoded data such as token amounts might be missing or in the original big number format. This will be indicated by the response parameter partiallyRaw: true.1 credit per API call
\nGet information about latest added block on the following blockchains:
\nTo get started, you can just provide a chain.
" -category: 65e9ba6715ec3b004bc82075 -hidden: false -createdAt: "Mon Feb 05 2024 11:31:36 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 13:24:50 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain Data/insights.md b/v1.0/Blockchain Data/insights.md deleted file mode 100644 index cc46d72b..00000000 --- a/v1.0/Blockchain Data/insights.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Indexed Data Insights" -slug: "insights" -excerpt: "" -category: 65e9ba6715ec3b004bc82075 -hidden: true -createdAt: "Thu Mar 07 2024 13:24:26 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Tue Mar 19 2024 13:22:32 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain Data/insights/fungible-tokens-data.md b/v1.0/Blockchain Data/insights/fungible-tokens-data.md deleted file mode 100644 index ad8de5fe..00000000 --- a/v1.0/Blockchain Data/insights/fungible-tokens-data.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Fungible Tokens Data" -slug: "fungible-tokens-data" -excerpt: "" -category: 65e9ba6715ec3b004bc82075 -hidden: true -createdAt: "Thu Mar 07 2024 13:27:05 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Tue Mar 19 2024 13:22:32 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain Data/insights/nfts-2.md b/v1.0/Blockchain Data/insights/nfts-2.md deleted file mode 100644 index 46fd9cc2..00000000 --- a/v1.0/Blockchain Data/insights/nfts-2.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "NFT's" -slug: "nfts-2" -excerpt: "" -category: 65e9ba6715ec3b004bc82075 -hidden: true -createdAt: "Thu Mar 07 2024 13:25:03 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Tue Mar 19 2024 13:22:32 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain Data/insights/nfts-2/algorand-nft-mint-and-transfer-to-recipient-copy.md b/v1.0/Blockchain Data/insights/nfts-2/algorand-nft-mint-and-transfer-to-recipient-copy.md deleted file mode 100644 index c2aeb5f1..00000000 --- a/v1.0/Blockchain Data/insights/nfts-2/algorand-nft-mint-and-transfer-to-recipient-copy.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -title: "Solana - NFT Mint and Transfer to Recipient" -slug: "algorand-nft-mint-and-transfer-to-recipient-copy" -excerpt: "" -category: 65e9ba6715ec3b004bc82075 -hidden: true -createdAt: "Sun Feb 25 2024 12:03:56 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Tue Mar 19 2024 13:22:32 GMT+0000 (Coordinated Universal Time)" ---- -NFTs over Solana work a bit differently than other EVM (like Ethereum) chains. - -With most EVM chains, you need to deploy a smart contract from which you will mint NFTs. However, Solana uses the [Metaplex Protocol](https://www.metaplex.com/) — a smart contract and metadata standard for creating and working with NFTs. Tatum’s API endpoints leverage the Metaplex protocol, and as a result, you do not need to deploy your own smart contract to mint NFTs. - -Usually, the JSON metadata scheme that points to the metadata included in your NFT must be stored on IPFS. However, on Solana, this metadata is stored on the blockchain itself, so you do not need to create a JSON metadata scheme and upload it to IPFS. All you need to do is include a URL that points to the metadata in the uri field of the Mint NFT API call below. - -## NFT Mint Example - Solana - -[v3 REST API endpoint](https://apidoc.tatum.io/tag/NFT-(ERC-721-or-compatible)#operation/NftMintErc721) where available Request Body Schema: - -- MintNftExpressSolana -- MintNftSolana -- MintNftSolana - -Most of the parameters are the same as other EVM chains. However, the royalty information in the metadata section has a couple of key differences: - -- The total percentage royalty of each transaction to be paid out to the creators is entered in the `sellerFeeBasisPoints` field of the Mint NFT endpoint. For example, if the `sellerFeeBasisPoints` value is “1000”, this means 10% of the purchase price of the NFT will be transferred to creators each time it is sold. To disable the royalty for the NFT completely, set `sellerFeeBasisPoints` to 0. -- The `share` field contains the different percentages of the total `sellerFeeBasisPoints` to be divided among the creators. If there are 2 creators, one with a `share` value of “30” and one with a share value of “70”, 30% and 70% of the total `sellerFeeBasisPoints` royalty will be paid to each respective creator. - -### Request Example: - -```json cURL -curl --location --request POST 'https://api.tatum.io/v3/nft/mint/' \ ---header 'x-api-key: {API_KEY}' \ ---header 'Content-Type: application/json' \ ---data-raw '{ - "from": "FykfMwA9WNShzPJbbb9DNXsfgDgS3XZzWiFgrVXfWoPJ", - "chain": "SOL", - "fromPrivateKey": "####", - "to": "FykfMwA9WNShzPJbbb9DNXsfgDgS3XZzWiFgrVXfWoPJ", - "metadata": { - "name": "Tatum API", - "symbol": "TAPI", - "sellerFeeBasisPoints": 10, - "uri": "ipfs://bafybeidi7xixphrxar6humruz4mn6ul7nzmres7j4triakpfabiezll4ti", - "creators": [ - { - "address": "FykfMwA9WNShzPJbbb9DNXsfgDgS3XZzWiFgrVXfWoPJ", - "verified": true, - "share": 100 - } - ] - } -}' -``` - -**Parameters:** - -| Name | Description | -| :------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| from | The address of the creator of the NFT from which the gas fees will be paid | -| chain | The blockchain on which the NFT is being minted (in this case, “SOL”) | -| fromPrivateKey | The private key of the address from which the NFT is being minted | -| to | The recipient address to which the NFT will be minted | -| metadata | The data included in the NFT, including the royalty payment information to each co-creator | -| name | The name of the NFT | -| symbol | The symbol of the NFT | -| sellerFeeBasisPoints | The total percentage of the sale price to be paid out to co-creators based on their individual share (see below) | -| uri | The location of the metadata (image, video file, audio file, etc.). Usually, metadata json schemes are stored on IPFS. However, on Solana, the metadata scheme is stored on the Solana blockchain itself. | -| creators | Information about each co-creator who will receive a percentage royalty share each time the NFT is sold address - the account address of the creator | -| verified | whether or not the account has been verified | -| share | the percentage share of the total `sellerFeeBasisPoints` percentage designated above to be paid out to each individual creator | - -### Response Example: - -```json cURL -{ - "txId": "5GAwhRcMR7h5Dx71KCQax4CAcCFA6FcrVE5fwNedq7wXDYS1qpZaGd4Bj2zh8dCUfAz7fqVSXhdZzXRigsNoTZsb", - "nftAddress": "7dQWANaodDyttJNz3seaXoAe6VA8cLpPV1bM4cPGuNhG", - "nftAccountAddress": "3z2bPwKzfTAFDKPNKTM4vvffBSDvcBvkuRJeME5iALs3" -} -``` - -**Parameters:** - -| Name | Description | -| :---------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| txId | The transaction ID. This ID can be used to get information about the transaction using the Get transaction endpoint or within the Solana Explorer. | -| nftAddress | The address of the NFT on the blockchain. This is the address that is used to transfer the NFT below in the contractAddress field of the Transfer NFT API endpoint. | -| nftAccountAddress | The address of the account that owns the NFT. This address is owned by the recipient address, and a new `nftAccountAddress` is created each time a new NFT is minted. The private key of the `nftAccountAddress` is the same as the private key of the account address it is owned by. Each time an NFT is transferred on Solana, a new `nftAccountAddress` is created to receive the token under the recipient’s account address. | - -## NFT Transfer Example - Solana - -The way the Solana blockchain works with minting and transferring NFTs uses `nftAccountAddresses`. For practical use of Tatum’s API, this makes very little difference, but it is important to know that for transferring NFTs, the `nftAddress` of the NFT is used, NOT the `nftAccountAddress`. - -### Request Example: - -```json cURL -curl --request POST \ - --url https://api.tatum.io/v3/nft/transaction \ - --header 'content-type: application/json' \ - --header 'x-api-key: {API_KEY}' \ - --data '{ - "chain": "SOL", - "from": "FykfMwA9WNShzPJbbb9DNXsfgDgS3XZzWiFgrVXfWoPJ", - "to": "FykfMwA9WNShzPJbbb9DNXsfgDgS3XZzWiFgrVXfWoPJ", - "contractAddress": "7dQWANaodDyttJNz3seaXoAe6VA8cLpPV1bM4cPGuNhG", - "fromPrivateKey": "####" -}' -``` - -**Parameters:** - -| Name | Description | -| :-------------- | :-------------------------------------------------------------------------------------------------------- | -| chain | The chain on which you are transferring the NFT (in this case, “SOL”) from - the sender’s account address | -| to | The recipient’s account address | -| ContractAddress | The address of the NFT from the nftAddress field in the response to the Mint NFT call above. | -| fromPrivateKey | The private key of the sender’s address | - -### Response Example: - -```json cURL -{ - "txId": "c83f8818db43d9ba4accfe454aa44fc33123d47a4f89d47b314d6748eb0e9bc9" -} -``` diff --git a/v1.0/Blockchain Data/insights/nfts-2/algorand-nft-mint-and-transfer-to-recipient.md b/v1.0/Blockchain Data/insights/nfts-2/algorand-nft-mint-and-transfer-to-recipient.md deleted file mode 100644 index dfe598d7..00000000 --- a/v1.0/Blockchain Data/insights/nfts-2/algorand-nft-mint-and-transfer-to-recipient.md +++ /dev/null @@ -1,95 +0,0 @@ ---- -title: "Algorand - NFT Mint and Transfer to Recipient" -slug: "algorand-nft-mint-and-transfer-to-recipient" -excerpt: "" -category: 65e9ba6715ec3b004bc82075 -hidden: true -createdAt: "Sun Feb 25 2024 10:40:19 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Tue Mar 19 2024 13:22:32 GMT+0000 (Coordinated Universal Time)" ---- -NFTs over Algorand work a bit differently than other EVM (like Ethereum) chains. - -Algorand charges users for storing NFTs on their addresses and an Algorand blockchain address by default does not receive NFTs unless the owner of the address explicitly agrees to receive an NFT. - -### NFT Mint Example - Algorand - -[v3 REST API endpoint](https://apidoc.tatum.io/tag/NFT-(ERC-721-or-compatible)#operation/NftMintErc721) where available Request Body Schema: - -- MintNftExpressAlgorand -- MintNftAlgorand -- MintNftAlgorandKMS - -In the following example, the `privatekey` and `contractaddress` are default set to Tatum’s pre-deployed smart contract with Tatum's private key. The gas fees are deducted as credits from the monthly credit allowance from the paid Tatum plan. - -```json cURL -curl -i -X POST \ - https://api.tatum.io/v3/nft/mint \ - -H 'Content-Type: application/json' \ - -H 'x-api-key: {API_KEY}' \ - -d '{ - "chain": "ALGO", - "url": "https://my_token_data.com", - "name": "My Crazy NFT", - "attr": { - "assetUnit": "USDT", - "clawback": "TMETT6BXL3QUH7AH5TS6IONU7LVTLKIGG54CFCNPMQXWGRIZFIESZBYWP4", - "manager": "TMETT6BXL3QUH7AH5TS6IONU7LVTLKIGG54CFCNPMQXWGRIZFIESZBYWP4", - "reserve": "TMETT6BXL3QUH7AH5TS6IONU7LVTLKIGG54CFCNPMQXWGRIZFIESZBYWP4", - "freeze": "TMETT6BXL3QUH7AH5TS6IONU7LVTLKIGG54CFCNPMQXWGRIZFIESZBYWP4" - } - }' -``` - -### Parameters - -| Name | Description | -| :-------- | :---------------------------------------------------------------------------------------------------------------------- | -| chain | ALGO for Algorand in this specific case. | -| url | Metadata of the minted NFT. For details, see [the Ethereum site](https://eips.ethereum.org/EIPS/eip-721#specification). | -| name | The name of the minted NFT. | -| attr | Attributes | -| assetUnit | The name of the minted NFT unit. | -| clawback | The address of the clawback account. | -| manager | The address of the reserve account. | -| freeze | The address of the freeze account. | - -## NFT Transfer Example - Algorand - -An NFT that you mint on Algorand is automatically transferred to your blockchain address. After the NFT is minted, you have to transfer it to the recipient's address. - -The recipient has to agree in advance to receive your NFT (by default, Algorand charges users for storing NFTs on their addresses which, by default, does not receive NFTs unless agreed). - -### Step_1 - The recipient agrees with the NFT reception - -The recipient [agrees to receive the NFT](https://apidoc.tatum.io/tag/Algorand/#operation/AlgorandBlockchainReceiveAsset). **Recipient** enables accepting assets on an Algorand address using the mintNftExpressAlgorand schema: - -**Request Example**: - -```json cURL -curl -i -X POST \ - https://api.tatum.io/v3/algorand/asset/receive \ - -H 'Content-Type: application/json' \ - -H 'x-api-key: {API_KEY}' \ - -d '{ - "assetId": "116363571", //The NFT the recipient must agree to recieve. - "fromPrivateKey": "####" - }' -``` - -### Step_2 - The sender sends the NFT to the recipient - - You [transfer the NFT](https://preview.redoc.ly/tatum/develop/tag/NFT-(ERC-721-or-compatible)/#operation/NftTransferErc721) to the recipient's address using the `transferNftAlgoExpress` schema: - -**Request Example:** - -```json cURL -curl -i -X POST \ - https://api.tatum.io/v3/nft/transaction \ - -H 'Content-Type: application/json' \ - -H 'x-api-key: {API_KEY}' \ - -d '{ - "chain": "ALGO", - "to": "TMETT6BXL3QUH7AH5TS6IONU7LVTLKIGG54CFCNPMQXWGRIZFIESZBYWP4", - "contractAddress": "100000" - }' -``` diff --git a/v1.0/Blockchain Data/insights/nfts-2/nft-creating-your-own-collection.md b/v1.0/Blockchain Data/insights/nfts-2/nft-creating-your-own-collection.md deleted file mode 100644 index 9a3667d0..00000000 --- a/v1.0/Blockchain Data/insights/nfts-2/nft-creating-your-own-collection.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: "Creating a NFT Collection" -slug: "nft-creating-your-own-collection" -excerpt: "" -category: 65e9ba6715ec3b004bc82075 -hidden: true -createdAt: "Sat Feb 17 2024 13:34:32 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Tue Mar 19 2024 13:22:32 GMT+0000 (Coordinated Universal Time)" ---- -To mint an NFT, first you need a Collection to which said NFT must belong. To create your own NFT Collection, you have to deploy your own SmartContract. Tatum makes these steps easy. - -## Creating an NFT Collection - -1. Select the network you want the NFTs to exist. -2. Have ready an address with its `privatekey` with native assets. Required to pay for the SmartContract deployment. -3. Pick on a "`name`" and "`symbol`" for your collection. -4. Deploy the NFT SmartContract to get your Collection. -5. (Optional) Add a Tatum minter address - 1. If a Minter address is added to the Collection SmartContract, Tatum pays on your behalf. _Your account will be charged accordingly._ - -### Example request to create a new NFT Collection (CELO Testnet) - -**Step_1:** Deploy the NFT SmartContract to create a collection - -- v3 REST API endpoint - [Deploy an NFT Smart Contract](https://apidoc.tatum.io/tag/NFT-(ERC-721-or-compatible)#operation/NftDeployErc721) - -```json cURL -curl --location --request POST 'https://api.tatum.io/v3/nft/deploy' \ ---header 'x-api-key: {API_KEY}' \ ---header 'Content-Type: application/json' \ ---data-raw '{ - "chain": "CELO", - "name": "NFT on Celo Test Collection", - "symbol": "NCTC", - "fromPrivateKey": "####", - "feeCurrency": "CELO" -}' - -//Response -{ - "txId": "0xa3ed3b9d2686dad28e93bbad6df37fc38430ecd8c0b49aceef787d33a9a6edcd" -} -``` - -> 📘 Find the transaction in [Celo Alfajores Explorer](https://explorer.celo.org/alfajores/tx/0xa3ed3b9d2686dad28e93bbad6df37fc38430ecd8c0b49aceef787d33a9a6edcd). - -**Step_2:** Retrieve the "SmartContract - address" - -- v3 REST API endpoint - [Get the SC from a transaction hash](https://apidoc.tatum.io/tag/Blockchain-utils#operation/SCGetContractAddress) - -```json cURL -curl --location --request GET 'https://api.tatum.io/v3/blockchain/sc/address/CELO/0xa6e0f4f1571dd5f50af126f173f0ff62ee8dd9d9aa7d708843c4b8058d347be5' \ ---header 'x-api-key: {API_KEY}' -//Response -{ - "contractAddress": "0x0935a78C8a268c8ED0590E5A8d4409f7604Bed1A" -} -``` - -**Step_3:** (optional) Adding Tatum as a Minter - -- v3 REST API endpoint - [Add an address as Minter](https://apidoc.tatum.io/tag/NFT-(ERC-721-or-compatible)#operation/NftAddMinter) - -```json cURL -curl --location --request POST 'https://api.tatum.io/v3/nft/mint/add' \ ---header 'x-api-key: {API_KEY}' \ ---header 'Content-Type: application/json' \ ---data-raw '{ - "chain": "CELO", - "contractAddress": "0x0935a78C8a268c8ED0590E5A8d4409f7604Bed1A", - "minter": "0xBC2eBA680EE50d685cc4Fe65f102AA70AfB27D3F", - "fromPrivateKey": "#####" -}' -//Response -{ - "txId": "0x04e159bd515c917efcfbb88f819b513fb7c5d54aef70c26aaa285e7b987c1aae" -} -``` - -### Tatum Minter role addresses - -| Environment | Chain | Address | -| :---------- | :-------------------------------------------- | :--------------------------------------------- | -| **Mainnet** | BSC, Celo, Ethereum, Harmony, Klaytn, Polygon | **0x49678AAB11E001eb3cB2cBD9aA96b36DC2461A94** | -| Testnet | BSC | 0xc16ae5e8c985b906935a0cadf4e24f0400531883 | -| Testnet | Celo | 0xBC2eBA680EE50d685cc4Fe65f102AA70AfB27D3F | -| Testnet | Ethereum | 0x53e8577C4347C365E4e0DA5B57A589cB6f2AB848 | -| Testnet | Harmony | 0x8906f62d40293ddca77fdf6714c3f63265deddf0 | -| Testnet | Polygon | 0x542b9ac4945a3836fd12ad98acbc76a0c8b743f5 | - -> 📘 Adding a Minter Address into an NFT Collection SmartContract is non-reversible. The cost of each use in crypto is charged to the account in credits. diff --git a/v1.0/Blockchain Data/insights/nfts-2/nft-minting-nfts.md b/v1.0/Blockchain Data/insights/nfts-2/nft-minting-nfts.md deleted file mode 100644 index 6635c715..00000000 --- a/v1.0/Blockchain Data/insights/nfts-2/nft-minting-nfts.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -title: "Minting NFTs" -slug: "nft-minting-nfts" -excerpt: "" -category: 65e9ba6715ec3b004bc82075 -hidden: true -createdAt: "Sat Feb 17 2024 14:17:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Tue Mar 19 2024 13:22:32 GMT+0000 (Coordinated Universal Time)" ---- -To mint an NFT, first you need a Collection to which said NFT must belong. Once you have the Collection SmartContract, minting NFTs just takes a few steps. - -## Minting an NFT - -1. Select the network you want the NFTs to exist. -2. Have ready a Collection (SmartContract) for your NFT to belong. -3. Have ready an address with its `privatekey` with native assets. Required to pay for the minting. - 1. If a Minter address was added to the Collection SmartContract, Tatum pays on your behalf. _Your account will be charged accordingly._ -4. Get ready the metadata JSON file. -5. Mint the NFT. - -### Example request to mint an NFT (CELO Testnet) - -**Step_1:** Upload the Image and the Metadata JSON file - -- v3 REST API endpoint - [Store data to IPFS](https://apidoc.tatum.io/tag/IPFS#operation/StoreIPFS) - -```json cURL -//First upload the NFT image -curl --location --request POST 'https://api.tatum.io/v3/ipfs' \ ---header 'x-api-key: {API_KEY}' \ ---form 'file=@"/Users/{username}/Documents/tatum_nft_example.jpeg"' -//Response -{ - "ipfsHash": "bafkreif6ifegpj74w6biowzzbswqwvg6c5t6hhtwsrmpxhweg6yn7zxm7e" -} - -//After that, create a JSON file and upload this new file -//File format: -// { -// "name": "Tatum NFT for Diagram example", -// "description": "This is an NFT minted as an example.", -// "image": "ipfs://bafkreif6ifegpj74w6biowzzbswqwvg6c5t6hhtwsrmpxhweg6yn7zxm7e" -// } - -curl --location --request POST 'https://api.tatum.io/v3/ipfs' \ ---header 'x-api-key: {API_KEY}' \ ---form 'file=@"/Users/{username}/Documents/Tatum_NFT_example.json"' -//Response -{ - "ipfsHash": "bafkreiebg3ugqtumak2ueyf2j2sbggt47hxjvbozkxbgyssebufmbgp3fa" -} -``` - -**Step_2:** Mint the NFT - -- v3 REST API endpoint - [Mint an NFT](https://apidoc.tatum.io/tag/NFT-(ERC-721-or-compatible)#operation/NftMintErc721) - -```json cURL -curl --location --request POST 'https://api.tatum.io/v3/nft/mint/' \ ---header 'x-api-key: {API_KEY}' \ ---header 'Content-Type: application/json' \ ---data-raw '{ -"chain": "CELO", -"tokenId": "001", -"to": "0x40245fa66666508e4121f4400819eef4b08ac4bf", -"url": "ipfs://bafkreiebg3ugqtumak2ueyf2j2sbggt47hxjvbozkxbgyssebufmbgp3fa", -"contractAddress": "0x0935a78C8a268c8ED0590E5A8d4409f7604Bed1A", -"minter": "0xBC2eBA680EE50d685cc4Fe65f102AA70AfB27D3F", // If there's no "minter", PrivateKey must be used instead. -"feeCurrency": "CELO" -}' -//Resonse -{ - "txId": "0xd16536eea02ddffd2deee2db5e2c053ee429526758420477781082c7a5465aa7" -} -``` - -### Parameters - -| Name | Description | -| :-------------- | :------------------------------------------------------------------------------------------ | -| chain | The network on which the NFT will be minted. | -| contractAddress | The address of your NFT Collection/SmartContract. | -| minter | The address of the Tatum NFT minter that you have added as a minter to your smart contract. | -| to | The blockchain address of the recipient to whom the NFT will be sent. | -| tokenId | The identifier of the NTF that will be minted. | -| url | The URL of the metadata (image, audio, video, etc) to be included in the NFT. | - -> 📘 Find the transaction in [Celo Alfajores Explorer](https://explorer.celo.org/alfajores/tx/0xd16536eea02ddffd2deee2db5e2c053ee429526758420477781082c7a5465aa7). - -### Tatum Minter role addresses - -| Environment | Chain | Address | -| :---------- | :-------------------------------------------- | :--------------------------------------------- | -| **Mainnet** | BSC, Celo, Ethereum, Harmony, Klaytn, Polygon | **0x49678AAB11E001eb3cB2cBD9aA96b36DC2461A94** | -| Testnet | BSC | 0xc16ae5e8c985b906935a0cadf4e24f0400531883 | -| Testnet | Celo | 0xBC2eBA680EE50d685cc4Fe65f102AA70AfB27D3F | -| Testnet | Ethereum | 0x53e8577C4347C365E4e0DA5B57A589cB6f2AB848 | -| Testnet | Harmony | 0x8906f62d40293ddca77fdf6714c3f63265deddf0 | -| Testnet | Polygon | 0x542b9ac4945a3836fd12ad98acbc76a0c8b743f5 | diff --git a/v1.0/Blockchain Data/insights/wallet-data.md b/v1.0/Blockchain Data/insights/wallet-data.md deleted file mode 100644 index e0bd61ea..00000000 --- a/v1.0/Blockchain Data/insights/wallet-data.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Wallet Address Data" -slug: "wallet-data" -excerpt: "" -category: 65e9ba6715ec3b004bc82075 -hidden: true -createdAt: "Thu Mar 07 2024 13:27:12 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Tue Mar 19 2024 13:22:32 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain Data/nft-api.md b/v1.0/Blockchain Data/nft-api.md deleted file mode 100644 index f86ad9a3..00000000 --- a/v1.0/Blockchain Data/nft-api.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: "NFT API" -slug: "nft-api" -excerpt: "NFT API is a sub product of Blockchain Data that aims to help you get any NFT related on-chain data you would need to add NFT functionality in your web3 app." -category: 65e9ba6715ec3b004bc82075 -hidden: false -createdAt: "Mon Feb 05 2024 11:31:36 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 12 2024 11:47:59 GMT+0000 (Coordinated Universal Time)" ---- -# List of Features Available - -| Feature | Description | Supported Mainnets | Supported Testnets | -| :------------------------------- | :------------------------------------------------------------------------ | :---------------------------------------------------- | :-------------------------------------------- | -| **Get Tokens From a Collection** | Fetch all tokens from an NFT Collection or MultiToken Collection | Ethereum, Celo, BSC, Polygon, Horizen, Chilliz, Tezos | Ethereum Sepolia, BSC-Testnet, Polygon-Mumbai | -| **Get Tokens Metadata** | Fetch metadata about an NFT or a MultiToken | Ethereum, Celo, BSC, Polygon, Horizen, Chilliz | Ethereum Sepolia, BSC-Testnet, Polygon-Mumbai | -| **Get Owners of a Token** | Find all the owners of Fungible Tokens, NFTs or Multitokens | Ethereum, Celo, BSC, Polygon, Horizen, Chilliz | Ethereum Sepolia, BSC-Testnet, Polygon-Mumbai | -| **Check ownership for a Token** | Check if a wallet owns a specific Fungible Token, or NFT or a MultiToken. | Ethereum, Celo, BSC, Polygon, Horizen, Chilliz | Ethereum Sepolia, BSC-Testnet, Polygon-Mumbai | - -[block:html]{"html":"Don't have an API key?\n
Get one to start using Blockchain Data in your app today.
\n Get started for free\n1 credit per API call
\nCheck if wallet address owns any specified token (ERC-20, ERC-721 or ERC-1155) on the following blockchains:
\nTo get started:
\ntrue if provided wallet address owns them.false and status code is 200.tokenId.10 credits per API call
\nGet all NFTs (ERC-721 and ERC-1155) and multitokens (ERC-1155 only) of your favorite collections! Our API lets you search for all tokens on:
\nTo get started:
\nexcludeMetadata to true).tokenType.excludeMetadata and tokenType won't have any effect on filtering data.5 credits per API call
\nGet metadata of NFTs (ERC-721 and ERC-1155) or multitokens (ERC-1155 only) by IDs for a given token address! Our API lets you search for all tokens on:
\nTo get started:
\n20 credits per API call
\nGet all addresses that own your favorite token (ERC-20, ERC-721 or ERC-1155)! Our API lets you search for all token owners on:
\nTo get started:
\ntokenId. In case of multitoken, result is an array of addresses.Don't have an API key?\n
Get one to start using Blockchain Data in your app today.
\n Get started for free\n1 credit per API call
\nGet information about your favorite token! Our API lets you search for all tokens on:
\nTo get started:
\ntokenId as a query parameter.10 credits per API call
\nEstimate the current fee for different types of transactions.
\nThis API is supported for the following blockchains:
\n1 credit per API call
\nGet the recommended fee/gas price for a blockchain.
\nFee is in satoshis(meaning currency(BTC, DOGE,... / 100 000 000) per byte\n
This API is supported for the following blockchains:
\n20 credits per API call
\nGet transactions on the following blockchains:
\nTo get started:
\ntransactionTypes and even transactionSubtype (incoming, outgoing, zero-transfer).addresses query parameter. Following query parameters won't have any effect on filtering data: transactionTypes, transactionSubtype, tokenId, blockTo.pageSize and offset query parameters. \ncursor query parameter, by filling in the value from prevPage or nextPage field in the response body.5 credits per API call
\nGet transactions by hash on the following blockchains:
\nTo get started:
\n50 credits per API call
\nGet balances of fungible tokens (ERC-20), NFTs (ERC-721 and ERC-1155) or multitokens (ERC-1155 only) for a specific wallet address on the following blockchains:
\nTo get started:
\nexcludeMetadata to true).tokenTypes.excludeMetadata.100 credits per API call
\nGet unspent UTXOs for a specific address up to a specific total amount.\nIf you want to prepare a transaction on UTXO-based chains like Bitcoin, you need to enter unspent UTXOs to be able to perform a transaction. By providing ```totalValue``` as a total, our API will return a list of UTXOs that will be enough to cover the transaction.
\nOur API lets you get the unpenst UTXOs for a specific address on:\nTo get started:
\nThe number of credits consumed depends on the number of methods submitted in an API call:
\n* 50 credits per debug*/trace* method (for EVM-based blockchains)
\n* 50 credits per EOS Trace API methods
\n* 5 credits per eth_call method (for EVM-based blockchains)
\n* 2 credits per any other RPC method
Connect directly to the blockchain node provided by Tatum.
\nThe POST method is used. The API endpoint URL acts as an HTTP-based RPC driver.
In the request body, provide valid Web3 RPC method content, for example:
\n\n{\n \"jsonrpc\": \"2.0\",\n \"id\": 1,\n \"method\": \"method_name\",\n \"params\": []\n}\n\nFor the blockchains using the JSON-RPC 2.0 specification, you can submit multiple RPC methods in one API call:
\n\n[\n {\n \"jsonrpc\": \"2.0\",\n \"id\": 1,\n \"method\": \"method_1_name\",\n \"params\": []\n },\n {\n \"jsonrpc\": \"2.0\",\n \"id\": 2,\n \"method\": \"method_2_name\",\n \"params\": []\n },\n ...\n]\n\nThis API is supported for the following blockchains:
\n2 credits per RPC method in an API call
\nConnect directly to the blockchain node provided by Tatum.
\nThe GET method is used. The API endpoint URL acts as an HTTP-based RPC driver.
This API is supported for the following blockchains:
\n" -category: 65c0c794d329e30077a0638c -hidden: false -createdAt: "Mon Feb 05 2024 11:33:42 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:33:42 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain Node RPC/node-rpc/nodejsonrpcputdriver.md b/v1.0/Blockchain Node RPC/node-rpc/nodejsonrpcputdriver.md deleted file mode 100644 index 156f3a4a..00000000 --- a/v1.0/Blockchain Node RPC/node-rpc/nodejsonrpcputdriver.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Connect to the blockchain node through an RPC driver" -slug: "nodejsonrpcputdriver" -excerpt: "2 credits per RPC method in an API call
\nConnect directly to the blockchain node provided by Tatum.
\nThe PUT method is used. The API endpoint URL acts as an HTTP-based RPC driver.
In the request body, provide valid Web3 RPC method content, for example:
\n\n{\n \"jsonrpc\": \"2.0\",\n \"id\": 1,\n \"method\": \"method_name\",\n \"params\": []\n}\n\nFor the blockchains using the JSON-RPC 2.0 specification, you can submit multiple RPC methods in one API call:
\n\n[\n {\n \"jsonrpc\": \"2.0\",\n \"id\": 1,\n \"method\": \"method_1_name\",\n \"params\": []\n },\n {\n \"jsonrpc\": \"2.0\",\n \"id\": 2,\n \"method\": \"method_2_name\",\n \"params\": []\n },\n ...\n]\n\nThis API is supported for the following blockchains:
\n1 credit per API call
\nThis endpoint is deprecated. Use the HTTP-based JSON RPC driver instead.
Use this endpoint URL as a http-based url to connect directly to the Algorand node provided by Tatum.\nYou can check al available APIs here - https://developer.algorand.org/docs/rest-apis/algod/v2/.\n
\nExample call for Get Block is described in the response. https://developer.algorand.org/docs/rest-apis/algod/v2/#get-v2blocksround.\n
\nURL used for this call would be
https://api.tatum.io/v3/algorand/node/algod/YOUR_API_KEY/v2/blocks/16775567\n" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/algorand/algonodeindexergetdriver.md b/v1.0/Blockchain/algorand/algonodeindexergetdriver.md deleted file mode 100644 index b2d75581..00000000 --- a/v1.0/Blockchain/algorand/algonodeindexergetdriver.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Access Algorand Indexer GET node endpoints" -slug: "algonodeindexergetdriver" -excerpt: "
1 credit per API call
\nThis endpoint is deprecated. Use the HTTP-based JSON RPC driver instead.
Use this endpoint URL as a http-based url to connect directly to the Algorand node provided by Tatum.\nYou can check all available APIs here - https://developer.algorand.org/docs/rest-apis/indexer/.\n
\nExample call for Get Tx By ID is described in the response. https://developer.algorand.org/docs/rest-apis/indexer/#get-v2transactionstxid.\n
\nURL used for this call would be
https://api.tatum.io/v3/algorand/node/indexer/YOUR_API_KEY/v2/transactions/HNIQ76UTJYPOLZP5FWODYABBJPYPGJNEM2QEJSMDMQRWEKHEYJHQ" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:02 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/algorand/algonodepostdriver.md b/v1.0/Blockchain/algorand/algonodepostdriver.md deleted file mode 100644 index 4f15c517..00000000 --- a/v1.0/Blockchain/algorand/algonodepostdriver.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Access Algorand Algod POST node endpoints" -slug: "algonodepostdriver" -excerpt: "
2 credits per API call
\nThis endpoint is deprecated. Use the HTTP-based JSON RPC driver instead.
Use this endpoint URL as a http-based url to connect directly to the Algorand node provided by Tatum.\n You can check al available APIs here - https://developer.algorand.org/docs/rest-apis/algod/v2/.\n
\n Example call for Broadcast a raw transaction is described in the response. https://developer.algorand.org/docs/rest-apis/algod/v2/#post-v2transactions.\n
\n URL used for this call would be
https://api.tatum.io/v3/algorand/node/algod/YOUR_API_KEY/v2/transactions\n " -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:02 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/algorand/algorandblockchainreceiveasset.md b/v1.0/Blockchain/algorand/algorandblockchainreceiveasset.md deleted file mode 100644 index 5cd8c16b..00000000 --- a/v1.0/Blockchain/algorand/algorandblockchainreceiveasset.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Enable receiving asset on account" -slug: "algorandblockchainreceiveasset" -excerpt: "
Enable accepting Algorand asset on the sender account.
\nThis operation needs the private key of the blockchain address.\nNo 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\nor signatureId. PrivateKey should be used only for quick development on testnet versions of blockchain when there is no risk of losing funds. In production,\nTatum KMS should be used for the highest security standards, and signatureId should be present in the request.\nAlternatively, using the Tatum client library for supported languages.\n
2 credits per API call
\nSend Algos from one Algorand address to the other one.
\nSigning a transaction
\nWhen sending Algos, 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.
\nProviding 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.
\nFor 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.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/algorand/algorandbroadcast.md b/v1.0/Blockchain/algorand/algorandbroadcast.md deleted file mode 100644 index 0db097b9..00000000 --- a/v1.0/Blockchain/algorand/algorandbroadcast.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Broadcast signed Algorand transaction" -slug: "algorandbroadcast" -excerpt: "Broadcast signed transaction to Algorand blockchain. This method is used internally from Tatum KMS or Tatum client libraries.\nIt is possible to create custom signing mechanism and use this method only for broadcasting data to the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:03 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/algorand/algorandgenerateaddress.md b/v1.0/Blockchain/algorand/algorandgenerateaddress.md deleted file mode 100644 index aa293f56..00000000 --- a/v1.0/Blockchain/algorand/algorandgenerateaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Algorand account address from private key" -slug: "algorandgenerateaddress" -excerpt: "Generate Algorand account deposit address from private key.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:02 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/algorand/algorandgeneratewallet.md b/v1.0/Blockchain/algorand/algorandgeneratewallet.md deleted file mode 100644 index 8853e27a..00000000 --- a/v1.0/Blockchain/algorand/algorandgeneratewallet.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Algorand wallet" -slug: "algorandgeneratewallet" -excerpt: "Tatum supports Algorand wallets.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/algorand/algorandgetbalance.md b/v1.0/Blockchain/algorand/algorandgetbalance.md deleted file mode 100644 index 0ab58448..00000000 --- a/v1.0/Blockchain/algorand/algorandgetbalance.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Algorand Account balance" -slug: "algorandgetbalance" -excerpt: "Get Algorand account balance in ALGO.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:02 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/algorand/algorandgetblock.md b/v1.0/Blockchain/algorand/algorandgetblock.md deleted file mode 100644 index dee4ca06..00000000 --- a/v1.0/Blockchain/algorand/algorandgetblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Algorand block by block round number" -slug: "algorandgetblock" -excerpt: "Get Algorand block by block round number.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:02 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/algorand/algorandgetcurrentblock.md b/v1.0/Blockchain/algorand/algorandgetcurrentblock.md deleted file mode 100644 index 427c516d..00000000 --- a/v1.0/Blockchain/algorand/algorandgetcurrentblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get current block number" -slug: "algorandgetcurrentblock" -excerpt: "Get Algorand current block number. This is the number of the latest block in the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/algorand/algorandgetpaytransactionsbyfromto.md b/v1.0/Blockchain/algorand/algorandgetpaytransactionsbyfromto.md deleted file mode 100644 index c629843c..00000000 --- a/v1.0/Blockchain/algorand/algorandgetpaytransactionsbyfromto.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Algorand Transactions between from and to" -slug: "algorandgetpaytransactionsbyfromto" -excerpt: "1 credit per API call
\nThis endpoint is deprecated.
Get Algorand transaction by specified period of time.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/algorand/algorandgettransaction.md b/v1.0/Blockchain/algorand/algorandgettransaction.md deleted file mode 100644 index de5dc3b0..00000000 --- a/v1.0/Blockchain/algorand/algorandgettransaction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Algorand Transaction" -slug: "algorandgettransaction" -excerpt: "Get Algorand transaction by transaction id.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:03 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bitcoin-cash.md b/v1.0/Blockchain/bitcoin-cash.md deleted file mode 100644 index 45cdc45f..00000000 --- a/v1.0/Blockchain/bitcoin-cash.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Bitcoin Cash" -slug: "bitcoin-cash" -excerpt: "" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bitcoin-cash/bchbroadcast.md b/v1.0/Blockchain/bitcoin-cash/bchbroadcast.md deleted file mode 100644 index 0ffde73c..00000000 --- a/v1.0/Blockchain/bitcoin-cash/bchbroadcast.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Broadcast signed Bitcoin Cash transaction" -slug: "bchbroadcast" -excerpt: "Broadcast signed transaction to Bitcoin Cash blockchain. This method is used internally from Tatum KMS or Tatum client libraries.\nIt is possible to create custom signing mechanism and use this method only for broadcasting data to the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bitcoin-cash/bchgenerateaddress.md b/v1.0/Blockchain/bitcoin-cash/bchgenerateaddress.md deleted file mode 100644 index 8d955568..00000000 --- a/v1.0/Blockchain/bitcoin-cash/bchgenerateaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Bitcoin Cash deposit address from Extended public key" -slug: "bchgenerateaddress" -excerpt: "Generate Bitcoin Cash deposit address from Extended public key. Deposit address is generated for the specific index - each extended public key can generate\nup to 2^31 addresses starting from index 0 until 2^31 - 1. Generates new format of address starting with bitcoincash: in case of mainnet, bchtest: in case of testnet..
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bitcoin-cash/bchgenerateaddressprivatekey.md b/v1.0/Blockchain/bitcoin-cash/bchgenerateaddressprivatekey.md deleted file mode 100644 index a3aa7d11..00000000 --- a/v1.0/Blockchain/bitcoin-cash/bchgenerateaddressprivatekey.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Bitcoin Cash private key" -slug: "bchgenerateaddressprivatekey" -excerpt: "Generate private key for address from mnemonic for given derivation path index. Private key is generated for the specific index - each mnemonic\ncan generate up to 2^32 private keys starting from index 0 until 2^31 - 1.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bitcoin-cash/bchgeneratewallet.md b/v1.0/Blockchain/bitcoin-cash/bchgeneratewallet.md deleted file mode 100644 index f4ebe20b..00000000 --- a/v1.0/Blockchain/bitcoin-cash/bchgeneratewallet.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Bitcoin Cash wallet" -slug: "bchgeneratewallet" -excerpt: "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 Bitcoin Cash wallet with derivation path m'/44'/145'/0'/0. More about BIP44 HD wallets can be found here - https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki.\nGenerate BIP44 compatible Bitcoin Cash wallet.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bitcoin-cash/bchgetblock.md b/v1.0/Blockchain/bitcoin-cash/bchgetblock.md deleted file mode 100644 index f0135070..00000000 --- a/v1.0/Blockchain/bitcoin-cash/bchgetblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Bitcoin Cash Block by hash" -slug: "bchgetblock" -excerpt: "Get Bitcoin Cash Block detail by block hash or height.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:55 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bitcoin-cash/bchgetblockchaininfo.md b/v1.0/Blockchain/bitcoin-cash/bchgetblockchaininfo.md deleted file mode 100644 index 59fbd034..00000000 --- a/v1.0/Blockchain/bitcoin-cash/bchgetblockchaininfo.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Bitcoin Cash Blockchain Information" -slug: "bchgetblockchaininfo" -excerpt: "Get Bitcoin Cash Blockchain Information. Obtain basic info like testnet / mainnet version of the chain, current block number and it's hash.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bitcoin-cash/bchgetblockhash.md b/v1.0/Blockchain/bitcoin-cash/bchgetblockhash.md deleted file mode 100644 index 59111844..00000000 --- a/v1.0/Blockchain/bitcoin-cash/bchgetblockhash.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Bitcoin Cash Block hash" -slug: "bchgetblockhash" -excerpt: "Get Bitcoin Cash Block hash. Returns hash of the block to get the block detail.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:55 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bitcoin-cash/bchgetrawtransaction.md b/v1.0/Blockchain/bitcoin-cash/bchgetrawtransaction.md deleted file mode 100644 index 9c2dfd79..00000000 --- a/v1.0/Blockchain/bitcoin-cash/bchgetrawtransaction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Bitcoin Cash Transaction by hash" -slug: "bchgetrawtransaction" -excerpt: "Get Bitcoin Cash Transaction by transaction hash.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:55 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bitcoin-cash/bchgettxbyaddress.md b/v1.0/Blockchain/bitcoin-cash/bchgettxbyaddress.md deleted file mode 100644 index 619a99bd..00000000 --- a/v1.0/Blockchain/bitcoin-cash/bchgettxbyaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Bitcoin Cash Transactions by address" -slug: "bchgettxbyaddress" -excerpt: "Get Bitcoin Cash Transaction by address. Limit is 50 transaction per response.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:55 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bitcoin-cash/bchrpcdriver.md b/v1.0/Blockchain/bitcoin-cash/bchrpcdriver.md deleted file mode 100644 index 854ea928..00000000 --- a/v1.0/Blockchain/bitcoin-cash/bchrpcdriver.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "JSON RPC HTTP driver" -slug: "bchrpcdriver" -excerpt: "2 credits per API call
\nThis endpoint is deprecated. Use the HTTP-based JSON RPC driver instead.
Use this endpoint URL as an http-based JSON RPC driver to connect directly to the node provided by Tatum.\nTo learn more about JSON RPC, visit Bitcoin Cash developers' guide.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:54 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bitcoin-cash/bchtransferblockchain.md b/v1.0/Blockchain/bitcoin-cash/bchtransferblockchain.md deleted file mode 100644 index ae29e486..00000000 --- a/v1.0/Blockchain/bitcoin-cash/bchtransferblockchain.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send BCH to Bitcoin Cash addresses" -slug: "bchtransferblockchain" -excerpt: "10 credits per API call
\nSend BCH to blockchain addresses.
\nBitcoin Cash transactions are based on UTXOs. \"UTXO\" stands for \"Unspent Transaction Output\". A UTXO is the amount of BCH that remains at a Bitcoin Cash address after a cryptocurrency transaction involving this address has been performed. The UTXO can then be used as input for a new cryptocurrency transaction. For more information the UTXO, see the Bitcoin user documentation.
\nYou build a BCH transaction by sending BCH from UTXOs. Each UTXO is included in the transaction.
\nWhen an UTXO is entered into a transaction, the whole UTXO amount is included and must be spent. For example, address A receives two transactions, T1 with 1 BCH and T2 with 2 BCH. A transaction that consumes the UTXOs from both T1 and T2 will have an available amount of 3 BCH to spend:1 BCH (from T1) + 2 BCH (from T2) = 3 BCH (to spend in total)
You can send the assets to one or multiple recipients in one transaction. If you send the assets to multiple addresses, each address must have its own amount to receive.
\nPaying the gas fee and receiving the change
\nWhen the amount that the recipients should receive is lower than the amount from the UTXOs, the difference between these two amounts is by default used as the gas fee for the transaction. Because this amount may be considerable and you may not want to spend it all on the gas fee, you can explicitly specify the fee amount and the blockchain address where any extra funds remaining after covering the fee will be sent (the fee and changeAddress parameters in the request body, correspondingly).
Signing a transaction
\nWhen sending BCH, 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.
\nFor 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.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:55 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bitcoin.md b/v1.0/Blockchain/bitcoin.md deleted file mode 100644 index 756b80f4..00000000 --- a/v1.0/Blockchain/bitcoin.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Bitcoin" -slug: "bitcoin" -excerpt: "" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bitcoin/btcbroadcast.md b/v1.0/Blockchain/bitcoin/btcbroadcast.md deleted file mode 100644 index 7a2ff9ab..00000000 --- a/v1.0/Blockchain/bitcoin/btcbroadcast.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Broadcast a signed Bitcoin transaction" -slug: "btcbroadcast" -excerpt: "2 credits per API call
\nBroadcasts a signed transaction to the Bitcoin blockchain. This method is used internally from Tatum KMS or Tatum Client Libraries.\nIt is possible to create a custom signing mechanism and only use this method for broadcasting data to the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:53 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bitcoin/btcgenerateaddress.md b/v1.0/Blockchain/bitcoin/btcgenerateaddress.md deleted file mode 100644 index 9c1da16d..00000000 --- a/v1.0/Blockchain/bitcoin/btcgenerateaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate a Bitcoin address from the wallet's extended public key" -slug: "btcgenerateaddress" -excerpt: "1 credit per API call
\nGenerate a Bitcoin address from the extended public key of the wallet. The address is generated for the specific index - each extended public key can generate up to 2^32 addresses with the index starting from 0 up to 2^31 - 1.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bitcoin/btcgenerateaddressprivatekey.md b/v1.0/Blockchain/bitcoin/btcgenerateaddressprivatekey.md deleted file mode 100644 index 2c872372..00000000 --- a/v1.0/Blockchain/bitcoin/btcgenerateaddressprivatekey.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate the private key for a Bitcoin address" -slug: "btcgenerateaddressprivatekey" -excerpt: "1 credit per API call
\nGenerates a private key for an address from a mnemonic for a given derivation path index. The private key is generated for the specific index - each mnemonic can generate up to 2^32 private keys starting from index 0 until 2^31 - 1.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bitcoin/btcgeneratewallet.md b/v1.0/Blockchain/bitcoin/btcgeneratewallet.md deleted file mode 100644 index 3978170d..00000000 --- a/v1.0/Blockchain/bitcoin/btcgeneratewallet.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate a Bitcoin wallet" -slug: "btcgeneratewallet" -excerpt: "1 credit per API call
\nTatum supports BIP44 HD wallets. Because they can generate 2^31 addresses from 1 mnemonic phrase, they are very convenient and secure. A mnemonic phrase consists of 24 special words in a 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 Bitcoin wallet with derivation path m'/44'/0'/0'/0. More about BIP44 HD wallets can be found here - https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki.\nGenerate BIP44 compatible Bitcoin wallet.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bitcoin/btcgetbalanceofaddress.md b/v1.0/Blockchain/bitcoin/btcgetbalanceofaddress.md deleted file mode 100644 index 7b0d278c..00000000 --- a/v1.0/Blockchain/bitcoin/btcgetbalanceofaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get the balance of a Bitcoin address" -slug: "btcgetbalanceofaddress" -excerpt: "1 credit per API call
\nGet the balance of a Bitcoin address.
\nThe API returns the balance only if the address has up to 50,000 UTXOs (Unspent Transaction Outputs). For an address with more than 50,000 UTXOs, the API returns an error with the 403 response code.
50 credits per API call
\nGet the balance of multiple Bitcoin addresses, up to 30.
\nThe API returns the balance only if the address has up to 50,000 UTXOs (Unspent Transaction Outputs). For an address with more than 50,000 UTXOs, the API returns an error with the 403 response code.
1 credit per API call
\nGets Bitcoin block detail by block hash or height.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bitcoin/btcgetblockchaininfo.md b/v1.0/Blockchain/bitcoin/btcgetblockchaininfo.md deleted file mode 100644 index c47e101d..00000000 --- a/v1.0/Blockchain/bitcoin/btcgetblockchaininfo.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Bitcoin blockchain information" -slug: "btcgetblockchaininfo" -excerpt: "1 credit per API call
\nGets Bitcoin blockchain information. Obtains basic info like the testnet / mainnet version of the chain, the current block number and its hash.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bitcoin/btcgetblockhash.md b/v1.0/Blockchain/bitcoin/btcgetblockhash.md deleted file mode 100644 index 89cdea42..00000000 --- a/v1.0/Blockchain/bitcoin/btcgetblockhash.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get the hash of a Bitcoin block" -slug: "btcgetblockhash" -excerpt: "1 credit per API call
\nGets a Bitcoin block hash. Returns the hash of the block to get the block's details.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bitcoin/btcgetmempool.md b/v1.0/Blockchain/bitcoin/btcgetmempool.md deleted file mode 100644 index a9e34e23..00000000 --- a/v1.0/Blockchain/bitcoin/btcgetmempool.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get transactions from the Bitcoin mempool" -slug: "btcgetmempool" -excerpt: "1 credit per API call
\nGets Bitcoin transaction IDs in the mempool.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bitcoin/btcgetrawtransaction.md b/v1.0/Blockchain/bitcoin/btcgetrawtransaction.md deleted file mode 100644 index 1ca0a7dd..00000000 --- a/v1.0/Blockchain/bitcoin/btcgetrawtransaction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get a Bitcoin transaction by its hash" -slug: "btcgetrawtransaction" -excerpt: "1 credit per API call
\nGet Bitcoin Transaction detail by transaction hash.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:52 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bitcoin/btcgettxbyaddress.md b/v1.0/Blockchain/bitcoin/btcgettxbyaddress.md deleted file mode 100644 index 4fd9e89d..00000000 --- a/v1.0/Blockchain/bitcoin/btcgettxbyaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get all transactions for a Bitcoin address" -slug: "btcgettxbyaddress" -excerpt: "1 credit per API call
\nGet all transactions for a Bitcoin address.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:52 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bitcoin/btcgetutxo.md b/v1.0/Blockchain/bitcoin/btcgetutxo.md deleted file mode 100644 index f874c86f..00000000 --- a/v1.0/Blockchain/bitcoin/btcgetutxo.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get information about a transaction output (UTXO) in a Bitcoin transaction" -slug: "btcgetutxo" -excerpt: "1 credit per API call
\nGet information about a transaction output in a transaction and check whether this output is a UTXO or has been spent.
\n\"UTXO\" stands for \"Unspent Transaction Output\". A UTXO is the amount of BTC/satoshis that remains at a Bitcoin address after a cryptocurrency transaction involving this address has been performed. The UTXO can then be used as input for a new cryptocurrency transaction. For more information about Bitcoin transactions and UTXO, see the Bitcoin user documentation.
\n404 response code.This endpoint is deprecated. Do not use it.
\nInstead, use this API.
2 credits per API call
\nUse this endpoint URL as an http-based JSON RPC driver to connect directly to the node provided by Tatum.\nTo learn more about JSON RPC, visit the Bitcoin developers' guide.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bitcoin/btctransferblockchain.md b/v1.0/Blockchain/bitcoin/btctransferblockchain.md deleted file mode 100644 index 4e142448..00000000 --- a/v1.0/Blockchain/bitcoin/btctransferblockchain.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send BTC to Bitcoin addresses" -slug: "btctransferblockchain" -excerpt: "2 credits per API call
\nSend BTC to blockchain addresses.
\nBitcoin transactions are based on UTXOs. \"UTXO\" stands for \"Unspent Transaction Output\". A UTXO is the amount of BTC/satoshis that remains at a Bitcoin address after a cryptocurrency transaction involving this address has been performed. The UTXO can then be used as input for a new cryptocurrency transaction. For more information about Bitcoin transactions and UTXO, see the Bitcoin user documentation. To check UTXOs in a transaction, see the API for getting information about a transaction output (UTXO) in a Bitcoin transaction.
\nYou can build a BTC transaction by one of the following methods:
\nBtcTransactionFromAddress or BtcTransactionFromAddressKMS schema of the request body.BtcTransactionFromUTXO or BtcTransactionFromUTXOKMS schema of the request body.When an UTXO is entered into a transaction, the whole UTXO amount is included and must be spent. For example, address A receives two transactions, T1 with 1 BTC and T2 with 2 BTC. A transaction that consumes the UTXOs from both T1 and T2 will have an available amount of 3 BTC to spend:1 BTC (from T1) + 2 BTC (from T2) = 3 BTC (to spend in total)
You can send the assets to one or multiple recipients in one transaction. If you send the assets to multiple addresses, each address must have its own amount to receive.
\nPaying the gas fee and receiving the change
\nWhen the amount that the recipients should receive is lower than the amount from the UTXOs, the difference between these two amounts is by default used as the gas fee for the transaction. Because this amount may be considerable and you may not want to spend it all on the gas fee, you can explicitly specify the fee amount and the blockchain address where any extra funds remaining after covering the fee will be sent (the fee and changeAddress parameters in the request body, correspondingly).
Signing a transaction
\nWhen sending BTC, 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.
\nFor 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.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:52 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bnb-beacon-chain.md b/v1.0/Blockchain/bnb-beacon-chain.md deleted file mode 100644 index 55677df6..00000000 --- a/v1.0/Blockchain/bnb-beacon-chain.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "BNB Beacon Chain" -slug: "bnb-beacon-chain" -excerpt: "" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bnb-beacon-chain/bnbblockchaintransfer.md b/v1.0/Blockchain/bnb-beacon-chain/bnbblockchaintransfer.md deleted file mode 100644 index c00fdb00..00000000 --- a/v1.0/Blockchain/bnb-beacon-chain/bnbblockchaintransfer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send Binance / Binance Token from account to account" -slug: "bnbblockchaintransfer" -excerpt: "Send Binance or Binance Token token from account to account.
\nThis 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.\nNo 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.\nPrivateKey should be used only for quick development on testnet versions of blockchain when there is no risk of losing funds. In production,\n Tatum KMS should be used for the highest security standards, and signatureId should be present in the request.\n Alternatively, using the Tatum client library for supported languages.\n
Broadcast signed transaction to Binance blockchain. This method is used internally or Tatum client libraries.\nIt is possible to create custom signing mechanism and use this method only for broadcasting data to the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:01 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bnb-beacon-chain/bnbgeneratewallet.md b/v1.0/Blockchain/bnb-beacon-chain/bnbgeneratewallet.md deleted file mode 100644 index 2fd6b48d..00000000 --- a/v1.0/Blockchain/bnb-beacon-chain/bnbgeneratewallet.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Binance wallet" -slug: "bnbgeneratewallet" -excerpt: "Generate BNB account. Tatum does not support HD wallet for BNB, only specific address and private key can be generated.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bnb-beacon-chain/bnbgetaccount.md b/v1.0/Blockchain/bnb-beacon-chain/bnbgetaccount.md deleted file mode 100644 index 05ed9d51..00000000 --- a/v1.0/Blockchain/bnb-beacon-chain/bnbgetaccount.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Binance Account" -slug: "bnbgetaccount" -excerpt: "Get Binance Account Detail by address.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:00 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bnb-beacon-chain/bnbgetblock.md b/v1.0/Blockchain/bnb-beacon-chain/bnbgetblock.md deleted file mode 100644 index a094c4a3..00000000 --- a/v1.0/Blockchain/bnb-beacon-chain/bnbgetblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Binance Transactions in Block" -slug: "bnbgetblock" -excerpt: "Get Transactions in block by block height.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bnb-beacon-chain/bnbgetcurrentblock.md b/v1.0/Blockchain/bnb-beacon-chain/bnbgetcurrentblock.md deleted file mode 100644 index 33d5a48c..00000000 --- a/v1.0/Blockchain/bnb-beacon-chain/bnbgetcurrentblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Binance current block" -slug: "bnbgetcurrentblock" -excerpt: "Get Binance current block number.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:00 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bnb-beacon-chain/bnbgettransaction.md b/v1.0/Blockchain/bnb-beacon-chain/bnbgettransaction.md deleted file mode 100644 index f1e9bfc6..00000000 --- a/v1.0/Blockchain/bnb-beacon-chain/bnbgettransaction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Binance Transaction" -slug: "bnbgettransaction" -excerpt: "Get Binance Transaction by transaction hash.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:00 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bnb-beacon-chain/bnbgettxbyaccount.md b/v1.0/Blockchain/bnb-beacon-chain/bnbgettxbyaccount.md deleted file mode 100644 index 48555e6c..00000000 --- a/v1.0/Blockchain/bnb-beacon-chain/bnbgettxbyaccount.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Binance Transactions By Address" -slug: "bnbgettxbyaccount" -excerpt: "Get Binance Transactions by address.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:00 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bnb-smart-chain.md b/v1.0/Blockchain/bnb-smart-chain.md deleted file mode 100644 index b2e93940..00000000 --- a/v1.0/Blockchain/bnb-smart-chain.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "BNB Smart Chain" -slug: "bnb-smart-chain" -excerpt: "" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bnb-smart-chain/bscblockchainsmartcontractinvocation.md b/v1.0/Blockchain/bnb-smart-chain/bscblockchainsmartcontractinvocation.md deleted file mode 100644 index f28b4f81..00000000 --- a/v1.0/Blockchain/bnb-smart-chain/bscblockchainsmartcontractinvocation.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Invoke a method in a smart contract on BNB Smart Chain" -slug: "bscblockchainsmartcontractinvocation" -excerpt: "2 credits per API call
\nInvoke a method in an existing smart contract on BNB Smart Chain.
\nYou can call a read-only or write method.
\nTroubleshooting a failed transaction
\nTatum ensures that this API works against the blockchain (accesses the blockchain, finds the specified smart contract, and executes the specified ABI method with the provided parameters).
However, because this API can be run against any smart contract on the blockchain, Tatum cannot in any way guarantee that the method itself will be executed successfully.
If you have issues with invoking the method, refer to the user documentation for this method, or contact the author of the smart contract.
\nFor more information about invoking methods in smart contracts, see this article on our Support Portal.
\nSigning a transaction
\nWhen 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.
If caller field is present instead of the private key, Tatum will sign the transaction with the managed private key connected to the caller address. This is applicable only for paid mainnet plans and all testnet plans. Keep in mind that the caller address must have enough access right to perform the action in the smart contract method.
\nProviding 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.
\nFor 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.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:09 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bnb-smart-chain/bscblockchaintransfer.md b/v1.0/Blockchain/bnb-smart-chain/bscblockchaintransfer.md deleted file mode 100644 index bd661e10..00000000 --- a/v1.0/Blockchain/bnb-smart-chain/bscblockchaintransfer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send BSC / BEP20 from account to account" -slug: "bscblockchaintransfer" -excerpt: "2 credits per API call
\nSend BNB or Tatum supported BEP20 token from account to account.
\n
Signing a transaction
\nWhen sending BNB, 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.
\nProviding 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.
\nFor 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.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:09 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bnb-smart-chain/bscbroadcast.md b/v1.0/Blockchain/bnb-smart-chain/bscbroadcast.md deleted file mode 100644 index 0cb249bc..00000000 --- a/v1.0/Blockchain/bnb-smart-chain/bscbroadcast.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Broadcast signed BSC transaction" -slug: "bscbroadcast" -excerpt: "2 credits per API call
\nBroadcast signed transaction to BSC blockchain. This method is used internally from Tatum KMS or Tatum client libraries.\nIt is possible to create custom signing mechanism and use this method only for broadcasting data to the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bnb-smart-chain/bscgenerateaddress.md b/v1.0/Blockchain/bnb-smart-chain/bscgenerateaddress.md deleted file mode 100644 index 42a80ae0..00000000 --- a/v1.0/Blockchain/bnb-smart-chain/bscgenerateaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate BSC account address from Extended public key" -slug: "bscgenerateaddress" -excerpt: "1 credit per API call
\nGenerate BSC account deposit address from Extended public key. Deposit address is generated for the specific index - each extended public key can generate\nup to 2^31 addresses starting from index 0 until 2^31.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:08 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bnb-smart-chain/bscgenerateaddressprivatekey.md b/v1.0/Blockchain/bnb-smart-chain/bscgenerateaddressprivatekey.md deleted file mode 100644 index 11ecc792..00000000 --- a/v1.0/Blockchain/bnb-smart-chain/bscgenerateaddressprivatekey.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate BSC private key" -slug: "bscgenerateaddressprivatekey" -excerpt: "1 credit per API call
\nGenerate private key of address from mnemonic for given derivation path index. Private key is generated for the specific index - each mnemonic\ncan generate up to 2^31 private keys starting from index 0 until 2^31.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:08 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bnb-smart-chain/bscgeneratewallet.md b/v1.0/Blockchain/bnb-smart-chain/bscgeneratewallet.md deleted file mode 100644 index e6032b15..00000000 --- a/v1.0/Blockchain/bnb-smart-chain/bscgeneratewallet.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate BSC wallet" -slug: "bscgeneratewallet" -excerpt: "1 credit per API call
\nTatum 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 BSC wallet with derivation path m'/44'/60'/0'/0. More about BIP44 HD wallets can be found here - https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki.\nGenerate BIP44 compatible BSC wallet.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:08 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bnb-smart-chain/bscgetbalance.md b/v1.0/Blockchain/bnb-smart-chain/bscgetbalance.md deleted file mode 100644 index bb48799e..00000000 --- a/v1.0/Blockchain/bnb-smart-chain/bscgetbalance.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get BSC Account balance" -slug: "bscgetbalance" -excerpt: "1 credit per API call
\nGet BSC account balance in BNB. This method does not prints any balance of the BEP20 or BEP721 tokens on the account.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:08 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bnb-smart-chain/bscgetblock.md b/v1.0/Blockchain/bnb-smart-chain/bscgetblock.md deleted file mode 100644 index ff36b0a8..00000000 --- a/v1.0/Blockchain/bnb-smart-chain/bscgetblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get BSC block by hash" -slug: "bscgetblock" -excerpt: "1 credit per API call
\nGet BSC block by block hash or block number.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:08 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bnb-smart-chain/bscgetcurrentblock.md b/v1.0/Blockchain/bnb-smart-chain/bscgetcurrentblock.md deleted file mode 100644 index 67bcae5d..00000000 --- a/v1.0/Blockchain/bnb-smart-chain/bscgetcurrentblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get current block number" -slug: "bscgetcurrentblock" -excerpt: "1 credit per API call
\nGet BSC current block number. This is the number of the latest block in the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:09 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bnb-smart-chain/bscgettransaction.md b/v1.0/Blockchain/bnb-smart-chain/bscgettransaction.md deleted file mode 100644 index 57876cb5..00000000 --- a/v1.0/Blockchain/bnb-smart-chain/bscgettransaction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get BSC Transaction" -slug: "bscgettransaction" -excerpt: "2 credits per API call
\nGet BSC transaction by transaction hash.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bnb-smart-chain/bscgettransactioncount.md b/v1.0/Blockchain/bnb-smart-chain/bscgettransactioncount.md deleted file mode 100644 index ed2741f6..00000000 --- a/v1.0/Blockchain/bnb-smart-chain/bscgettransactioncount.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get count of outgoing BSC transactions" -slug: "bscgettransactioncount" -excerpt: "1 credit per API call
\nGet a number of outgoing BSC transactions for the address. When a transaction is sent, there can be multiple outgoing transactions,\nwhich are not yet processed by the blockchain. To distinguish between them, there is a counter called a nonce, which represents\nthe order of the transaction in the list of outgoing transactions.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:09 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/bnb-smart-chain/bscweb3driver.md b/v1.0/Blockchain/bnb-smart-chain/bscweb3driver.md deleted file mode 100644 index a1787413..00000000 --- a/v1.0/Blockchain/bnb-smart-chain/bscweb3driver.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Web3 HTTP driver" -slug: "bscweb3driver" -excerpt: "2 credits per API call
\nThis 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 BSC node provided by Tatum.\nTo learn more about BSC Web3, visit the BSC developer's guide.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:09 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/cardano.md b/v1.0/Blockchain/cardano.md deleted file mode 100644 index 7e2e114f..00000000 --- a/v1.0/Blockchain/cardano.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Cardano" -slug: "cardano" -excerpt: "" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/cardano/adabroadcast.md b/v1.0/Blockchain/cardano/adabroadcast.md deleted file mode 100644 index d0e1970e..00000000 --- a/v1.0/Blockchain/cardano/adabroadcast.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Broadcast signed Ada transaction" -slug: "adabroadcast" -excerpt: "\nYou can work with Cardano by connecting directly to a blockchain node provided by Tatum.
Broadcasts a signed transaction to the Ada blockchain. This method is used internally from Tatum KMS or Tatum Client Libraries.\nIt is possible to create a custom signing mechanism and only use this method for broadcasting data to the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:02 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/cardano/adagenerateaddress.md b/v1.0/Blockchain/cardano/adagenerateaddress.md deleted file mode 100644 index 5f4f6da7..00000000 --- a/v1.0/Blockchain/cardano/adagenerateaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Ada deposit address from Extended public key" -slug: "adagenerateaddress" -excerpt: "\nYou can work with Cardano by connecting directly to a blockchain node provided by Tatum.
Generates a Ada deposit address from an Extended public key. The deposit address is generated for the specific index - each extended public key can generate\nup to 2^31 addresses starting from index 0 until 2^31 - 1.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:02 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/cardano/adagenerateaddressprivatekey.md b/v1.0/Blockchain/cardano/adagenerateaddressprivatekey.md deleted file mode 100644 index defe6263..00000000 --- a/v1.0/Blockchain/cardano/adagenerateaddressprivatekey.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Ada private key" -slug: "adagenerateaddressprivatekey" -excerpt: "\nYou can work with Cardano by connecting directly to a blockchain node provided by Tatum.
Generates a private key for an address from a mnemonic for a given derivation path index. The private key is generated for the specific index - each mnemonic\ncan generate up to 2^32 private keys starting from index 0 until 2^31 - 1.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:02 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/cardano/adageneratewallet.md b/v1.0/Blockchain/cardano/adageneratewallet.md deleted file mode 100644 index 0e4ef0bb..00000000 --- a/v1.0/Blockchain/cardano/adageneratewallet.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Ada wallet" -slug: "adageneratewallet" -excerpt: "\nYou can work with Cardano by connecting directly to a blockchain node provided by Tatum.
Tatum supports BIP44 HD wallets. Because they can generate 2^31 addresses from 1 mnemonic phrase, they are very convenient and secure. A mnemonic phrase consists of 24 special words in a 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 ADA wallet with derivation path m/1852'/1815'/0'. More about BIP44 HD wallets can be found here - https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki.\nGenerate BIP44 compatible Ada wallet.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:01 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/cardano/adagetaccount.md b/v1.0/Blockchain/cardano/adagetaccount.md deleted file mode 100644 index 5cb93829..00000000 --- a/v1.0/Blockchain/cardano/adagetaccount.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Gets a Ada account by address" -slug: "adagetaccount" -excerpt: "\nYou can work with Cardano by connecting directly to a blockchain node provided by Tatum.
Gets a Ada account by address.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:02 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/cardano/adagetblock.md b/v1.0/Blockchain/cardano/adagetblock.md deleted file mode 100644 index cc56be92..00000000 --- a/v1.0/Blockchain/cardano/adagetblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Block by hash or height" -slug: "adagetblock" -excerpt: "You can work with Cardano by connecting directly to a blockchain node provided by Tatum.
Gets Ada block detail by block hash or height.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:02 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/cardano/adagetblockchaininfo.md b/v1.0/Blockchain/cardano/adagetblockchaininfo.md deleted file mode 100644 index 60273030..00000000 --- a/v1.0/Blockchain/cardano/adagetblockchaininfo.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Blockchain information" -slug: "adagetblockchaininfo" -excerpt: "You can work with Cardano by connecting directly to a blockchain node provided by Tatum.
Gets Ada blockchain information. Obtains basic info like the testnet / mainnet version of the chain, the current block number and its hash.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:01 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/cardano/adagetrawtransaction.md b/v1.0/Blockchain/cardano/adagetrawtransaction.md deleted file mode 100644 index e464c8be..00000000 --- a/v1.0/Blockchain/cardano/adagetrawtransaction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get transaction by hash" -slug: "adagetrawtransaction" -excerpt: "You can work with Cardano by connecting directly to a blockchain node provided by Tatum.
Get Ada Transaction detail by transaction hash.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:02 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/cardano/adagettxbyaddress.md b/v1.0/Blockchain/cardano/adagettxbyaddress.md deleted file mode 100644 index 4075e974..00000000 --- a/v1.0/Blockchain/cardano/adagettxbyaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get transactions by address" -slug: "adagettxbyaddress" -excerpt: "You can work with Cardano by connecting directly to a blockchain node provided by Tatum.
Gets a Ada transaction by address.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/cardano/adagetutxobyaddress.md b/v1.0/Blockchain/cardano/adagetutxobyaddress.md deleted file mode 100644 index 503865a3..00000000 --- a/v1.0/Blockchain/cardano/adagetutxobyaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get UTXOs by address" -slug: "adagetutxobyaddress" -excerpt: "You can work with Cardano by connecting directly to a blockchain node provided by Tatum.
Gets a Ada UTXOs by address.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:02 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/cardano/adatransferblockchain.md b/v1.0/Blockchain/cardano/adatransferblockchain.md deleted file mode 100644 index a2bc0631..00000000 --- a/v1.0/Blockchain/cardano/adatransferblockchain.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send ADA to Cardano addresses" -slug: "adatransferblockchain" -excerpt: "2 credits per API call
\nSend ADA to blockchain addresses.
\nCardano transactions are based on UTXOs. \"UTXO\" stands for \"Unspent Transaction Output\". A UTXO is the amount of ADA that remains at a Cardano address after a cryptocurrency transaction involving this address has been performed. The UTXO can then be used as input for a new cryptocurrency transaction. For more information about the UTXO, see the Bitcoin user documentation.
\nYou can build an ADA transaction by one of the following methods:
\nAdaTransactionFromAddress or AdaTransactionFromAddressKMS schema of the request body.AdaTransactionFromUTXO or AdaTransactionFromUTXOKMS schema of the request body.When an UTXO is entered into a transaction, the whole UTXO amount is included and must be spent. For example, address A receives two transactions, T1 with 1 ADA and T2 with 2 ADA. A transaction that consumes the UTXOs from both T1 and T2 will have an available amount of 3 ADA to spend:1 ADA (from T1) + 2 ADA (from T2) = 3 ADA (to spend in total)
You can send the assets to one or multiple recipients in one transaction. If you send the assets to multiple addresses, each address must have its own amount to receive.
\nPaying the gas fee and receiving the change
\nWhen the amount that the recipients should receive is lower than the amount from the UTXOs, the difference between these two amounts is by default used as the gas fee for the transaction. Because this amount may be considerable and you may not want to spend it all on the gas fee, you can explicitly specify the fee amount and the blockchain address where any extra funds remaining after covering the fee will be sent (the fee and changeAddress parameters in the request body, correspondingly).
Signing a transaction
\nWhen sending ADA, 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.
\nFor 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.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/celo.md b/v1.0/Blockchain/celo.md deleted file mode 100644 index 19f43996..00000000 --- a/v1.0/Blockchain/celo.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Celo" -slug: "celo" -excerpt: "" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/celo/celoblockchainsmartcontractinvocation.md b/v1.0/Blockchain/celo/celoblockchainsmartcontractinvocation.md deleted file mode 100644 index 8ad19aa6..00000000 --- a/v1.0/Blockchain/celo/celoblockchainsmartcontractinvocation.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Invoke a method in a smart contract on Celo" -slug: "celoblockchainsmartcontractinvocation" -excerpt: "2 credits per API call
\nInvoke a method in an existing smart contract on Celo.
\nYou can call a read-only or write method.
\nTroubleshooting a failed transaction
\nTatum ensures that this API works against the blockchain (accesses the blockchain, finds the specified smart contract, and executes the specified ABI method with the provided parameters).
However, because this API can be run against any smart contract on the blockchain, Tatum cannot in any way guarantee that the method itself will be executed successfully.
If you have issues with invoking the method, refer to the user documentation for this method, or contact the author of the smart contract.
\nFor more information about invoking methods in smart contracts, see this article on our Support Portal.
\nSigning a transaction
\nWhen 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.
\nFor 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.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:06 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/celo/celoblockchaintransfer.md b/v1.0/Blockchain/celo/celoblockchaintransfer.md deleted file mode 100644 index 9101e9db..00000000 --- a/v1.0/Blockchain/celo/celoblockchaintransfer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send Celo / ERC20 from account to account" -slug: "celoblockchaintransfer" -excerpt: "2 credits per API call
\nSend Celo, cUSD or Tatum supported ERC20 token from account to account.
\n
Signing a transaction
\nWhen sending CELO, 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.
\nProviding 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.
\nFor 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.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:06 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/celo/celobroadcast.md b/v1.0/Blockchain/celo/celobroadcast.md deleted file mode 100644 index f5bcd7cf..00000000 --- a/v1.0/Blockchain/celo/celobroadcast.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Broadcast signed Celo transaction" -slug: "celobroadcast" -excerpt: "2 credits per API call
\nBroadcast signed transaction to Celo blockchain. This method is used internally from Tatum KMS or Tatum client libraries.\nIt is possible to create custom signing mechanism and use this method only for broadcasting data to the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:06 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/celo/celogenerateaddress.md b/v1.0/Blockchain/celo/celogenerateaddress.md deleted file mode 100644 index 2bf2d624..00000000 --- a/v1.0/Blockchain/celo/celogenerateaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Celo account address from Extended public key" -slug: "celogenerateaddress" -excerpt: "1 credit per API call
\nGenerate Celo account deposit address from Extended public key. Deposit address is generated for the specific index - each extended public key can generate\nup to 2^31 addresses starting from index 0 until 2^31.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/celo/celogenerateaddressprivatekey.md b/v1.0/Blockchain/celo/celogenerateaddressprivatekey.md deleted file mode 100644 index 0550b5a5..00000000 --- a/v1.0/Blockchain/celo/celogenerateaddressprivatekey.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Celo private key" -slug: "celogenerateaddressprivatekey" -excerpt: "1 credit per API call
\nGenerate private key of address from mnemonic for given derivation path index. Private key is generated for the specific index - each mnemonic\ncan generate up to 2^31 private keys starting from index 0 until 2^31.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:06 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/celo/celogeneratewallet.md b/v1.0/Blockchain/celo/celogeneratewallet.md deleted file mode 100644 index ca4aed34..00000000 --- a/v1.0/Blockchain/celo/celogeneratewallet.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Celo wallet" -slug: "celogeneratewallet" -excerpt: "1 credit per API call
\nTatum 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 Celo wallet with derivation path m'/44'/52752'/0'/0. More about BIP44 HD wallets can be found here - https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki.\nGenerate BIP44 compatible Celo wallet.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:06 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/celo/celogetbalance.md b/v1.0/Blockchain/celo/celogetbalance.md deleted file mode 100644 index 0b12c7aa..00000000 --- a/v1.0/Blockchain/celo/celogetbalance.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Celo Account balance" -slug: "celogetbalance" -excerpt: "1 credit per API call
\nGet Celo account balance in ETH. This method does not prints any balance of the ERC20 or ERC721 tokens on the account.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:06 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/celo/celogetblock.md b/v1.0/Blockchain/celo/celogetblock.md deleted file mode 100644 index 24e2bc91..00000000 --- a/v1.0/Blockchain/celo/celogetblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Celo block by hash" -slug: "celogetblock" -excerpt: "1 credit per API call
\nGet Celo block by block hash or block number.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:06 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/celo/celogetcurrentblock.md b/v1.0/Blockchain/celo/celogetcurrentblock.md deleted file mode 100644 index 91c4e592..00000000 --- a/v1.0/Blockchain/celo/celogetcurrentblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get current block number" -slug: "celogetcurrentblock" -excerpt: "1 credit per API call
\nGet Celo current block number. This is the number of the latest block in the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/celo/celogettransaction.md b/v1.0/Blockchain/celo/celogettransaction.md deleted file mode 100644 index a049f23d..00000000 --- a/v1.0/Blockchain/celo/celogettransaction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Celo Transaction" -slug: "celogettransaction" -excerpt: "2 credits per API call
\nGet Celo transaction by transaction hash.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:06 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/celo/celogettransactionbyaddress.md b/v1.0/Blockchain/celo/celogettransactionbyaddress.md deleted file mode 100644 index 664a72ac..00000000 --- a/v1.0/Blockchain/celo/celogettransactionbyaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Celo transactions by address" -slug: "celogettransactionbyaddress" -excerpt: "This endpoint is deprecated. Do not use it.
\n1 credit per API call
\nGet Celo transactions by address. This includes incoming and outgoing transactions for the address.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:06 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/celo/celogettransactioncount.md b/v1.0/Blockchain/celo/celogettransactioncount.md deleted file mode 100644 index 9b831c70..00000000 --- a/v1.0/Blockchain/celo/celogettransactioncount.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get count of outgoing Celo transactions" -slug: "celogettransactioncount" -excerpt: "1 credit per API call
\nGet a number of outgoing Celo transactions for the address. When a transaction is sent, there can be multiple outgoing transactions,\nwhich are not yet processed by the blockchain. To distinguish between them, there is a counter called a nonce, which represents\nthe order of the transaction in the list of outgoing transactions.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/celo/celoweb3driver.md b/v1.0/Blockchain/celo/celoweb3driver.md deleted file mode 100644 index c0146820..00000000 --- a/v1.0/Blockchain/celo/celoweb3driver.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Web3 HTTP driver" -slug: "celoweb3driver" -excerpt: "2 credits per API call
\nThis 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 Celo node provided by Tatum.\nTo learn more about Celo Web3, visit the Celo developer's guide.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:06 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/dogecoin.md b/v1.0/Blockchain/dogecoin.md deleted file mode 100644 index 8ca210ef..00000000 --- a/v1.0/Blockchain/dogecoin.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Dogecoin" -slug: "dogecoin" -excerpt: "" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/dogecoin/dogebroadcast.md b/v1.0/Blockchain/dogecoin/dogebroadcast.md deleted file mode 100644 index e4e49b89..00000000 --- a/v1.0/Blockchain/dogecoin/dogebroadcast.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Broadcast signed Dogecoin transaction" -slug: "dogebroadcast" -excerpt: "Broadcast signed transaction to Dogecoin blockchain. This method is used internally from Tatum KMS or Tatum client libraries.\nIt is possible to create custom signing mechanism and use this method only for broadcasting data to the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/dogecoin/dogegenerateaddress.md b/v1.0/Blockchain/dogecoin/dogegenerateaddress.md deleted file mode 100644 index ba1826b0..00000000 --- a/v1.0/Blockchain/dogecoin/dogegenerateaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Dogecoin deposit address from Extended public key" -slug: "dogegenerateaddress" -excerpt: "Generate Dogecoin deposit address from Extended public key. Deposit address is generated for the specific index - each extended public key can generate\nup to 2^31 addresses starting from index 0 until 2^31 - 1.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:56 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/dogecoin/dogegenerateaddressprivatekey.md b/v1.0/Blockchain/dogecoin/dogegenerateaddressprivatekey.md deleted file mode 100644 index a0dfd04a..00000000 --- a/v1.0/Blockchain/dogecoin/dogegenerateaddressprivatekey.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Dogecoin private key" -slug: "dogegenerateaddressprivatekey" -excerpt: "Generate private key for address from mnemonic for given derivation path index. Private key is generated for the specific index - each mnemonic\ncan generate up to 2^32 private keys starting from index 0 until 2^31 - 1.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:56 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/dogecoin/dogegeneratewallet.md b/v1.0/Blockchain/dogecoin/dogegeneratewallet.md deleted file mode 100644 index cd7a1123..00000000 --- a/v1.0/Blockchain/dogecoin/dogegeneratewallet.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Dogecoin wallet" -slug: "dogegeneratewallet" -excerpt: "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 Dogecoin wallet with derivation path m'/44'/3'/0'/0. More about BIP44 HD wallets can be found here - https://github.com/litecoin/bips/blob/master/bip-0044.mediawiki.\nGenerate BIP44 compatible Dogecoin wallet.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:56 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/dogecoin/dogegetbalanceofaddress.md b/v1.0/Blockchain/dogecoin/dogegetbalanceofaddress.md deleted file mode 100644 index f4ea3b15..00000000 --- a/v1.0/Blockchain/dogecoin/dogegetbalanceofaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get the balance of a Dogecoin address" -slug: "dogegetbalanceofaddress" -excerpt: "Get Dogecoin Balance of the address.
\n50 credits per API call
\nGet the balance of multiple Dogecoin addresses, up to 30.
\nThe API returns the balance only if the address has up to 50,000 UTXOs (Unspent Transaction Outputs). For an address with more than 50,000 UTXOs, the API returns an error with the 403 response code.
Get Dogecoin Block detail by block hash or height.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:56 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/dogecoin/dogegetblockchaininfo.md b/v1.0/Blockchain/dogecoin/dogegetblockchaininfo.md deleted file mode 100644 index ee93d0a3..00000000 --- a/v1.0/Blockchain/dogecoin/dogegetblockchaininfo.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Dogecoin Blockchain Information" -slug: "dogegetblockchaininfo" -excerpt: "Get Dogecoin Blockchain Information. Obtain basic info like testnet / mainnet version of the chain, current block number and it's hash.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:56 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/dogecoin/dogegetblockhash.md b/v1.0/Blockchain/dogecoin/dogegetblockhash.md deleted file mode 100644 index e21a1187..00000000 --- a/v1.0/Blockchain/dogecoin/dogegetblockhash.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Dogecoin Block hash" -slug: "dogegetblockhash" -excerpt: "Get Dogecoin Block hash. Returns hash of the block to get the block detail.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:56 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/dogecoin/dogegetmempool.md b/v1.0/Blockchain/dogecoin/dogegetmempool.md deleted file mode 100644 index 86ffdb7b..00000000 --- a/v1.0/Blockchain/dogecoin/dogegetmempool.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Mempool Transactions" -slug: "dogegetmempool" -excerpt: "Get Dogecoin Transaction ids in the mempool.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:57 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/dogecoin/dogegetrawtransaction.md b/v1.0/Blockchain/dogecoin/dogegetrawtransaction.md deleted file mode 100644 index a82394c3..00000000 --- a/v1.0/Blockchain/dogecoin/dogegetrawtransaction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Dogecoin Transaction by hash" -slug: "dogegetrawtransaction" -excerpt: "Get Dogecoin Transaction detail by transaction hash.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/dogecoin/dogegettxbyaddress.md b/v1.0/Blockchain/dogecoin/dogegettxbyaddress.md deleted file mode 100644 index 2784d0ab..00000000 --- a/v1.0/Blockchain/dogecoin/dogegettxbyaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Dogecoin Transactions by address" -slug: "dogegettxbyaddress" -excerpt: "Get Dogecoin Transaction by address.
\n1 credit per API call
\nGet information about a transaction output in a transaction and check whether this output is a UTXO or has been spent.
\n\"UTXO\" stands for \"Unspent Transaction Output\". A UTXO is the amount of DOGE that remains at a Dogecoin address after a cryptocurrency transaction involving this address has been performed. The UTXO can then be used as input for a new cryptocurrency transaction. For more information about the UTXO, see the Bitcoin user documentation.
\n404 response code.2 credits per API call
\nThis endpoint is deprecated. Use the HTTP-based JSON RPC driver instead.
Use this endpoint URL as an http-based JSON RPC driver to connect directly to the node provided by Tatum.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:56 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/dogecoin/dogetransferblockchain.md b/v1.0/Blockchain/dogecoin/dogetransferblockchain.md deleted file mode 100644 index 45567a1a..00000000 --- a/v1.0/Blockchain/dogecoin/dogetransferblockchain.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send DOGE to Dogecoin addresses" -slug: "dogetransferblockchain" -excerpt: "2 credits per API call
\nSend DOGE to blockchain addresses.
\nDogecoin transactions are based on UTXOs. \"UTXO\" stands for \"Unspent Transaction Output\". A UTXO is the amount of DOGE that remains at a Bitcoin Cash address after a cryptocurrency transaction involving this address has been performed. The UTXO can then be used as input for a new cryptocurrency transaction. For more information the UTXO, see the Bitcoin user documentation. To check UTXOs in a transaction, see the API for getting information about a transaction output (UTXO) in a Dogecoin transaction
\nYou build a DOGE transaction by sending DOGE from UTXOs. Each UTXO is included in the transaction.
\nWhen an UTXO is entered into a transaction, the whole UTXO amount is included and must be spent. For example, address A receives two transactions, T1 with 1 DOGE and T2 with 2 DOGE. A transaction that consumes the UTXOs from both T1 and T2 will have an available amount of 3 DOGE to spend:1 DOGE (from T1) + 2 DOGE (from T2) = 3 DOGE (to spend in total)
You can send the assets to one or multiple recipients in one transaction. If you send the assets to multiple addresses, each address must have its own amount to receive.
\nPaying the gas fee and receiving the change
\nWhen the amount that the recipients should receive is lower than the amount from the UTXOs, the difference between these two amounts is by default used as the gas fee for the transaction. Because this amount may be considerable and you may not want to spend it all on the gas fee, you can explicitly specify the fee amount and the blockchain address where any extra funds remaining after covering the fee will be sent (the fee and changeAddress parameters in the request body, correspondingly).
Signing a transaction
\nWhen sending DOGE, 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.
\nFor 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.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:57 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/elrond.md b/v1.0/Blockchain/elrond.md deleted file mode 100644 index 463192ee..00000000 --- a/v1.0/Blockchain/elrond.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Elrond" -slug: "elrond" -excerpt: "" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/elrond/egldblockchaintransfer.md b/v1.0/Blockchain/elrond/egldblockchaintransfer.md deleted file mode 100644 index 5092fb17..00000000 --- a/v1.0/Blockchain/elrond/egldblockchaintransfer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send EGLD from account to account" -slug: "egldblockchaintransfer" -excerpt: "Send EGLD from account to account.
\nThis 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.\nNo 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\nor signatureId. PrivateKey should be used only for quick development on devnet versions of blockchain when there is no risk of losing funds. In production,\nTatum KMS should be used for the highest security standards, and signatureId should be present in the request.\nAlternatively, using the Tatum client library for supported languages.\n
Broadcast signed transaction to EGLD blockchain. This method is used internally from Tatum KMS or Tatum client libraries.\nIt is possible to create custom signing mechanism and use this method only for broadcasting data to the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:07 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/elrond/egldgenerateaddress.md b/v1.0/Blockchain/elrond/egldgenerateaddress.md deleted file mode 100644 index 48ee0b03..00000000 --- a/v1.0/Blockchain/elrond/egldgenerateaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate EGLD account address from mnemonic" -slug: "egldgenerateaddress" -excerpt: "Generate EGLD account deposit address from mnemonic phrase. Deposit address is generated for the specific\nindex - each mnemonic phrase can generate up to 2^31 addresses starting from index 0 until 2^31.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:07 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/elrond/egldgenerateaddressprivatekey.md b/v1.0/Blockchain/elrond/egldgenerateaddressprivatekey.md deleted file mode 100644 index 4601551d..00000000 --- a/v1.0/Blockchain/elrond/egldgenerateaddressprivatekey.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate EGLD private key" -slug: "egldgenerateaddressprivatekey" -excerpt: "Generate private key of address from mnemonic for given derivation path index. Private key is generated for the specific index - each mnemonic\ncan generate up to 2^31 private keys starting from index 0 until 2^31.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:07 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/elrond/egldgeneratewallet.md b/v1.0/Blockchain/elrond/egldgeneratewallet.md deleted file mode 100644 index 7cb6a84a..00000000 --- a/v1.0/Blockchain/elrond/egldgeneratewallet.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate EGLD wallet" -slug: "egldgeneratewallet" -excerpt: "The Elrond Address format is bech32, specified by the BIP 0173. The address always starts with an erd1. It is very convenient and secure, since it can generate 2^31 addresses from 1 mnemonic phrase.\nMnemonic phrase consists of 24 special words in defined order and can restore access to all generated addresses and private keys.\n
\nEach address is identified by 3 main values:\n
Tatum follows BIP44 specification and generates for EGLD wallet with derivation path m'/44'/508'/0'/0'.\nMore about BIP44 HD wallets can be found here - https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki.\nGenerate BIP44 compatible EGLD wallet.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:07 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/elrond/egldgetbalance.md b/v1.0/Blockchain/elrond/egldgetbalance.md deleted file mode 100644 index 0bd529b1..00000000 --- a/v1.0/Blockchain/elrond/egldgetbalance.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get EGLD Account balance" -slug: "egldgetbalance" -excerpt: "Get account balance in EGLD.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:07 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/elrond/egldgetblock.md b/v1.0/Blockchain/elrond/egldgetblock.md deleted file mode 100644 index ed274fc3..00000000 --- a/v1.0/Blockchain/elrond/egldgetblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get EGLD block by hash" -slug: "egldgetblock" -excerpt: "Get EGLD block by block hash or block number. EGLD docs
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:07 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/elrond/egldgetcurrentblock.md b/v1.0/Blockchain/elrond/egldgetcurrentblock.md deleted file mode 100644 index 3b1eeacf..00000000 --- a/v1.0/Blockchain/elrond/egldgetcurrentblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get current block number" -slug: "egldgetcurrentblock" -excerpt: "Get EGLD current block number. This is the number of the latest block in the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/elrond/egldgettransaction.md b/v1.0/Blockchain/elrond/egldgettransaction.md deleted file mode 100644 index e8bdcd1c..00000000 --- a/v1.0/Blockchain/elrond/egldgettransaction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get EGLD Transaction" -slug: "egldgettransaction" -excerpt: "Get EGLD transaction by transaction hash. Detail result please find here EGLD docs
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/elrond/egldgettransactionaddress.md b/v1.0/Blockchain/elrond/egldgettransactionaddress.md deleted file mode 100644 index b7b3edef..00000000 --- a/v1.0/Blockchain/elrond/egldgettransactionaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get count of outgoing EGLD transactions" -slug: "egldgettransactionaddress" -excerpt: "This endpoint allows one to retrieve the latest 20 transactions sent from an address.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:07 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/elrond/egldgettransactioncount.md b/v1.0/Blockchain/elrond/egldgettransactioncount.md deleted file mode 100644 index ed9e0fc6..00000000 --- a/v1.0/Blockchain/elrond/egldgettransactioncount.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get count of outgoing EGLD transactions" -slug: "egldgettransactioncount" -excerpt: "Get a number of outgoing EGLD transactions for the address. When a transaction is sent, there can be multiple outgoing transactions,\nwhich are not yet processed by the blockchain. To distinguish between them, there is a counter called a nonce, which represents\nthe order of the transaction in the list of outgoing transactions.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/elrond/egldnodeget.md b/v1.0/Blockchain/elrond/egldnodeget.md deleted file mode 100644 index 18cb2ea6..00000000 --- a/v1.0/Blockchain/elrond/egldnodeget.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Node HTTP driver" -slug: "egldnodeget" -excerpt: "2 credits per API call
\nThis endpoint is deprecated. Use the HTTP-based JSON RPC driver instead.
Use this endpoint URL as a http-based driver to connect directly to the EGLD node provided by Tatum.\nTo learn more about EGLD, visit the EGLD developer's guide.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:07 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/elrond/egldnodepost.md b/v1.0/Blockchain/elrond/egldnodepost.md deleted file mode 100644 index ac0f198e..00000000 --- a/v1.0/Blockchain/elrond/egldnodepost.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Node HTTP driver" -slug: "egldnodepost" -excerpt: "2 credits per API call
\nThis endpoint is deprecated. Use the HTTP-based JSON RPC driver instead.
Use this endpoint URL as a http-based driver to connect directly to the EGLD node provided by Tatum.\nTo learn more about EGLD, visit the EGLD developer's guide.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/ethereum-1.md b/v1.0/Blockchain/ethereum-1.md deleted file mode 100644 index bbf85a1e..00000000 --- a/v1.0/Blockchain/ethereum-1.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Ethereum" -slug: "ethereum-1" -excerpt: "" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/ethereum-1/ethblockchainsmartcontractinvocation.md b/v1.0/Blockchain/ethereum-1/ethblockchainsmartcontractinvocation.md deleted file mode 100644 index fbd6ff2c..00000000 --- a/v1.0/Blockchain/ethereum-1/ethblockchainsmartcontractinvocation.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Invoke a method in a smart contract on Ethereum" -slug: "ethblockchainsmartcontractinvocation" -excerpt: "2 credits per API call
\nInvoke a method in an existing smart contract on Ethereum.
\nYou can call a read-only or write method.
\nTroubleshooting a failed transaction
\nTatum ensures that this API works against the blockchain (accesses the blockchain, finds the specified smart contract, and executes the specified ABI method with the provided parameters).
However, because this API can be run against any smart contract on the blockchain, Tatum cannot in any way guarantee that the method itself will be executed successfully.
If you have issues with invoking the method, refer to the user documentation for this method, or contact the author of the smart contract.
\nFor more information about invoking methods in smart contracts, see this article on our Support Portal.
\nSigning a transaction
\nWhen 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.
If caller field is present instead of the private key, Tatum will sign the transaction with the managed private key connected to the caller address. This is applicable only for paid mainnet plans and all testnet plans. Keep in mind that the caller address must have enough access right to perform the action in the smart contract method.
\nProviding 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.
\nFor 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.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:54 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/ethereum-1/ethblockchaintransfer.md b/v1.0/Blockchain/ethereum-1/ethblockchaintransfer.md deleted file mode 100644 index 85b6e1c1..00000000 --- a/v1.0/Blockchain/ethereum-1/ethblockchaintransfer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send ETH or fungible tokens (ERC-20) from account to account" -slug: "ethblockchaintransfer" -excerpt: "2 credits per API call
\nSend ETH or Tatum-supported fungible tokens (ERC-20) from account to account.
\nNOTE: Sending the fungible tokens is supported only on the mainnet.
\nSigning a transaction
\nWhen sending ETH, 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.
\nFor 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.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/ethereum-1/ethbroadcast.md b/v1.0/Blockchain/ethereum-1/ethbroadcast.md deleted file mode 100644 index 462d15e8..00000000 --- a/v1.0/Blockchain/ethereum-1/ethbroadcast.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Broadcast signed Ethereum transaction" -slug: "ethbroadcast" -excerpt: "2 credits per API call
\nBroadcast signed transaction to Ethereum blockchain. This method is used internally from Tatum KMS or Tatum client libraries.\nIt is possible to create custom signing mechanism and use this method only for broadcasting data to the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:54 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/ethereum-1/ethgenerateaddress.md b/v1.0/Blockchain/ethereum-1/ethgenerateaddress.md deleted file mode 100644 index 3147146e..00000000 --- a/v1.0/Blockchain/ethereum-1/ethgenerateaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Ethereum account address from Extended public key" -slug: "ethgenerateaddress" -excerpt: "Generates an Ethereum account deposit address from an Extended public key. The deposit address is generated for the specific index - each extended public key can generate\nup to 2^31 addresses starting from index 0 until 2^31 - 1.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:53 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/ethereum-1/ethgenerateaddressprivatekey.md b/v1.0/Blockchain/ethereum-1/ethgenerateaddressprivatekey.md deleted file mode 100644 index 161ee03d..00000000 --- a/v1.0/Blockchain/ethereum-1/ethgenerateaddressprivatekey.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Ethereum private key" -slug: "ethgenerateaddressprivatekey" -excerpt: "Generates the private key of an address from a mnemonic for a given derivation path index. The private key is generated for the specific index - each mnemonic\ncan generate up to 2^32 private keys starting from index 0 until 2^31 - 1.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/ethereum-1/ethgeneratewallet.md b/v1.0/Blockchain/ethereum-1/ethgeneratewallet.md deleted file mode 100644 index 51849991..00000000 --- a/v1.0/Blockchain/ethereum-1/ethgeneratewallet.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Ethereum wallet" -slug: "ethgeneratewallet" -excerpt: "Tatum supports BIP44 HD wallets. Because they can generate 2^31 addresses from 1 mnemonic phrase, they are very convenient and secure. A mnemonic phrase consists of 24 special words in a defined order and can restore access to all generated addresses and private keys.
Each address is identified by 3 main values:
Tatum follows the BIP44 specification and generates for Ethereum wallets with the derivation path m/44'/60'/0'/0. More about BIP44 HD wallets can be found here - https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki.\nGenerates a BIP44 compatible Ethereum wallet.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:53 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/ethereum-1/ethgetbalance.md b/v1.0/Blockchain/ethereum-1/ethgetbalance.md deleted file mode 100644 index eec8aa76..00000000 --- a/v1.0/Blockchain/ethereum-1/ethgetbalance.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get the ETH balance of an Ethereum account" -slug: "ethgetbalance" -excerpt: "1 credit per API call
\nGet the balance of ETH of an Ethereum account.
\nTo get the balance of tokens, use the APIs for getting the balance of fungible tokens (ERC-20) and NFTs (ERC-721).
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:54 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/ethereum-1/ethgetblock.md b/v1.0/Blockchain/ethereum-1/ethgetblock.md deleted file mode 100644 index aa806451..00000000 --- a/v1.0/Blockchain/ethereum-1/ethgetblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Ethereum block by hash" -slug: "ethgetblock" -excerpt: "Gets an Ethereum block-by-block hash or block number.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:54 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/ethereum-1/ethgetcurrentblock.md b/v1.0/Blockchain/ethereum-1/ethgetcurrentblock.md deleted file mode 100644 index 2de59eed..00000000 --- a/v1.0/Blockchain/ethereum-1/ethgetcurrentblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get current block number" -slug: "ethgetcurrentblock" -excerpt: "Gets the current Ethereum block number. This is the number of the latest block in the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:54 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/ethereum-1/ethgetinternaltransactionbyaddress.md b/v1.0/Blockchain/ethereum-1/ethgetinternaltransactionbyaddress.md deleted file mode 100644 index bb92edc5..00000000 --- a/v1.0/Blockchain/ethereum-1/ethgetinternaltransactionbyaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Ethereum internal transactions by address" -slug: "ethgetinternaltransactionbyaddress" -excerpt: "Get Ethereum internal transactions by address.
1 credit per API call
\nGet Ethereum transaction by transaction hash.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:54 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/ethereum-1/ethgettransactionbyaddress.md b/v1.0/Blockchain/ethereum-1/ethgettransactionbyaddress.md deleted file mode 100644 index 6b43dd2b..00000000 --- a/v1.0/Blockchain/ethereum-1/ethgettransactionbyaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Ethereum transactions by address" -slug: "ethgettransactionbyaddress" -excerpt: "This endpoint is deprecated. Do not use it.
\nGet Ethereum transactions by address. This includes incoming and outgoing transactions for the address.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:54 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/ethereum-1/ethgettransactioncount.md b/v1.0/Blockchain/ethereum-1/ethgettransactioncount.md deleted file mode 100644 index faa04ed1..00000000 --- a/v1.0/Blockchain/ethereum-1/ethgettransactioncount.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get count of outgoing Ethereum transactions" -slug: "ethgettransactioncount" -excerpt: "Get a number of outgoing Ethereum transactions for the address. When a transaction is sent, there can be multiple outgoing transactions,\nwhich are not yet processed by the blockchain. To distinguish between them, there is a counter called a nonce, which represents\nthe order of the transaction in the list of outgoing transactions.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/ethereum-1/ethweb3driver.md b/v1.0/Blockchain/ethereum-1/ethweb3driver.md deleted file mode 100644 index d20b8041..00000000 --- a/v1.0/Blockchain/ethereum-1/ethweb3driver.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Web3 HTTP driver" -slug: "ethweb3driver" -excerpt: "2 credits per API call
\nThis endpoint is deprecated. Use the HTTP-based JSON RPC driver instead.
Use this endpoint URL as an http-based web3 driver to connect directly to the Ethereum node provided by Tatum.\nTo learn more about Ethereum Web3, visit the Ethereum developers' guide.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:53 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/flow.md b/v1.0/Blockchain/flow.md deleted file mode 100644 index 6649aab2..00000000 --- a/v1.0/Blockchain/flow.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Flow" -slug: "flow" -excerpt: "" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/flow/flowaddpubkeytoaddress.md b/v1.0/Blockchain/flow/flowaddpubkeytoaddress.md deleted file mode 100644 index f4039449..00000000 --- a/v1.0/Blockchain/flow/flowaddpubkeytoaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Add public key to Flow address" -slug: "flowaddpubkeytoaddress" -excerpt: "Add public key to existing Flow blockchain addresses. Private key for that public key can be used for signing transaction.\nThere are two possibilites how the transaction on the blockchain can be created:\n
Create Flow blockchain addresses from public key. This will generate address on the blockchain with public key. Private key for that public key can be used for signing transaction.\nThere are two possibilites how the transaction on the blockchain can be created:\n
Generate Flow address from Extended public key. This operation internally creates public key and assigns it to the newly created address on the blockchain.\nThere is minimal amount, which must be sent to the FLOW address during creation - 0.001 FLOW, which will be used from Tatum service account.
\nThis operation is allowed on any Testnet plan and only on Paid Mainnet plans.\nPublic key is generated for the specific index - each extended public key can generate up to 2^31 addresses starting from index 0 until 2^31 - 1.
Generate Flow public key from Extended public key. This key is added to the address on the blockchain and can control the funds there. Public key is generated for the specific index - each extended public key can generate\nup to 2^31 addresses starting from index 0 until 2^31 - 1.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/flow/flowgeneratepubkeyprivatekey.md b/v1.0/Blockchain/flow/flowgeneratepubkeyprivatekey.md deleted file mode 100644 index e81f6b24..00000000 --- a/v1.0/Blockchain/flow/flowgeneratepubkeyprivatekey.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Flow private key" -slug: "flowgeneratepubkeyprivatekey" -excerpt: "Generate private key for address from mnemonic for given derivation path index. Private key is generated for the specific index - each mnemonic\ncan generate up to 2^32 private keys starting from index 0 until 2^31 - 1.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:57 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/flow/flowgeneratewallet.md b/v1.0/Blockchain/flow/flowgeneratewallet.md deleted file mode 100644 index 14f9ec7f..00000000 --- a/v1.0/Blockchain/flow/flowgeneratewallet.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Flow wallet" -slug: "flowgeneratewallet" -excerpt: "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 Dogecoin wallet with derivation path m'/44'/3'/0'/0. More about BIP44 HD wallets can be found here - https://github.com/litecoin/bips/blob/master/bip-0044.mediawiki.\nGenerate BIP44 compatible Dogecoin wallet.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:57 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/flow/flowgetaccount.md b/v1.0/Blockchain/flow/flowgetaccount.md deleted file mode 100644 index f59cafb3..00000000 --- a/v1.0/Blockchain/flow/flowgetaccount.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get the balance of a Flow account" -slug: "flowgetaccount" -excerpt: "Get Flow account details.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:58 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/flow/flowgetblock.md b/v1.0/Blockchain/flow/flowgetblock.md deleted file mode 100644 index 586dded2..00000000 --- a/v1.0/Blockchain/flow/flowgetblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Flow Block by hash or height" -slug: "flowgetblock" -excerpt: "Get Flow Block detail by block hash or height.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:57 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/flow/flowgetblockchaininfo.md b/v1.0/Blockchain/flow/flowgetblockchaininfo.md deleted file mode 100644 index 199b3f06..00000000 --- a/v1.0/Blockchain/flow/flowgetblockchaininfo.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Flow current block number" -slug: "flowgetblockchaininfo" -excerpt: "Get Flow current block number.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/flow/flowgetblockevents.md b/v1.0/Blockchain/flow/flowgetblockevents.md deleted file mode 100644 index 3e649753..00000000 --- a/v1.0/Blockchain/flow/flowgetblockevents.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Flow events from blocks" -slug: "flowgetblockevents" -excerpt: "Get Flow events from block.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/flow/flowgetrawtransaction.md b/v1.0/Blockchain/flow/flowgetrawtransaction.md deleted file mode 100644 index 93b3bbc2..00000000 --- a/v1.0/Blockchain/flow/flowgetrawtransaction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Flow Transaction by hash" -slug: "flowgetrawtransaction" -excerpt: "Get Flow Transaction detail by transaction hash.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:58 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/flow/flowtransferblockchain.md b/v1.0/Blockchain/flow/flowtransferblockchain.md deleted file mode 100644 index 3d13987f..00000000 --- a/v1.0/Blockchain/flow/flowtransferblockchain.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send Flow to blockchain addresses" -slug: "flowtransferblockchain" -excerpt: "Send Flow or FUSD to blockchain addresses. Tatum covers the fee connected to the transaction costs in subscription credits. This operation can be done on mainnet only for paid plans.
\nThere are two possibilites how the transaction on the blockchain can be created:\n
Send arbitrary blockchain transaction to FLOW blockchain. Tatum covers the fee connected to the transaction costs in subscription credits. This operation can be done on mainnet only for paid plans.
\nThere are two possibilites how the transaction on the blockchain can be created:\n
2 credits per API call
\nInvoke a method in an existing smart contract on Harmony.
\nYou can call a read-only or write method.
\nTroubleshooting a failed transaction
\nTatum ensures that this API works against the blockchain (accesses the blockchain, finds the specified smart contract, and executes the specified ABI method with the provided parameters).
However, because this API can be run against any smart contract on the blockchain, Tatum cannot in any way guarantee that the method itself will be executed successfully.
If you have issues with invoking the method, refer to the user documentation for this method, or contact the author of the smart contract.
\nFor more information about invoking methods in smart contracts, see this article on our Support Portal.
\nSigning a transaction
\nWhen 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.
\nFor 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.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/harmony/oneblockchaintransfer.md b/v1.0/Blockchain/harmony/oneblockchaintransfer.md deleted file mode 100644 index 9022f6a4..00000000 --- a/v1.0/Blockchain/harmony/oneblockchaintransfer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send ONE from account to account" -slug: "oneblockchaintransfer" -excerpt: "2 credits per API call
\nSend ONE from account to account.
\nThe default shard 0 is used for the sender and the recipient.
Signing a transaction
\nWhen sending ONE, 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.
\nFor 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.
\nAlternatively, using the Tatum client library for supported languages." -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/harmony/onebroadcast.md b/v1.0/Blockchain/harmony/onebroadcast.md deleted file mode 100644 index 958e3a78..00000000 --- a/v1.0/Blockchain/harmony/onebroadcast.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Broadcast signed ONE transaction" -slug: "onebroadcast" -excerpt: "2 credits per API call
\nBroadcast signed transaction to ONE blockchain. This method is used internally from Tatum KMS or Tatum client libraries.\nIt is possible to create custom signing mechanism and use this method only for broadcasting data to the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:11 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/harmony/oneformataddress.md b/v1.0/Blockchain/harmony/oneformataddress.md deleted file mode 100644 index 420da7bc..00000000 --- a/v1.0/Blockchain/harmony/oneformataddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Transform HEX address to Bech32 ONE address format" -slug: "oneformataddress" -excerpt: "1 credit per API call
\nTransform HEX address to Bech32 format with one prefix.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/harmony/onegenerateaddress.md b/v1.0/Blockchain/harmony/onegenerateaddress.md deleted file mode 100644 index 5142cd8b..00000000 --- a/v1.0/Blockchain/harmony/onegenerateaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate ONE account address from Extended public key" -slug: "onegenerateaddress" -excerpt: "1 credit per API call
\nGenerate ONE account deposit address from Extended public key. Deposit address is generated for the specific index - each extended public key can generate\nup to 2^31 addresses starting from index 0 until 2^31.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/harmony/onegenerateaddressprivatekey.md b/v1.0/Blockchain/harmony/onegenerateaddressprivatekey.md deleted file mode 100644 index b74a1ab8..00000000 --- a/v1.0/Blockchain/harmony/onegenerateaddressprivatekey.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate ONE private key" -slug: "onegenerateaddressprivatekey" -excerpt: "1 credit per API call
\nGenerate private key of address from mnemonic for given derivation path index. Private key is generated for the specific index - each mnemonic\ncan generate up to 2^31 private keys starting from index 0 until 2^31.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/harmony/onegeneratewallet.md b/v1.0/Blockchain/harmony/onegeneratewallet.md deleted file mode 100644 index ce6ce407..00000000 --- a/v1.0/Blockchain/harmony/onegeneratewallet.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate ONE wallet" -slug: "onegeneratewallet" -excerpt: "1 credit per API call
\nTatum 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 ONE wallet with derivation path m'/44'/60'/0'/0. More about BIP44 HD wallets can be found here - https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki.\nGenerate BIP44 compatible ONE wallet.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/harmony/onegetbalance.md b/v1.0/Blockchain/harmony/onegetbalance.md deleted file mode 100644 index e9e9af3e..00000000 --- a/v1.0/Blockchain/harmony/onegetbalance.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get ONE Account balance" -slug: "onegetbalance" -excerpt: "1 credit per API call
\nGet ONE account balance in ONE. This method does not prints any balance of the HRM20 or HRM721 tokens on the account.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/harmony/onegetblock.md b/v1.0/Blockchain/harmony/onegetblock.md deleted file mode 100644 index 6a57dc40..00000000 --- a/v1.0/Blockchain/harmony/onegetblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get ONE block by hash" -slug: "onegetblock" -excerpt: "1 credit per API call
\nGet ONE block by block hash or block number.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/harmony/onegetcurrentblock.md b/v1.0/Blockchain/harmony/onegetcurrentblock.md deleted file mode 100644 index 2cbf6f22..00000000 --- a/v1.0/Blockchain/harmony/onegetcurrentblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get current block number" -slug: "onegetcurrentblock" -excerpt: "1 credit per API call
\nGet ONE current block number. This is the number of the latest block in the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/harmony/onegettransaction.md b/v1.0/Blockchain/harmony/onegettransaction.md deleted file mode 100644 index 0172ef3f..00000000 --- a/v1.0/Blockchain/harmony/onegettransaction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get ONE Transaction" -slug: "onegettransaction" -excerpt: "2 credits per API call
\nGet ONE transaction by transaction hash.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/harmony/onegettransactioncount.md b/v1.0/Blockchain/harmony/onegettransactioncount.md deleted file mode 100644 index 6f44bb2d..00000000 --- a/v1.0/Blockchain/harmony/onegettransactioncount.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get count of outgoing ONE transactions" -slug: "onegettransactioncount" -excerpt: "1 credit per API call
\nGet a number of outgoing ONE transactions for the address. When a transaction is sent, there can be multiple outgoing transactions,\nwhich are not yet processed by the blockchain. To distinguish between them, there is a counter called a nonce, which represents\nthe order of the transaction in the list of outgoing transactions.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/harmony/oneweb3driver.md b/v1.0/Blockchain/harmony/oneweb3driver.md deleted file mode 100644 index 12655019..00000000 --- a/v1.0/Blockchain/harmony/oneweb3driver.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Web3 HTTP driver" -slug: "oneweb3driver" -excerpt: "2 credits per API call
\nThis 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 ONE node provided by Tatum.\nTo learn more about ONE Web3, visit the ONE developer's guide.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/klaytn.md b/v1.0/Blockchain/klaytn.md deleted file mode 100644 index c99ccc16..00000000 --- a/v1.0/Blockchain/klaytn.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Klaytn" -slug: "klaytn" -excerpt: "" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/klaytn/klaytnblockchainsmartcontractinvocation.md b/v1.0/Blockchain/klaytn/klaytnblockchainsmartcontractinvocation.md deleted file mode 100644 index 00628eb7..00000000 --- a/v1.0/Blockchain/klaytn/klaytnblockchainsmartcontractinvocation.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Invoke a method in a smart contract on Klaytn" -slug: "klaytnblockchainsmartcontractinvocation" -excerpt: "2 credits per API call
\nInvoke a method in an existing smart contract on Klaytn.
\nYou can call a read-only or write method.
\nTroubleshooting a failed transaction
\nTatum ensures that this API works against the blockchain (accesses the blockchain, finds the specified smart contract, and executes the specified ABI method with the provided parameters).
However, because this API can be run against any smart contract on the blockchain, Tatum cannot in any way guarantee that the method itself will be executed successfully.
If you have issues with invoking the method, refer to the user documentation for this method, or contact the author of the smart contract.
\nFor more information about invoking methods in smart contracts, see this article on our Support Portal.
\nSigning a transaction
\nWhen 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.
\nFor 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.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:04 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/klaytn/klaytnblockchaintransfer.md b/v1.0/Blockchain/klaytn/klaytnblockchaintransfer.md deleted file mode 100644 index 0d1da4b6..00000000 --- a/v1.0/Blockchain/klaytn/klaytnblockchaintransfer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send KLAY from account to account" -slug: "klaytnblockchaintransfer" -excerpt: "2 credits per API call
\nSend KLAY from account to account.
\n
Signing a transaction
\nWhen sending KLAY, 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.
\nProviding 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.
\nFor 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.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:04 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/klaytn/klaytnbroadcast.md b/v1.0/Blockchain/klaytn/klaytnbroadcast.md deleted file mode 100644 index 31f5c0f0..00000000 --- a/v1.0/Blockchain/klaytn/klaytnbroadcast.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Broadcast signed Klaytn transaction" -slug: "klaytnbroadcast" -excerpt: "2 credits per API call
\nBroadcast signed transaction to Klaytn blockchain. This method is used internally from Tatum KMS or Tatum client libraries.\nIt is possible to create custom signing mechanism and use this method only for broadcasting data to the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:05 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/klaytn/klaytngenerateaddress.md b/v1.0/Blockchain/klaytn/klaytngenerateaddress.md deleted file mode 100644 index a77b5a34..00000000 --- a/v1.0/Blockchain/klaytn/klaytngenerateaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Klaytn account address from Extended public key" -slug: "klaytngenerateaddress" -excerpt: "1 credit per API call
\nGenerate Klaytn account deposit address from Extended public key. Deposit address is generated for the specific index - each extended public key can generate\nup to 2^31 addresses starting from index 0 until 2^31.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/klaytn/klaytngenerateaddressprivatekey.md b/v1.0/Blockchain/klaytn/klaytngenerateaddressprivatekey.md deleted file mode 100644 index 3677d5f1..00000000 --- a/v1.0/Blockchain/klaytn/klaytngenerateaddressprivatekey.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Klaytn private key" -slug: "klaytngenerateaddressprivatekey" -excerpt: "1 credit per API call
\nGenerate private key of address from mnemonic for given derivation path index. Private key is generated for the specific index - each mnemonic\ncan generate up to 2^31 private keys starting from index 0 until 2^31.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:04 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/klaytn/klaytngeneratewallet.md b/v1.0/Blockchain/klaytn/klaytngeneratewallet.md deleted file mode 100644 index 6055032d..00000000 --- a/v1.0/Blockchain/klaytn/klaytngeneratewallet.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Klaytn wallet" -slug: "klaytngeneratewallet" -excerpt: "1 credit per API call
\nTatum 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 Klaytn wallet with derivation path m'/44'/966'/0'/0. More about BIP44 HD wallets can be found here - https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki.\nGenerate BIP44 compatible Klaytn wallet.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:04 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/klaytn/klaytngetbalance.md b/v1.0/Blockchain/klaytn/klaytngetbalance.md deleted file mode 100644 index b46662bc..00000000 --- a/v1.0/Blockchain/klaytn/klaytngetbalance.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Klaytn Account balance" -slug: "klaytngetbalance" -excerpt: "1 credit per API call
\nGet Klaytn account balance in KLAY. This method does not prints any balance of the ERC20 or ERC721 tokens on the account.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:04 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/klaytn/klaytngetblock.md b/v1.0/Blockchain/klaytn/klaytngetblock.md deleted file mode 100644 index 885ef3b4..00000000 --- a/v1.0/Blockchain/klaytn/klaytngetblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Klaytn block by hash" -slug: "klaytngetblock" -excerpt: "1 credit per API call
\nGet Klaytn block by block hash or block number.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/klaytn/klaytngetcurrentblock.md b/v1.0/Blockchain/klaytn/klaytngetcurrentblock.md deleted file mode 100644 index cf3aa47a..00000000 --- a/v1.0/Blockchain/klaytn/klaytngetcurrentblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get current block number" -slug: "klaytngetcurrentblock" -excerpt: "1 credit per API call
\nGet Klaytn current block number. This is the number of the latest block in the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:04 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/klaytn/klaytngettransaction.md b/v1.0/Blockchain/klaytn/klaytngettransaction.md deleted file mode 100644 index 0a12b381..00000000 --- a/v1.0/Blockchain/klaytn/klaytngettransaction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Klaytn Transaction" -slug: "klaytngettransaction" -excerpt: "2 credits per API call
\nGet Klaytn transaction by transaction hash.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/klaytn/klaytngettransactioncount.md b/v1.0/Blockchain/klaytn/klaytngettransactioncount.md deleted file mode 100644 index 85b9b726..00000000 --- a/v1.0/Blockchain/klaytn/klaytngettransactioncount.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get count of outgoing Klaytn transactions" -slug: "klaytngettransactioncount" -excerpt: "1 credit per API call
\nGet a number of outgoing Klaytn 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.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:04 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/klaytn/klaytnweb3driver.md b/v1.0/Blockchain/klaytn/klaytnweb3driver.md deleted file mode 100644 index e184e5b3..00000000 --- a/v1.0/Blockchain/klaytn/klaytnweb3driver.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Web3 HTTP driver" -slug: "klaytnweb3driver" -excerpt: "2 credits per API call
\nThis 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 Klaytn node provided by Tatum.\nTo learn more about Klaytn Web3, visit the Klaytn developer's guide.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:04 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/kucoin.md b/v1.0/Blockchain/kucoin.md deleted file mode 100644 index d54a3ba9..00000000 --- a/v1.0/Blockchain/kucoin.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "KuCoin" -slug: "kucoin" -excerpt: "" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/kucoin/kcsblockchainsmartcontractinvocation.md b/v1.0/Blockchain/kucoin/kcsblockchainsmartcontractinvocation.md deleted file mode 100644 index 7386f4d0..00000000 --- a/v1.0/Blockchain/kucoin/kcsblockchainsmartcontractinvocation.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Invoke a method in a smart contract on KuCoin Community Chain" -slug: "kcsblockchainsmartcontractinvocation" -excerpt: "2 credits per API call
\nInvoke a method in an existing smart contract on KuCoin Community Chain.
\nYou can call a read-only or write method.
\nTroubleshooting a failed transaction
\nTatum ensures that this API works against the blockchain (accesses the blockchain, finds the specified smart contract, and executes the specified ABI method with the provided parameters).
However, because this API can be run against any smart contract on the blockchain, Tatum cannot in any way guarantee that the method itself will be executed successfully.
If you have issues with invoking the method, refer to the user documentation for this method, or contact the author of the smart contract.
\nFor more information about invoking methods in smart contracts, see this article on our Support Portal.
\nSigning a transaction
\nWhen 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.
\nFor 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.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/kucoin/kcsblockchaintransfer.md b/v1.0/Blockchain/kucoin/kcsblockchaintransfer.md deleted file mode 100644 index 570a6ba3..00000000 --- a/v1.0/Blockchain/kucoin/kcsblockchaintransfer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send KCS from account to account" -slug: "kcsblockchaintransfer" -excerpt: "2 credits per API call
\nSend KCS from account to account.
\n
Signing a transaction
\nWhen sending KCS, 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.
\nProviding 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.
\nFor 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.
\nAlternatively, using the Tatum client library for supported languages." -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/kucoin/kcsbroadcast.md b/v1.0/Blockchain/kucoin/kcsbroadcast.md deleted file mode 100644 index 9007392a..00000000 --- a/v1.0/Blockchain/kucoin/kcsbroadcast.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Broadcast signed Kcs transaction" -slug: "kcsbroadcast" -excerpt: "2 credits per API call
\nBroadcast signed transaction to Kcs blockchain. This method is used internally from Tatum KMS or Tatum client libraries.\nIt is possible to create custom signing mechanism and use this method only for broadcasting data to the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/kucoin/kcsgenerateaddress.md b/v1.0/Blockchain/kucoin/kcsgenerateaddress.md deleted file mode 100644 index 0046f0a2..00000000 --- a/v1.0/Blockchain/kucoin/kcsgenerateaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Kcs account address from Extended public key" -slug: "kcsgenerateaddress" -excerpt: "1 credit per API call
\nGenerate Kcs account deposit address from Extended public key. Deposit address is generated for the specific index - each extended public key can generate\nup to 2^31 addresses starting from index 0 until 2^31.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:09 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/kucoin/kcsgenerateaddressprivatekey.md b/v1.0/Blockchain/kucoin/kcsgenerateaddressprivatekey.md deleted file mode 100644 index 55236970..00000000 --- a/v1.0/Blockchain/kucoin/kcsgenerateaddressprivatekey.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Kcs private key" -slug: "kcsgenerateaddressprivatekey" -excerpt: "1 credit per API call
\nGenerate private key of address from mnemonic for given derivation path index. Private key is generated for the specific index - each mnemonic\ncan generate up to 2^31 private keys starting from index 0 until 2^31.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:09 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/kucoin/kcsgeneratewallet.md b/v1.0/Blockchain/kucoin/kcsgeneratewallet.md deleted file mode 100644 index c6b4bfe1..00000000 --- a/v1.0/Blockchain/kucoin/kcsgeneratewallet.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Kcs wallet" -slug: "kcsgeneratewallet" -excerpt: "1 credit per API call
\nTatum 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 Kcs wallet with derivation path m'/44'/966'/0'/0. More about BIP44 HD wallets can be found here - https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki.\nGenerate BIP44 compatible Kcs wallet.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/kucoin/kcsgetbalance.md b/v1.0/Blockchain/kucoin/kcsgetbalance.md deleted file mode 100644 index aaead124..00000000 --- a/v1.0/Blockchain/kucoin/kcsgetbalance.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Kcs Account balance" -slug: "kcsgetbalance" -excerpt: "1 credit per API call
\nGet Kcs account balance in KCS. This method does not prints any balance of the ERC20 or ERC721 tokens on the account.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/kucoin/kcsgetblock.md b/v1.0/Blockchain/kucoin/kcsgetblock.md deleted file mode 100644 index 1bddf013..00000000 --- a/v1.0/Blockchain/kucoin/kcsgetblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Kcs block by hash" -slug: "kcsgetblock" -excerpt: "1 credit per API call
\nGet Kcs block by block hash or block number.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:09 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/kucoin/kcsgetcurrentblock.md b/v1.0/Blockchain/kucoin/kcsgetcurrentblock.md deleted file mode 100644 index 0d88dd3c..00000000 --- a/v1.0/Blockchain/kucoin/kcsgetcurrentblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get current block number" -slug: "kcsgetcurrentblock" -excerpt: "1 credit per API call
\nGet Kcs current block number. This is the number of the latest block in the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/kucoin/kcsgettransaction.md b/v1.0/Blockchain/kucoin/kcsgettransaction.md deleted file mode 100644 index 3d28ecbb..00000000 --- a/v1.0/Blockchain/kucoin/kcsgettransaction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Kcs Transaction" -slug: "kcsgettransaction" -excerpt: "2 credits per API call
\nGet Kcs transaction by transaction hash.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:09 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/kucoin/kcsgettransactioncount.md b/v1.0/Blockchain/kucoin/kcsgettransactioncount.md deleted file mode 100644 index 6fca2263..00000000 --- a/v1.0/Blockchain/kucoin/kcsgettransactioncount.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get count of outgoing Kcs transactions" -slug: "kcsgettransactioncount" -excerpt: "1 credit per API call
\nGet a number of outgoing Kcs transactions for the address. When a transaction is sent, there can be multiple outgoing transactions,\nwhich are not yet processed by the blockchain. To distinguish between them, there is a counter called a nonce, which represents\nthe order of the transaction in the list of outgoing transactions.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/kucoin/kcsweb3driver.md b/v1.0/Blockchain/kucoin/kcsweb3driver.md deleted file mode 100644 index 4f1ff40d..00000000 --- a/v1.0/Blockchain/kucoin/kcsweb3driver.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Web3 HTTP driver" -slug: "kcsweb3driver" -excerpt: "2 credits per API call
\nThis 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 Kcs node provided by Tatum.\nTo learn more about Kcs Web3, visit the Kcs developer's guide.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:09 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/litecoin.md b/v1.0/Blockchain/litecoin.md deleted file mode 100644 index 856d0700..00000000 --- a/v1.0/Blockchain/litecoin.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Litecoin" -slug: "litecoin" -excerpt: "" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/litecoin/ltcbroadcast.md b/v1.0/Blockchain/litecoin/ltcbroadcast.md deleted file mode 100644 index d5f76fe4..00000000 --- a/v1.0/Blockchain/litecoin/ltcbroadcast.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Broadcast signed Litecoin transaction" -slug: "ltcbroadcast" -excerpt: "Broadcast signed transaction to Litecoin blockchain. This method is used internally from Tatum KMS or Tatum client libraries.\nIt is possible to create custom signing mechanism and use this method only for broadcasting data to the blockchain.
\nGenerate Litecoin deposit address from Extended public key. Deposit address is generated for the specific index - each extended public key can generate\nup to 2^31 addresses starting from index 0 until 2^31 - 1.
\nGenerate private key for address from mnemonic for given derivation path index. Private key is generated for the specific index - each mnemonic\ncan generate up to 2^32 private keys starting from index 0 until 2^31 - 1.
\nTatum 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 Litecoin wallet with derivation path m'/44'/2'/0'/0. More about BIP44 HD wallets can be found here - https://github.com/litecoin/bips/blob/master/bip-0044.mediawiki.\nGenerate BIP44 compatible Litecoin wallet.
\nGet Litecoin Balance of the address.
\n50 credits per API call
\nGet the balance of multiple Litecoin addresses, up to 30.
\nThe API returns the balance only if the address has up to 50,000 UTXOs (Unspent Transaction Outputs). For an address with more than 50,000 UTXOs, the API returns an error with the 403 response code.
Get Litecoin Block detail by block hash or height.
\nGet Litecoin Blockchain Information. Obtain basic info like testnet / mainnet version of the chain, current block number and it's hash.
\nGet Litecoin Block hash. Returns hash of the block to get the block detail.
Get Litecoin Transaction ids in the mempool.
\nGet Litecoin Transaction detail by transaction hash.
\nGet Litecoin Transaction by address.
\n5 credits per API call
\nGet information about a transaction output in a transaction and check whether this output is a UTXO or has been spent.
\n\"UTXO\" stands for \"Unspent Transaction Output\". A UTXO is the amount of LTC that remains at a Litecoin address after a cryptocurrency transaction involving this address has been performed. The UTXO can then be used as input for a new cryptocurrency transaction. For more information the UTXO, see the Bitcoin user documentation.
\n404 response code.2 credits per API call
\nThis endpoint is deprecated. Use the HTTP-based JSON RPC driver instead.
Use this endpoint URL as an http-based JSON RPC driver to connect directly to the node provided by Tatum.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:55 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/litecoin/ltctransferblockchain.md b/v1.0/Blockchain/litecoin/ltctransferblockchain.md deleted file mode 100644 index 2f18c2b9..00000000 --- a/v1.0/Blockchain/litecoin/ltctransferblockchain.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send LTC to Litecoin addresses" -slug: "ltctransferblockchain" -excerpt: "10 credits per API call
\nSend LTC to blockchain addresses.
\nLitecoin transactions are based on UTXOs. \"UTXO\" stands for \"Unspent Transaction Output\". A UTXO is the amount of LTC that remains at a Litecoin address after a cryptocurrency transaction involving this address has been performed. The UTXO can then be used as input for a new cryptocurrency transaction. For more information about the UTXO, see the Bitcoin user documentation. To check UTXOs in a transaction, see the API for getting information about a transaction output (UTXO) in a Litecoin transaction.
\nYou can build a LTC transaction by one of the following methods:
\nLtcTransactionAddress or LtcTransactionAddressKMS schema of the request body.LtcTransactionFromUTXO or LtcTransactionFromUTXOKMS schema of the request body.When an UTXO is entered into a transaction, the whole UTXO amount is included and must be spent. For example, address A receives two transactions, T1 with 1 LTC and T2 with 2 LTC. A transaction that consumes the UTXOs from both T1 and T2 will have an available amount of 3 LTC to spend:1 LTC (from T1) + 2 LTC (from T2) = 3 LTC (to spend in total)
You can send the assets to one or multiple recipients in one transaction. If you send the assets to multiple addresses, each address must have its own amount to receive.
\nPaying the gas fee and receiving the change
\nWhen the amount that the recipients should receive is lower than the amount from the UTXOs, the difference between these two amounts is by default used as the gas fee for the transaction. Because this amount may be considerable and you may not want to spend it all on the gas fee, you can explicitly specify the fee amount and the blockchain address where any extra funds remaining after covering the fee will be sent (the fee and changeAddress parameters in the request body, correspondingly).
Signing a transaction
\nWhen sending LTC, 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.
\nFor 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.
\n2 credits per API call
\nInvoke a method in an existing smart contract on Polygon.
\nYou can call a read-only or write method.
\nTroubleshooting a failed transaction
\nTatum ensures that this API works against the blockchain (accesses the blockchain, finds the specified smart contract, and executes the specified ABI method with the provided parameters).
However, because this API can be run against any smart contract on the blockchain, Tatum cannot in any way guarantee that the method itself will be executed successfully.
If you have issues with invoking the method, refer to the user documentation for this method, or contact the author of the smart contract.
\nFor more information about invoking methods in smart contracts, see this article on our Support Portal.
\nSigning a transaction
\nWhen 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.
If caller field is present instead of the private key, Tatum will sign the transaction with the managed private key connected to the caller address. This is applicable only for paid mainnet plans and all testnet plans. Keep in mind that the caller address must have enough access right to perform the action in the smart contract method.
\nProviding 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.
\nFor 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.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:04 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/polygon-1/polygonblockchaintransfer.md b/v1.0/Blockchain/polygon-1/polygonblockchaintransfer.md deleted file mode 100644 index a96b9a08..00000000 --- a/v1.0/Blockchain/polygon-1/polygonblockchaintransfer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send MATIC from account to account" -slug: "polygonblockchaintransfer" -excerpt: "2 credits per API call
\nSend MATIC from account to account.
\n
Signing a transaction
\nWhen sending MATIC, 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.
\nProviding 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.
\nFor 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.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/polygon-1/polygonbroadcast.md b/v1.0/Blockchain/polygon-1/polygonbroadcast.md deleted file mode 100644 index 50e48e59..00000000 --- a/v1.0/Blockchain/polygon-1/polygonbroadcast.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Broadcast signed Polygon transaction" -slug: "polygonbroadcast" -excerpt: "2 credits per API call
\nBroadcast signed transaction to Polygon blockchain. This method is used internally from Tatum KMS or Tatum client libraries.\nIt is possible to create custom signing mechanism and use this method only for broadcasting data to the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:04 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/polygon-1/polygongenerateaddress.md b/v1.0/Blockchain/polygon-1/polygongenerateaddress.md deleted file mode 100644 index 8b63fce5..00000000 --- a/v1.0/Blockchain/polygon-1/polygongenerateaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Polygon account address from Extended public key" -slug: "polygongenerateaddress" -excerpt: "1 credit per API call
\nGenerate Polygon account deposit address from Extended public key. Deposit address is generated for the specific index - each extended public key can generate\nup to 2^31 addresses starting from index 0 until 2^31.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:03 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/polygon-1/polygongenerateaddressprivatekey.md b/v1.0/Blockchain/polygon-1/polygongenerateaddressprivatekey.md deleted file mode 100644 index ceb6ef52..00000000 --- a/v1.0/Blockchain/polygon-1/polygongenerateaddressprivatekey.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Polygon private key" -slug: "polygongenerateaddressprivatekey" -excerpt: "1 credit per API call
\nGenerate private key of address from mnemonic for given derivation path index. Private key is generated for the specific index - each mnemonic\ncan generate up to 2^31 private keys starting from index 0 until 2^31.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/polygon-1/polygongeneratewallet.md b/v1.0/Blockchain/polygon-1/polygongeneratewallet.md deleted file mode 100644 index 30ff7a4b..00000000 --- a/v1.0/Blockchain/polygon-1/polygongeneratewallet.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Polygon wallet" -slug: "polygongeneratewallet" -excerpt: "1 credit per API call
\nTatum 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 Polygon wallet with derivation path m'/44'/966'/0'/0. More about BIP44 HD wallets can be found here - https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki.\nGenerate BIP44 compatible Polygon wallet.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/polygon-1/polygongetbalance.md b/v1.0/Blockchain/polygon-1/polygongetbalance.md deleted file mode 100644 index b965992c..00000000 --- a/v1.0/Blockchain/polygon-1/polygongetbalance.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Polygon Account balance" -slug: "polygongetbalance" -excerpt: "1 credit per API call
\nGet Polygon account balance in MATIC. This method does not prints any balance of the ERC20 or ERC721 tokens on the account.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:03 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/polygon-1/polygongetblock.md b/v1.0/Blockchain/polygon-1/polygongetblock.md deleted file mode 100644 index f7a0edf8..00000000 --- a/v1.0/Blockchain/polygon-1/polygongetblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Polygon block by hash" -slug: "polygongetblock" -excerpt: "1 credit per API call
\nGet Polygon block by block hash or block number.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:03 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/polygon-1/polygongetcurrentblock.md b/v1.0/Blockchain/polygon-1/polygongetcurrentblock.md deleted file mode 100644 index 09337f9b..00000000 --- a/v1.0/Blockchain/polygon-1/polygongetcurrentblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get current block number" -slug: "polygongetcurrentblock" -excerpt: "1 credit per API call
\nGet Polygon current block number. This is the number of the latest block in the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:03 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/polygon-1/polygongettransaction.md b/v1.0/Blockchain/polygon-1/polygongettransaction.md deleted file mode 100644 index 28d74e85..00000000 --- a/v1.0/Blockchain/polygon-1/polygongettransaction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Polygon Transaction" -slug: "polygongettransaction" -excerpt: "2 credits per API call
\nGet Polygon transaction by transaction hash.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:03 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/polygon-1/polygongettransactionbyaddress.md b/v1.0/Blockchain/polygon-1/polygongettransactionbyaddress.md deleted file mode 100644 index 23bfa34c..00000000 --- a/v1.0/Blockchain/polygon-1/polygongettransactionbyaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Polygon transactions by address" -slug: "polygongettransactionbyaddress" -excerpt: "This endpoint is deprecated. Do not use it.
\n1 credit per API call
\nGet Polygon transactions by address. This includes incoming and outgoing transactions for the address.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:03 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/polygon-1/polygongettransactioncount.md b/v1.0/Blockchain/polygon-1/polygongettransactioncount.md deleted file mode 100644 index 239d9a3d..00000000 --- a/v1.0/Blockchain/polygon-1/polygongettransactioncount.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get count of outgoing Polygon transactions" -slug: "polygongettransactioncount" -excerpt: "1 credit per API call
\nGet a number of outgoing Polygon transactions for the address. When a transaction is sent, there can be multiple outgoing transactions,\nwhich are not yet processed by the blockchain. To distinguish between them, there is a counter called a nonce, which represents\nthe order of the transaction in the list of outgoing transactions.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:03 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/polygon-1/polygonweb3driver.md b/v1.0/Blockchain/polygon-1/polygonweb3driver.md deleted file mode 100644 index 8f943414..00000000 --- a/v1.0/Blockchain/polygon-1/polygonweb3driver.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Web3 HTTP driver" -slug: "polygonweb3driver" -excerpt: "2 credits per API call
\nThis 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 Polygon node provided by Tatum.\nTo learn more about Polygon Web3, visit the Polygon developer's guide.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:03 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/solana.md b/v1.0/Blockchain/solana.md deleted file mode 100644 index 2de1d2ab..00000000 --- a/v1.0/Blockchain/solana.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Solana" -slug: "solana" -excerpt: "" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/solana/solanablockchaintransfer.md b/v1.0/Blockchain/solana/solanablockchaintransfer.md deleted file mode 100644 index c004e015..00000000 --- a/v1.0/Blockchain/solana/solanablockchaintransfer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send SOL from account to account" -slug: "solanablockchaintransfer" -excerpt: "Send SOL from account to account.
\nThis 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.\nNo 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\nor signatureId. PrivateKey should be used only for quick development on testnet versions of blockchain when there is no risk of losing funds. In production,\nTatum KMS should be used for the highest security standards, and signatureId should be present in the request.\nAlternatively, using the Tatum client library for supported languages.\n
Broadcast signed custom transactions to Solana blockchain and waits for transaction confirmation depending on the commitment given. More information about commitment levels here
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:05 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/solana/solanageneratewallet.md b/v1.0/Blockchain/solana/solanageneratewallet.md deleted file mode 100644 index 85d7011b..00000000 --- a/v1.0/Blockchain/solana/solanageneratewallet.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate Solana wallet" -slug: "solanageneratewallet" -excerpt: "Generate Solana private key and account address.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:05 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/solana/solanagetbalance.md b/v1.0/Blockchain/solana/solanagetbalance.md deleted file mode 100644 index 53085337..00000000 --- a/v1.0/Blockchain/solana/solanagetbalance.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Solana Account balance" -slug: "solanagetbalance" -excerpt: "Get Solana account balance in SOL. This method does not prints any balance of the SPL or NFT tokens on the account.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:05 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/solana/solanagetblock.md b/v1.0/Blockchain/solana/solanagetblock.md deleted file mode 100644 index d07270b3..00000000 --- a/v1.0/Blockchain/solana/solanagetblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Solana block by number" -slug: "solanagetblock" -excerpt: "Get Solana block by block hash or block number.
\nYou can find full data description here - https://docs.solana.com/developing/clients/jsonrpc-api#getblock\n
Get Solana current block number. This is the number of the latest block in the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:05 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/solana/solanagettransaction.md b/v1.0/Blockchain/solana/solanagettransaction.md deleted file mode 100644 index 0e404e4b..00000000 --- a/v1.0/Blockchain/solana/solanagettransaction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Solana Transaction" -slug: "solanagettransaction" -excerpt: "Get Solana transaction by transaction hash.
\nYou can find full data description here - https://docs.solana.com/developing/clients/jsonrpc-api#gettransaction\n
2 credits per API call
\nThis endpoint is deprecated. Use the HTTP-based JSON RPC driver instead.
Use this endpoint URL as a http-based JSON RPC driver to connect directly to the Solana node provided by Tatum.\nTo learn more about Solana JSON RPC, visit the Solana developer's guide.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:05 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/stellar.md b/v1.0/Blockchain/stellar.md deleted file mode 100644 index 8c3783c8..00000000 --- a/v1.0/Blockchain/stellar.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Stellar" -slug: "stellar" -excerpt: "" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/stellar/xlmbroadcast.md b/v1.0/Blockchain/stellar/xlmbroadcast.md deleted file mode 100644 index dfd9a055..00000000 --- a/v1.0/Blockchain/stellar/xlmbroadcast.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Broadcast signed XLM transaction" -slug: "xlmbroadcast" -excerpt: "Broadcast signed transaction to XLM blockchain. This method is used internally from Tatum KMS or Tatum client libraries.\nIt is possible to create custom signing mechanism and use this method only for broadcasting data to the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:00 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/stellar/xlmgetaccountinfo.md b/v1.0/Blockchain/stellar/xlmgetaccountinfo.md deleted file mode 100644 index 21b0593d..00000000 --- a/v1.0/Blockchain/stellar/xlmgetaccountinfo.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get XLM Account info" -slug: "xlmgetaccountinfo" -excerpt: "Get XLM Account detail.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:00 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/stellar/xlmgetaccounttx.md b/v1.0/Blockchain/stellar/xlmgetaccounttx.md deleted file mode 100644 index 68d27dce..00000000 --- a/v1.0/Blockchain/stellar/xlmgetaccounttx.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get XLM Account transactions" -slug: "xlmgetaccounttx" -excerpt: "List all XLM account transactions.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/stellar/xlmgetfee.md b/v1.0/Blockchain/stellar/xlmgetfee.md deleted file mode 100644 index da7ac3e2..00000000 --- a/v1.0/Blockchain/stellar/xlmgetfee.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get actual XLM fee" -slug: "xlmgetfee" -excerpt: "Get XLM Blockchain fee in 1/10000000 of XLM (stroop)
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:00 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/stellar/xlmgetlastclosedledger.md b/v1.0/Blockchain/stellar/xlmgetlastclosedledger.md deleted file mode 100644 index 3a3ffcc1..00000000 --- a/v1.0/Blockchain/stellar/xlmgetlastclosedledger.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get XLM Blockchain Information" -slug: "xlmgetlastclosedledger" -excerpt: "Get XLM Blockchain last closed ledger.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:59 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/stellar/xlmgetledger.md b/v1.0/Blockchain/stellar/xlmgetledger.md deleted file mode 100644 index b93ec600..00000000 --- a/v1.0/Blockchain/stellar/xlmgetledger.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get XLM Blockchain Ledger by sequence" -slug: "xlmgetledger" -excerpt: "Get XLM Blockchain ledger for ledger sequence.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:59 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/stellar/xlmgetledgertx.md b/v1.0/Blockchain/stellar/xlmgetledgertx.md deleted file mode 100644 index 0018f480..00000000 --- a/v1.0/Blockchain/stellar/xlmgetledgertx.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get XLM Blockchain Transactions in Ledger" -slug: "xlmgetledgertx" -excerpt: "Get XLM Blockchain transactions in the ledger.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:59 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/stellar/xlmgettransaction.md b/v1.0/Blockchain/stellar/xlmgettransaction.md deleted file mode 100644 index 7d6c3355..00000000 --- a/v1.0/Blockchain/stellar/xlmgettransaction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get XLM Transaction by hash" -slug: "xlmgettransaction" -excerpt: "Get XLM Transaction by transaction hash.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:00 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/stellar/xlmtransferblockchain.md b/v1.0/Blockchain/stellar/xlmtransferblockchain.md deleted file mode 100644 index 1b62213e..00000000 --- a/v1.0/Blockchain/stellar/xlmtransferblockchain.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send XLM from address to address" -slug: "xlmtransferblockchain" -excerpt: "Send XLM from account to account. It is possbile to send native XLM asset, or any other custom asset present on the network.
\nThis 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.\nNo 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\nor signatureId. PrivateKey should be used only for quick development on testnet versions of blockchain when there is no risk of losing funds. In production,\nTatum KMS should be used for the highest security standards, and signatureId should be present in the request.\nAlternatively, using the Tatum client library for supported languages.\n
\n
Create / Update / Delete XLM trust line between accounts to transfer private assets.\nBy creating trustline for the first time, the asset is created automatically and can be used in the transactions.
\nThis 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.\nNo 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\nor signatureId. PrivateKey should be used only for quick development on testnet versions of blockchain when there is no risk of losing funds. In production,\nTatum KMS should be used for the highest security standards, and signatureId should be present in the request.\nAlternatively, using the Tatum client library for supported languages.\n
Generate XLM account. Tatum does not support HD wallet for XLM, only specific address and private key can be generated.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:59 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/tron-1.md b/v1.0/Blockchain/tron-1.md deleted file mode 100644 index 7eaa2e85..00000000 --- a/v1.0/Blockchain/tron-1.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Tron" -slug: "tron-1" -excerpt: "" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/tron-1/generatetronwallet.md b/v1.0/Blockchain/tron-1/generatetronwallet.md deleted file mode 100644 index 429416c4..00000000 --- a/v1.0/Blockchain/tron-1/generatetronwallet.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate a TRON wallet" -slug: "generatetronwallet" -excerpt: "1 credit per API call
\nTatum 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 Bitcoin wallet with derivation path m'/44'/195'/0'/0. More about BIP44 HD wallets can be found here - https://github.com/tron/bips/blob/master/bip-0044.mediawiki.\n Generate BIP44 compatible Tron wallet.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/tron-1/tronaccounttx.md b/v1.0/Blockchain/tron-1/tronaccounttx.md deleted file mode 100644 index 8c3df7eb..00000000 --- a/v1.0/Blockchain/tron-1/tronaccounttx.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get all transactions for a TRON account" -slug: "tronaccounttx" -excerpt: "5 credits per API call
\nGet all transactions for a TRON account.
\nThis API returns up to 200 transactions in one API call. If there are more than 200 transactions for the TRON account, the response body will contain the next parameter with the fingerprint of the transaction that follows the last (200th) transaction in the returned list.
To get the next 200 transactions, make another call using this API, but this time add the next parameter the endpoint URL and set it to the transaction fingerprint from the next parameter in the response, for example:
https://api.tatum.io/v3/tron/transaction/account/{address}?next=81d0524acf5967f3b361e03fd7d141ab511791cd7aad7ae406c4c8d408290991
5 credits per API call
\nGet TRC-20 transactions for a TRON account.
\nThis API returns up to 200 transactions in one API call. If there are more than 200 transactions for the TRON account, the response body will contain the next parameter with the fingerprint of the transaction that follows the last (200th) transaction in the returned list.
To get the next 200 transactions, make another call using this API, but this time add the next parameter the endpoint URL and set it to the transaction fingerprint from the next parameter in the response, for example:
https://api.tatum.io/v3/tron/transaction/account/{address}/trc20?next=81d0524acf5967f3b361e03fd7d141ab511791cd7aad7ae406c4c8d408290991
5 credits per API call
\nBroadcast Tron transaction. This method is used internally from Tatum client libraries.\nIt is possible to create custom signing mechanism and use this method only for broadcasting data to the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:08 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/tron-1/troncreatetrc10.md b/v1.0/Blockchain/tron-1/troncreatetrc10.md deleted file mode 100644 index 2dbbfbd8..00000000 --- a/v1.0/Blockchain/tron-1/troncreatetrc10.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Create a TRC-10 token" -slug: "troncreatetrc10" -excerpt: "10 credits per API call
\nCreate a TRON TRC-10 token.
\nOne TRON account can create only one TRC-10 token. The whole supply of the token is transferred to the issuer's account 100 seconds after the token has been created.
\nSigning a transaction
\nWhen creating a TRC-10 token, 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.
\nFor 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.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/tron-1/troncreatetrc20.md b/v1.0/Blockchain/tron-1/troncreatetrc20.md deleted file mode 100644 index af77746f..00000000 --- a/v1.0/Blockchain/tron-1/troncreatetrc20.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Create a TRC-20 token" -slug: "troncreatetrc20" -excerpt: "10 credits per API call
\nCreate a TRON TRC-20 capped token. A capped TRC20 token is a type of token on the TRON blockchain that has a preset limit on the total number of tokens that can be created. This limit is specified during the token creation process and cannot be exceeded. Once the limit is reached, no more tokens can be minted. This feature helps to ensure the scarcity and value of the token and can provide investors with a sense of security. It is a popular choice for fundraising, as it allows for a predetermined amount of funds to be raised through the sale of tokens, and any excess tokens that are not sold are simply not minted.
\nSigning a transaction
\nWhen creating a TRC-20 token, 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.
\nFor 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.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/tron-1/tronfreeze.md b/v1.0/Blockchain/tron-1/tronfreeze.md deleted file mode 100644 index c32a35fc..00000000 --- a/v1.0/Blockchain/tron-1/tronfreeze.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Freeze the balance of a TRON account" -slug: "tronfreeze" -excerpt: "10 credits per API call
\nFreeze Tron assets on the address. By freezing assets, you can obtain energy or bandwidth to perform transactions.
\nSigning a transaction
\nWhen freezing the balance, 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.
\nFor 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.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:08 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/tron-1/trongenerateaddress.md b/v1.0/Blockchain/tron-1/trongenerateaddress.md deleted file mode 100644 index 1004deb9..00000000 --- a/v1.0/Blockchain/tron-1/trongenerateaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate a TRON address from the wallet's extended public key" -slug: "trongenerateaddress" -excerpt: "5 credits per API call
\nGenerate a TRON address from the extended public key of the wallet. The address is generated for the specific index - each extended public key can generate up to 2^32 addresses with the index starting from 0 up to 2^31.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:07 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/tron-1/trongenerateaddressprivatekey.md b/v1.0/Blockchain/tron-1/trongenerateaddressprivatekey.md deleted file mode 100644 index 0acf7c0c..00000000 --- a/v1.0/Blockchain/tron-1/trongenerateaddressprivatekey.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate the private key for a TRON address" -slug: "trongenerateaddressprivatekey" -excerpt: "10 credits per API call
\nGenerate private key for address from mnemonic for given derivation path index. Private key is generated for the specific index - each mnemonic\ncan generate up to 2^31 private keys starting from index 0 until 2^31.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:07 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/tron-1/trongetaccount.md b/v1.0/Blockchain/tron-1/trongetaccount.md deleted file mode 100644 index bc1ccbe7..00000000 --- a/v1.0/Blockchain/tron-1/trongetaccount.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get the TRON account by its address" -slug: "trongetaccount" -excerpt: "5 credits per API call
\nGet Tron account by address.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/tron-1/trongetblock.md b/v1.0/Blockchain/tron-1/trongetblock.md deleted file mode 100644 index 861b32ef..00000000 --- a/v1.0/Blockchain/tron-1/trongetblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get a TRON block by its hash or height" -slug: "trongetblock" -excerpt: "5 credits per API call
\nGet Tron block by hash or height.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/tron-1/trongetcurrentblock.md b/v1.0/Blockchain/tron-1/trongetcurrentblock.md deleted file mode 100644 index 9cec1bdd..00000000 --- a/v1.0/Blockchain/tron-1/trongetcurrentblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get the current TRON block" -slug: "trongetcurrentblock" -excerpt: "5 credits per API call
\nGet current Tron block.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:07 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/tron-1/trongettransaction.md b/v1.0/Blockchain/tron-1/trongettransaction.md deleted file mode 100644 index 358f1c91..00000000 --- a/v1.0/Blockchain/tron-1/trongettransaction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get a TRON transaction by its hash" -slug: "trongettransaction" -excerpt: "5 credits per API call
\nGet Tron transaction by hash.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:08 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/tron-1/trontransfer.md b/v1.0/Blockchain/tron-1/trontransfer.md deleted file mode 100644 index 1e3eb186..00000000 --- a/v1.0/Blockchain/tron-1/trontransfer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send TRX to a TRON account" -slug: "trontransfer" -excerpt: "10 credits per API call
\nSend an amount in TRX from address to address.
\nSigning a transaction
\nWhen sending TRX to a TRON account, 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.
\nProviding 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.
\nFor 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.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:07 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/tron-1/trontransfertrc10.md b/v1.0/Blockchain/tron-1/trontransfertrc10.md deleted file mode 100644 index 29266e47..00000000 --- a/v1.0/Blockchain/tron-1/trontransfertrc10.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send TRC-10 tokens to a TRON account" -slug: "trontransfertrc10" -excerpt: "10 credits per API call
\nSend TRC-10 tokens from address to address.
\nSigning a transaction
\nWhen sending TRC-10 tokens to a TRON account, 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.
\nProviding 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.
\nFor 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.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:08 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/tron-1/trontransfertrc20.md b/v1.0/Blockchain/tron-1/trontransfertrc20.md deleted file mode 100644 index 6abc6b49..00000000 --- a/v1.0/Blockchain/tron-1/trontransfertrc20.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send TRC-20 tokens to a TRON account" -slug: "trontransfertrc20" -excerpt: "10 credits per API call
\nSend TRC-20 tokens from address to address.
\nSigning a transaction
\nWhen sending TRC-20 tokens to a TRON account, 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.
\nProviding 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.
\nFor 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.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/tron-1/trontrc10detail.md b/v1.0/Blockchain/tron-1/trontrc10detail.md deleted file mode 100644 index e347c04e..00000000 --- a/v1.0/Blockchain/tron-1/trontrc10detail.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get information about a TRC-10 token" -slug: "trontrc10detail" -excerpt: "5 credits per API call
\nGet information about a TRON TRC-10 token.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:08 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/tron-1/tronunfreeze.md b/v1.0/Blockchain/tron-1/tronunfreeze.md deleted file mode 100644 index 28856c83..00000000 --- a/v1.0/Blockchain/tron-1/tronunfreeze.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Unfreeze the balance of a TRON account" -slug: "tronunfreeze" -excerpt: "10 credits per API call
\nUnfreeze Tron assets on the address. By unfreezing assets, you can unlock your staked TRX.
\nSigning a transaction
\nWhen unfreezing the balance, 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.
\nFor 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.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:08 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/vechain.md b/v1.0/Blockchain/vechain.md deleted file mode 100644 index f3590935..00000000 --- a/v1.0/Blockchain/vechain.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "VeChain" -slug: "vechain" -excerpt: "" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/vechain/vetblockchaintransfer.md b/v1.0/Blockchain/vechain/vetblockchaintransfer.md deleted file mode 100644 index aacc5fc0..00000000 --- a/v1.0/Blockchain/vechain/vetblockchaintransfer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send VeChain from account to account" -slug: "vetblockchaintransfer" -excerpt: "Send VET from account to account. Fee for the transaction is paid in VTHO.
\nThis 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.\nNo 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\nor signatureId. PrivateKey should be used only for quick development on testnet versions of blockchain when there is no risk of losing funds. In production,\nTatum KMS should be used for the highest security standards, and signatureId should be present in the request.\nAlternatively, using the Tatum client library for supported languages.\n
Broadcast signed transaction to VeChain blockchain. This method is used internally from Tatum KMS or Tatum client libraries.\nIt is possible to create custom signing mechanism and use this method only for broadcasting data to the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:01 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/vechain/vetgenerateaddress.md b/v1.0/Blockchain/vechain/vetgenerateaddress.md deleted file mode 100644 index c19bb0e5..00000000 --- a/v1.0/Blockchain/vechain/vetgenerateaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate VeChain account address from Extended public key" -slug: "vetgenerateaddress" -excerpt: "Generate VeChain account deposit address from Extended public key. Deposit address is generated for the specific index - each extended public key can generate\nup to 2^31 addresses starting from index 0 until 2^31 - 1.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:01 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/vechain/vetgenerateaddressprivatekey.md b/v1.0/Blockchain/vechain/vetgenerateaddressprivatekey.md deleted file mode 100644 index f4a853c4..00000000 --- a/v1.0/Blockchain/vechain/vetgenerateaddressprivatekey.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate VeChain private key" -slug: "vetgenerateaddressprivatekey" -excerpt: "Generate private key of address from mnemonic for given derivation path index. Private key is generated for the specific index - each mnemonic\ncan generate up to 2^32 private keys starting from index 0 until 2^31 - 1.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:01 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/vechain/vetgeneratewallet.md b/v1.0/Blockchain/vechain/vetgeneratewallet.md deleted file mode 100644 index 76adc0a2..00000000 --- a/v1.0/Blockchain/vechain/vetgeneratewallet.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate VeChain wallet" -slug: "vetgeneratewallet" -excerpt: "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 VeChain wallet with derivation path m'/44'/818'/0'/0. More about BIP44 HD wallets can be found here - https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki.\nGenerate BIP44 compatible VeChain wallet.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/vechain/vetgetbalance.md b/v1.0/Blockchain/vechain/vetgetbalance.md deleted file mode 100644 index 347b6f06..00000000 --- a/v1.0/Blockchain/vechain/vetgetbalance.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get VeChain Account balance" -slug: "vetgetbalance" -excerpt: "Get VeChain Account balance in VET.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:01 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/vechain/vetgetblock.md b/v1.0/Blockchain/vechain/vetgetblock.md deleted file mode 100644 index 6126333d..00000000 --- a/v1.0/Blockchain/vechain/vetgetblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get VeChain Block by hash" -slug: "vetgetblock" -excerpt: "Get VeChain Block by block hash or block number.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/vechain/vetgetcurrentblock.md b/v1.0/Blockchain/vechain/vetgetcurrentblock.md deleted file mode 100644 index ea6bc999..00000000 --- a/v1.0/Blockchain/vechain/vetgetcurrentblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get VeChain current block" -slug: "vetgetcurrentblock" -excerpt: "Get VeChain current block number.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:01 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/vechain/vetgetenergy.md b/v1.0/Blockchain/vechain/vetgetenergy.md deleted file mode 100644 index 8a82d9a2..00000000 --- a/v1.0/Blockchain/vechain/vetgetenergy.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get VeChain Account energy (VTHO)" -slug: "vetgetenergy" -excerpt: "Get VeChain Account energy in VTHO. VTHO is used for paying for the transaction fee.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/vechain/vetgettransaction.md b/v1.0/Blockchain/vechain/vetgettransaction.md deleted file mode 100644 index b206ec99..00000000 --- a/v1.0/Blockchain/vechain/vetgettransaction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get VeChain Transaction" -slug: "vetgettransaction" -excerpt: "Get VeChain Transaction by transaction hash.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/vechain/vetgettransactionreceipt.md b/v1.0/Blockchain/vechain/vetgettransactionreceipt.md deleted file mode 100644 index c41070ee..00000000 --- a/v1.0/Blockchain/vechain/vetgettransactionreceipt.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get VeChain Transaction Receipt" -slug: "vetgettransactionreceipt" -excerpt: "Get VeChain Transaction Receipt by transaction hash. Transaction receipt is available only after transaction is\nincluded in the block and contains information about paid fee or created contract address and much more.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:01 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/xinfin.md b/v1.0/Blockchain/xinfin.md deleted file mode 100644 index 2340c65e..00000000 --- a/v1.0/Blockchain/xinfin.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "XinFin" -slug: "xinfin" -excerpt: "" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/xinfin/xdcblockchainsmartcontractinvocation.md b/v1.0/Blockchain/xinfin/xdcblockchainsmartcontractinvocation.md deleted file mode 100644 index 7f44588e..00000000 --- a/v1.0/Blockchain/xinfin/xdcblockchainsmartcontractinvocation.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Invoke a method in a smart contract on XinFin" -slug: "xdcblockchainsmartcontractinvocation" -excerpt: "2 credits per API call
\nInvoke a method in an existing smart contract on XinFin.
\nYou can call a read-only or write method.
\nTroubleshooting a failed transaction
\nTatum ensures that this API works against the blockchain (accesses the blockchain, finds the specified smart contract, and executes the specified ABI method with the provided parameters).
However, because this API can be run against any smart contract on the blockchain, Tatum cannot in any way guarantee that the method itself will be executed successfully.
If you have issues with invoking the method, refer to the user documentation for this method, or contact the author of the smart contract.
\nFor more information about invoking methods in smart contracts, see this article on our Support Portal.
\nSigning a transaction
\nWhen 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.
\nFor 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.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/xinfin/xdcblockchaintransfer.md b/v1.0/Blockchain/xinfin/xdcblockchaintransfer.md deleted file mode 100644 index 062f6f1c..00000000 --- a/v1.0/Blockchain/xinfin/xdcblockchaintransfer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send XDC / ERC20 from account to account" -slug: "xdcblockchaintransfer" -excerpt: "2 credits per API call
\nSend XDC or Tatum supported ERC20 token from account to account.
\n
Signing a transaction
\nWhen 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.
\nProviding 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.
\nFor 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.
\nAlternatively, using the Tatum client library for supported languages." -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:11 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/xinfin/xdcbroadcast.md b/v1.0/Blockchain/xinfin/xdcbroadcast.md deleted file mode 100644 index d1b05903..00000000 --- a/v1.0/Blockchain/xinfin/xdcbroadcast.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Broadcast signed XDC transaction" -slug: "xdcbroadcast" -excerpt: "2 credits per API call
\nBroadcast signed transaction to XDC blockchain. This method is used internally from Tatum KMS or Tatum client libraries.\nIt is possible to create custom signing mechanism and use this method only for broadcasting data to the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:11 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/xinfin/xdcgenerateaddress.md b/v1.0/Blockchain/xinfin/xdcgenerateaddress.md deleted file mode 100644 index 4bea0368..00000000 --- a/v1.0/Blockchain/xinfin/xdcgenerateaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate XDC account address from Extended public key" -slug: "xdcgenerateaddress" -excerpt: "1 credit per API call
\nGenerate XDC account deposit address from Extended public key. Deposit address is generated for the specific\nindex - each extended public key can generate up to 2^31 addresses starting from index 0 until 2^31.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:11 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/xinfin/xdcgenerateaddressprivatekey.md b/v1.0/Blockchain/xinfin/xdcgenerateaddressprivatekey.md deleted file mode 100644 index 23f800c5..00000000 --- a/v1.0/Blockchain/xinfin/xdcgenerateaddressprivatekey.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate XDC private key" -slug: "xdcgenerateaddressprivatekey" -excerpt: "1 credit per API call
\nGenerate private key of address from mnemonic for given derivation path index. Private key is generated for the specific index - each mnemonic\ncan generate up to 2^31 private keys starting from index 0 until 2^31.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/xinfin/xdcgeneratewallet.md b/v1.0/Blockchain/xinfin/xdcgeneratewallet.md deleted file mode 100644 index ebad43ec..00000000 --- a/v1.0/Blockchain/xinfin/xdcgeneratewallet.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Generate XDC wallet" -slug: "xdcgeneratewallet" -excerpt: "1 credit per API call
\nTatum supports BIP44 HD wallets. It is very convenient and secure, since it can generate 2^31 addresses from 1 mnemonic phrase.\nMnemonic phrase consists of 24 special words in defined order and can restore access to all generated addresses and private keys.\n
\nEach address is identified by 3 main values:\n
Tatum follows BIP44 specification and generates for XDC wallet with derivation path m'/44'/550'/0'/0.\nMore about BIP44 HD wallets can be found here - https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki.\nGenerate BIP44 compatible XDC wallet.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:11 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/xinfin/xdcgetbalance.md b/v1.0/Blockchain/xinfin/xdcgetbalance.md deleted file mode 100644 index 1f3eb977..00000000 --- a/v1.0/Blockchain/xinfin/xdcgetbalance.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get XDC Account balance" -slug: "xdcgetbalance" -excerpt: "1 credit per API call
\nGet account balance in XDC. This method does not prints any balance of the ERC20 or ERC721 tokens on the account.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:11 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/xinfin/xdcgetblock.md b/v1.0/Blockchain/xinfin/xdcgetblock.md deleted file mode 100644 index 6fe3c856..00000000 --- a/v1.0/Blockchain/xinfin/xdcgetblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get XDC block by hash" -slug: "xdcgetblock" -excerpt: "1 credit per API call
\nGet XDC block by block hash or block number.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:11 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/xinfin/xdcgetcurrentblock.md b/v1.0/Blockchain/xinfin/xdcgetcurrentblock.md deleted file mode 100644 index fbefb962..00000000 --- a/v1.0/Blockchain/xinfin/xdcgetcurrentblock.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get current block number" -slug: "xdcgetcurrentblock" -excerpt: "1 credit per API call
\nGet XDC current block number. This is the number of the latest block in the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/xinfin/xdcgettransaction.md b/v1.0/Blockchain/xinfin/xdcgettransaction.md deleted file mode 100644 index 1975531c..00000000 --- a/v1.0/Blockchain/xinfin/xdcgettransaction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get XDC Transaction" -slug: "xdcgettransaction" -excerpt: "2 credits per API call
\nGet XDC transaction by transaction hash.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:11 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/xinfin/xdcgettransactioncount.md b/v1.0/Blockchain/xinfin/xdcgettransactioncount.md deleted file mode 100644 index 546085c3..00000000 --- a/v1.0/Blockchain/xinfin/xdcgettransactioncount.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get count of outgoing XDC transactions" -slug: "xdcgettransactioncount" -excerpt: "1 credit per API call
\nGet a number of outgoing XDC transactions for the address. When a transaction is sent, there can be multiple outgoing transactions,\nwhich are not yet processed by the blockchain. To distinguish between them, there is a counter called a nonce, which represents\nthe order of the transaction in the list of outgoing transactions.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:11 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/xinfin/xdcweb3driver.md b/v1.0/Blockchain/xinfin/xdcweb3driver.md deleted file mode 100644 index fcd52f96..00000000 --- a/v1.0/Blockchain/xinfin/xdcweb3driver.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Web3 HTTP driver" -slug: "xdcweb3driver" -excerpt: "2 credits per API call
\nThis 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.\nTo learn more about XDC Web3, visit the XDC developer's guide.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:11 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/xrp.md b/v1.0/Blockchain/xrp.md deleted file mode 100644 index 63edb78b..00000000 --- a/v1.0/Blockchain/xrp.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "XRP" -slug: "xrp" -excerpt: "" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:50 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/xrp/xrpaccountsettings.md b/v1.0/Blockchain/xrp/xrpaccountsettings.md deleted file mode 100644 index ba21284f..00000000 --- a/v1.0/Blockchain/xrp/xrpaccountsettings.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Modify XRP account" -slug: "xrpaccountsettings" -excerpt: "\n
Modify XRP account settings. If an XRP account should be an issuer of the custom asset, this accounts should have rippling enabled to true.\nIn order to support off-chain processing, required destination tag should be set on the account.
\nThis 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.\nNo 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\nor signatureId. PrivateKey should be used only for quick development on testnet versions of blockchain when there is no risk of losing funds. In production,\nTatum KMS should be used for the highest security standards, and signatureId should be present in the request.\nAlternatively, using the Tatum client library for supported languages.\n
Broadcast signed transaction to XRP blockchain. This method is used internally from Tatum KMS or Tatum client libraries.\nIt is possible to create custom signing mechanism and use this method only for broadcasting data to the blockchain.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/xrp/xrpgetaccountbalance.md b/v1.0/Blockchain/xrp/xrpgetaccountbalance.md deleted file mode 100644 index 0110bcad..00000000 --- a/v1.0/Blockchain/xrp/xrpgetaccountbalance.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Account Balance" -slug: "xrpgetaccountbalance" -excerpt: "Get XRP Account Balance. Obtain balance of the XRP and other assets on the account.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:59 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/xrp/xrpgetaccountinfo.md b/v1.0/Blockchain/xrp/xrpgetaccountinfo.md deleted file mode 100644 index 46d2d263..00000000 --- a/v1.0/Blockchain/xrp/xrpgetaccountinfo.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Account info" -slug: "xrpgetaccountinfo" -excerpt: "Get XRP Account info.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/xrp/xrpgetaccounttx.md b/v1.0/Blockchain/xrp/xrpgetaccounttx.md deleted file mode 100644 index 23ea3dcd..00000000 --- a/v1.0/Blockchain/xrp/xrpgetaccounttx.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Account transactions" -slug: "xrpgetaccounttx" -excerpt: "List all Account transactions.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:59 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/xrp/xrpgetfee.md b/v1.0/Blockchain/xrp/xrpgetfee.md deleted file mode 100644 index 1f84c5d3..00000000 --- a/v1.0/Blockchain/xrp/xrpgetfee.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get actual Blockchain fee" -slug: "xrpgetfee" -excerpt: "Get XRP Blockchain fee. Standard fee for the transaction is available in the drops.base_fee section and is 10 XRP drops by default.\nWhen there is a heavy traffic on the blockchain, fees are increasing according to current traffic.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/xrp/xrpgetlastclosedledger.md b/v1.0/Blockchain/xrp/xrpgetlastclosedledger.md deleted file mode 100644 index 9069d5f4..00000000 --- a/v1.0/Blockchain/xrp/xrpgetlastclosedledger.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get XRP Blockchain Information" -slug: "xrpgetlastclosedledger" -excerpt: "Get XRP Blockchain last closed ledger index and hash.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:58 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/xrp/xrpgetledger.md b/v1.0/Blockchain/xrp/xrpgetledger.md deleted file mode 100644 index 6b69b0bb..00000000 --- a/v1.0/Blockchain/xrp/xrpgetledger.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get Ledger" -slug: "xrpgetledger" -excerpt: "Get ledger by sequence.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:58 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/xrp/xrpgettransaction.md b/v1.0/Blockchain/xrp/xrpgettransaction.md deleted file mode 100644 index e9d2ae3d..00000000 --- a/v1.0/Blockchain/xrp/xrpgettransaction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get XRP Transaction by hash" -slug: "xrpgettransaction" -excerpt: "Get XRP Transaction by transaction hash.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:59 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Blockchain/xrp/xrptransferblockchain.md b/v1.0/Blockchain/xrp/xrptransferblockchain.md deleted file mode 100644 index 8233d15c..00000000 --- a/v1.0/Blockchain/xrp/xrptransferblockchain.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send XRP from address to address" -slug: "xrptransferblockchain" -excerpt: "Send XRP from account to account.
\nThis 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.\nNo 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\nor signatureId. PrivateKey should be used only for quick development on testnet versions of blockchain when there is no risk of losing funds. In production,\nTatum KMS should be used for the highest security standards, and signatureId should be present in the request.\nAlternatively, using the Tatum client library for supported languages.\n
\n
Create / Update / Delete XRP trust line between accounts to transfer private assets.\nBy creating trustline for the first time, the asset is created automatically and can be used in the transactions.
\nAccount setting rippling must be enabled on the issuer account before the trust line creation to asset work correctly.\nCreating a trust line will cause an additional 5 XRP to be blocked on the account.
\nThis 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.\nNo 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\nor signatureId. PrivateKey should be used only for quick development on testnet versions of blockchain when there is no risk of losing funds. In production,\nTatum KMS should be used for the highest security standards, and signatureId should be present in the request.\nAlternatively, using the Tatum client library for supported languages.
Generate XRP account. Tatum does not support HD wallet for XRP, only specific address and private key can be generated.
" -category: 65c0c8c6ba99f1006df40d7a -hidden: false -createdAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:51 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Documentation/getting-started.md b/v1.0/Documentation/getting-started.md deleted file mode 100644 index 7f17a3e6..00000000 --- a/v1.0/Documentation/getting-started.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: "Getting Started with Tatum 🚀" -slug: "getting-started" -excerpt: "" -category: 65a8e44fccf94800381cd6f6 -hidden: false -createdAt: "Thu Jan 18 2024 08:41:51 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Fri Mar 01 2024 07:24:33 GMT+0000 (Coordinated Universal Time)" ---- -Tatum's API and SDK are here to make your life easier when building blockchain applications! No more complicated setups, no need for previous blockchain experience. We've got you covered. - -# Why Tatum? 💡 - -1. **Super fast development:** Start building blockchain applications in no time. -2. **No previous blockchain experience required:** Perfect for beginners and experts alike. -3. **One line of code:** Perform complex tasks with minimal effort. - -[block:html]{"html":"Don't have an API key?\n
Get one to start using Blockchain Data in your app today.
\n Get started for free\n2 credits per API call
\nGet an estimated gas price and the number of gas units needed for a BNB Smart Chain transaction. The gas price is obtained from https://explorer.bitquery.io/bsc/gas.
\nNOTE: The estimated gas price is returned in wei. However, when making the transaction itself and providing the custom fee, you have to provide the gas price in Gwei. Make sure to convert the estimated gas price from wei to Gwei before submitting your transaction.
" -category: 65c0c807b4d77e006316ec5c -hidden: false -createdAt: "Mon Feb 05 2024 11:35:38 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:35:38 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Fee estimation/blockchain-fees/celoestimategas.md b/v1.0/Fee estimation/blockchain-fees/celoestimategas.md deleted file mode 100644 index 5f7c9df5..00000000 --- a/v1.0/Fee estimation/blockchain-fees/celoestimategas.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Estimate the fee for a Celo transaction" -slug: "celoestimategas" -excerpt: "2 credits per API call
\nGet an estimated gas price and the number of gas units needed for a Celo transaction. The gas price is obtained from https://explorer.bitquery.io/celo_rc1/gas.
\nNOTE: The estimated gas price is returned in wei. However, when making the transaction itself and providing the custom fee, you have to provide the gas price in Gwei. Make sure to convert the estimated gas price from wei to Gwei before submitting your transaction.
" -category: 65c0c807b4d77e006316ec5c -hidden: false -createdAt: "Mon Feb 05 2024 11:35:38 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:35:38 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Fee estimation/blockchain-fees/egldestimategas.md b/v1.0/Fee estimation/blockchain-fees/egldestimategas.md deleted file mode 100644 index 14715446..00000000 --- a/v1.0/Fee estimation/blockchain-fees/egldestimategas.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Estimate the fee for an Elrond transaction" -slug: "egldestimategas" -excerpt: "2 credits per API call
\nGet an estimated gas price and the number of gas units needed for an Elrond transaction. The gas price is obtained from https://gateway.elrond.com/network/config. The gas limit is obtains from https://gateway.elrond.com/transaction/cost.
" -category: 65c0c807b4d77e006316ec5c -hidden: false -createdAt: "Mon Feb 05 2024 11:35:38 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:35:38 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Fee estimation/blockchain-fees/estimatefeeblockchain-1.md b/v1.0/Fee estimation/blockchain-fees/estimatefeeblockchain-1.md deleted file mode 100644 index c0dfe91c..00000000 --- a/v1.0/Fee estimation/blockchain-fees/estimatefeeblockchain-1.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Estimate the fee for a transaction on a blockchain" -slug: "estimatefeeblockchain-1" -excerpt: "10 credits per API call
\nEstimate the current fee for different types of transactions.
\nThis API is supported for the following blockchains:
\n10 credits per API call
\nGet an estimated gas price and the number of gas units needed for an Ethereum transaction. The gas price is obtained from multiple sources and calculated based on the latest N blocks and the current mempool state.
\nThe fast gas price is used by default.
NOTE: The estimated gas price is returned in wei. However, when making the transaction itself and providing the custom fee, you have to provide the gas price in Gwei. Make sure to convert the estimated gas price from wei to Gwei before submitting your transaction.
" -category: 65c0c807b4d77e006316ec5c -hidden: false -createdAt: "Mon Feb 05 2024 11:35:38 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:35:38 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Fee estimation/blockchain-fees/ethestimategasbatch.md b/v1.0/Fee estimation/blockchain-fees/ethestimategasbatch.md deleted file mode 100644 index 892238ec..00000000 --- a/v1.0/Fee estimation/blockchain-fees/ethestimategasbatch.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Estimate the fee for multiple Ethereum transactions" -slug: "ethestimategasbatch" -excerpt: "10 credits per API call + 10 credits per each gas estimation
\nGet an estimated gas price and the number of gas units needed for multiple Ethereum transactions. The gas price is obtained from multiple sources and calculated based on the latest N blocks and the current mempool state.
\nThe estimations are returned in the same order as the transactions were submitted in the request.
\nThe fast gas price is used by default.
NOTE: The estimated gas price is returned in wei. However, when making a transaction itself and providing the custom fee, you have to provide the gas price in Gwei. Make sure to convert the estimated gas price from wei to Gwei before submitting your transaction.
\n" -category: 65c0c807b4d77e006316ec5c -hidden: false -createdAt: "Mon Feb 05 2024 11:35:38 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:35:38 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Fee estimation/blockchain-fees/getblockchainfee-1.md b/v1.0/Fee estimation/blockchain-fees/getblockchainfee-1.md deleted file mode 100644 index c953caa8..00000000 --- a/v1.0/Fee estimation/blockchain-fees/getblockchainfee-1.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get the recommended fee/gas price for a blockchain" -slug: "getblockchainfee-1" -excerpt: "1 credit per API call
\nGet the recommended fee/gas price for a blockchain.
\nFee is in satoshis(meaning currency(BTC, DOGE,... / 100 000 000) per byte\n
This API is supported for the following blockchains:
\n2 credits per API call
\nGet an estimated gas price and the number of gas units needed for a KuCoin Community Chain transaction.
\nNOTE: The estimated gas price is returned in wei. However, when making the transaction itself and providing the custom fee, you have to provide the gas price in Gwei. Make sure to convert the estimated gas price from wei to Gwei before submitting your transaction.
" -category: 65c0c807b4d77e006316ec5c -hidden: false -createdAt: "Mon Feb 05 2024 11:35:38 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:35:38 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Fee estimation/blockchain-fees/klaytnestimategas.md b/v1.0/Fee estimation/blockchain-fees/klaytnestimategas.md deleted file mode 100644 index 1b184f18..00000000 --- a/v1.0/Fee estimation/blockchain-fees/klaytnestimategas.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Estimate the fee for a Klaytn transaction" -slug: "klaytnestimategas" -excerpt: "2 credits per API call
\nGet an estimated gas price and the number of gas units needed for a Klaytn transaction. The gas price is obtained from https://explorer.bitquery.io/klaytn/gas.
\nNOTE: The estimated gas price is returned in peb. However, when making the transaction itself and providing the custom fee, you have to provide the gas price in Gpeb. Make sure to convert the estimated gas price from peb to Gpeb before submitting your transaction.
" -category: 65c0c807b4d77e006316ec5c -hidden: false -createdAt: "Mon Feb 05 2024 11:35:38 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:35:38 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Fee estimation/blockchain-fees/oneestimategas.md b/v1.0/Fee estimation/blockchain-fees/oneestimategas.md deleted file mode 100644 index 24ee339b..00000000 --- a/v1.0/Fee estimation/blockchain-fees/oneestimategas.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Estimate Harmony transaction fees" -slug: "oneestimategas" -excerpt: "2 credits per API call
\nGet an estimated gas price and the number of gas units needed for a Harmony transaction.
\nNOTE: The estimated gas price is returned in wei. However, when making the transaction itself, you have to provide the gas price in Gwei. Make sure to convert the estimated gas price from wei to Gwei before submitting your transaction.
" -category: 65c0c807b4d77e006316ec5c -hidden: false -createdAt: "Mon Feb 05 2024 11:35:38 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:35:38 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Fee estimation/blockchain-fees/polygonestimategas.md b/v1.0/Fee estimation/blockchain-fees/polygonestimategas.md deleted file mode 100644 index 72d883fb..00000000 --- a/v1.0/Fee estimation/blockchain-fees/polygonestimategas.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Estimate the fee for a Polygon transaction" -slug: "polygonestimategas" -excerpt: "2 credits per API call
\nGet an estimated gas price and the number of gas units needed for a Polygon transaction. The gas price is obtained from https://gasstation-mainnet.matic.network/.
\nNOTE: The estimated gas price is returned in wei. However, when making the transaction itself and providing the custom fee, you have to provide the gas price in Gwei. Make sure to convert the estimated gas price from wei to Gwei before submitting your transaction.
" -category: 65c0c807b4d77e006316ec5c -hidden: false -createdAt: "Mon Feb 05 2024 11:35:38 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:35:38 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Fee estimation/blockchain-fees/vetestimategas.md b/v1.0/Fee estimation/blockchain-fees/vetestimategas.md deleted file mode 100644 index 7be830e1..00000000 --- a/v1.0/Fee estimation/blockchain-fees/vetestimategas.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Estimate the gas needed for a VeChain transaction" -slug: "vetestimategas" -excerpt: "5 credits per API call
\nGet an estimated amount of gas needed for a VeChain transaction.
" -category: 65c0c807b4d77e006316ec5c -hidden: false -createdAt: "Mon Feb 05 2024 11:35:38 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:35:38 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Fee estimation/blockchain-fees/xdcestimategas.md b/v1.0/Fee estimation/blockchain-fees/xdcestimategas.md deleted file mode 100644 index 7e5eaece..00000000 --- a/v1.0/Fee estimation/blockchain-fees/xdcestimategas.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Estimate the fee for a XinFin transaction" -slug: "xdcestimategas" -excerpt: "2 credits per API call
\nGet an estimated gas price and the number of gas units needed for a XinFin transaction. The gas price is obtained from https://rpc.xinfin.network/gasPrice.
\nNOTE: The estimated gas price is returned in wei. However, when making the transaction itself and providing the custom fee, you have to provide the gas price in Gwei. Make sure to convert the estimated gas price from wei to Gwei before submitting your transaction.
" -category: 65c0c807b4d77e006316ec5c -hidden: false -createdAt: "Mon Feb 05 2024 11:35:38 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:35:38 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Fee estimation/virtual-account-blockchain-fees.md b/v1.0/Fee estimation/virtual-account-blockchain-fees.md deleted file mode 100644 index 0398e03c..00000000 --- a/v1.0/Fee estimation/virtual-account-blockchain-fees.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Virtual account blockchain fees" -slug: "virtual-account-blockchain-fees" -excerpt: "" -category: 65c0c807b4d77e006316ec5c -hidden: false -createdAt: "Mon Feb 05 2024 11:35:37 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:35:38 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Fee estimation/virtual-account-blockchain-fees/offchainestimatefee.md b/v1.0/Fee estimation/virtual-account-blockchain-fees/offchainestimatefee.md deleted file mode 100644 index 6745d8a8..00000000 --- a/v1.0/Fee estimation/virtual-account-blockchain-fees/offchainestimatefee.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Estimate ledger to blockchain transaction fee" -slug: "offchainestimatefee" -excerpt: "Estimate current transaction fee for ledger to blockchain transaction.
\nSupported blockchains:\n
Create new managed address for a specific chain. If the address is mainnet or testnet one depends on the API Key - testnet API Key manages testnet addresses, mainnet API Key manages mainnet addresses.\nResult of the operation is address and walletId, which is used for identifying the wallet later on and/or exporting the private key if needed.
\nFree users can manage only 10 addresses per API Key.\n
Delete managed address. Once deleted, the address won't be charged in a daily credit usage, but it won't be possible to get the private key for it.
" -category: 65c0c8593a8063001c639eae -hidden: false -createdAt: "Mon Feb 05 2024 11:36:59 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:37:00 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Security/custodial-managed-wallets/custodialgetwallet.md b/v1.0/Security/custodial-managed-wallets/custodialgetwallet.md deleted file mode 100644 index c11bde47..00000000 --- a/v1.0/Security/custodial-managed-wallets/custodialgetwallet.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get managed address" -slug: "custodialgetwallet" -excerpt: "Get managed address for an API Key. It's possible to export the private key, if query parameter export is set to true.
" -category: 65c0c8593a8063001c639eae -hidden: false -createdAt: "Mon Feb 05 2024 11:36:59 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:37:00 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Security/custodial-managed-wallets/custodialgetwallets.md b/v1.0/Security/custodial-managed-wallets/custodialgetwallets.md deleted file mode 100644 index 38b0be4c..00000000 --- a/v1.0/Security/custodial-managed-wallets/custodialgetwallets.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get managed addresses" -slug: "custodialgetwallets" -excerpt: "Get all managed addresses for an API Key.
" -category: 65c0c8593a8063001c639eae -hidden: false -createdAt: "Mon Feb 05 2024 11:36:59 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:59 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Security/custodial-managed-wallets/custodialtransfermanagedaddress.md b/v1.0/Security/custodial-managed-wallets/custodialtransfermanagedaddress.md deleted file mode 100644 index eed4e9f4..00000000 --- a/v1.0/Security/custodial-managed-wallets/custodialtransfermanagedaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Sign and transfer using managed address" -slug: "custodialtransfermanagedaddress" -excerpt: "Sign transaction and transfer assets from a custodial managed address.
\nSupported chains:\n
| Mainnet address | Devnet address | |
| Address | DSpHmb7hLnetoybammcJBJiyqMVR3pDhCuW6hqVg9eBF | DSpHmb7hLnetoybammcJBJiyqMVR3pDhCuW6hqVg9eBF |
\nimport { LAMPORTS_PER_SOL, PublicKey, SystemProgram, Transaction, Connection } from '@solana/web3.js'\n\nconst connection = new Connection('https://api.tatum.io/v3/blockchain/node/SOL')\nconst from = 'HrJtQTy2RW9c6y41RvN8x3bEiD6Co74AuhER2MGCpa58'\nconst to = 'FZAS4mtPvswgVxbpc117SqfNgCDLTCtk5CoeAtt58FWU'\nconst amount = '0.000001'\nconst devnet_fee_payer = '5zPr5331CtBjgVeLedhmJPEpFaUsorLCnb3aCQPsUc9w'\nconst fromPubkey = new PublicKey(from)\nconst transaction = new Transaction({ feePayer: new PublicKey(devnet_fee_payer) })\ntransaction.add(\n SystemProgram.transfer({\n fromPubkey: fromPubkey,\n toPubkey: new PublicKey(to),\n lamports: new BigNumber(amount).multipliedBy(LAMPORTS_PER_SOL).toNumber(),\n }),\n)\nconst { blockhash, lastValidBlockHeight } = await connection.getLatestBlockhash('finalized')\ntransaction.recentBlockhash = blockhash\ntransaction.lastValidBlockHeight = lastValidBlockHeight\ntransaction.partialSign(...signers)\nreturn transaction.serialize({ requireAllSignatures: false }).toString('hex')\n\nFor the above example, developer have 2 options how to sign transaction - if the sender address HrJtQTy2RW9c6y41RvN8x3bEiD6Co74AuhER2MGCpa58 is managed using a Tatum managed wallet with id 0b1eae3d-2520-4903-8bbf-5dec3ad2a5d4,\nthe final payload to the custodial/transaction endpoint should look like this:\n\n{\n \"chain\": \"SOL\",\n \"txData\": \"020001044a22af97a838a504e6f7c0b18d779afcea612da50794cc1dac641861fc1ab14afa5cacaf91c298694e64bb5496916c3c68a32affb92d4bcd2736fbb00169d57bd840de2a454960308f688cd3ee308c1fa01ecfa0b03770aaaf3b52d71d46c31d000000000000000000000000000000000000000000000000000000000000000060d38e0da20dc5900b7e902c918eae6a95e2d90af154b53a422f4ab26b050f4f01030201020c02000000e803000000000000\",\n \"walletIds\": [\n {\n \"key\": \"0b1eae3d-2520-4903-8bbf-5dec3ad2a5d4\",\n \"type\": \"MANAGED\"\n }\n ]\n}\n\nIf the sender address is not managed, the transaction could be signed with the private key of that address before the serialization and the payload will look like this:\n\n{\n \"chain\": \"SOL\",\n \"txData\": \"020001044a22af97a838a504e6f7c0b18d779afcea612da50794cc1dac641861fc1ab14afa5cacaf91c298694e64bb5496916c3c68a32affb92d4bcd2736fbb00169d57bd840de2a454960308f688cd3ee308c1fa01ecfa0b03770aaaf3b52d71d46c31d000000000000000000000000000000000000000000000000000000000000000060d38e0da20dc5900b7e902c918eae6a95e2d90af154b53a422f4ab26b050f4f01030201020c02000000e803000000000000\",\n \"walletIds\": []\n}\n\n"
-category: 65c0c8593a8063001c639eae
-hidden: false
-createdAt: "Mon Feb 05 2024 11:36:59 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Mon Feb 05 2024 11:37:00 GMT+0000 (Coordinated Universal Time)"
----
diff --git a/v1.0/Security/key-management-system.md b/v1.0/Security/key-management-system.md
deleted file mode 100644
index 21020c87..00000000
--- a/v1.0/Security/key-management-system.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: "Key Management System"
-slug: "key-management-system"
-excerpt: ""
-category: 65c0c8593a8063001c639eae
-hidden: false
-createdAt: "Mon Feb 05 2024 11:36:59 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Mon Feb 05 2024 11:36:59 GMT+0000 (Coordinated Universal Time)"
----
diff --git a/v1.0/Security/key-management-system/completependingsignature.md b/v1.0/Security/key-management-system/completependingsignature.md
deleted file mode 100644
index cb5f9b2b..00000000
--- a/v1.0/Security/key-management-system/completependingsignature.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: "Complete pending transaction to sign"
-slug: "completependingsignature"
-excerpt: "Mark pending transaction to sign as a complete and update it with a transactionID from the blockchain.
" -category: 65c0c8593a8063001c639eae -hidden: false -createdAt: "Mon Feb 05 2024 11:36:59 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:37:00 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Security/key-management-system/deletependingtransactiontosign.md b/v1.0/Security/key-management-system/deletependingtransactiontosign.md deleted file mode 100644 index 0a35fa4c..00000000 --- a/v1.0/Security/key-management-system/deletependingtransactiontosign.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Delete transaction" -slug: "deletependingtransactiontosign" -excerpt: "Delete transaction to be signed. When deleting offchain transaction, linked withdrawal will be cancelled automatically.
" -category: 65c0c8593a8063001c639eae -hidden: false -createdAt: "Mon Feb 05 2024 11:36:59 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:37:00 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Security/key-management-system/getpendingtransactionstosign.md b/v1.0/Security/key-management-system/getpendingtransactionstosign.md deleted file mode 100644 index dcf46862..00000000 --- a/v1.0/Security/key-management-system/getpendingtransactionstosign.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get pending transactions to sign" -slug: "getpendingtransactionstosign" -excerpt: "1 credit per API call
\nGet the list of pending transactions to sign and broadcast using KMS.
" -category: 65c0c8593a8063001c639eae -hidden: false -createdAt: "Mon Feb 05 2024 11:36:59 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:59 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Security/key-management-system/getpendingtransactiontosign.md b/v1.0/Security/key-management-system/getpendingtransactiontosign.md deleted file mode 100644 index da581fb9..00000000 --- a/v1.0/Security/key-management-system/getpendingtransactiontosign.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get transaction details" -slug: "getpendingtransactiontosign" -excerpt: "Get detail of transaction to be signed / that was already signed and contains transactionId.
" -category: 65c0c8593a8063001c639eae -hidden: false -createdAt: "Mon Feb 05 2024 11:36:59 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:37:00 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Security/key-management-system/receivependingtransactionstosign.md b/v1.0/Security/key-management-system/receivependingtransactionstosign.md deleted file mode 100644 index c1403743..00000000 --- a/v1.0/Security/key-management-system/receivependingtransactionstosign.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get pending transactions to sign" -slug: "receivependingtransactionstosign" -excerpt: "1 credit for every 500 signature IDs per API call
\nGet the list of pending transactions to sign and broadcast using KMS.
\nNOTE: This API works only in KMS v5.0 or later. If you use KMS older than v5.0, use this API instead.
" -category: 65c0c8593a8063001c639eae -hidden: false -createdAt: "Mon Feb 05 2024 11:36:59 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:59 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Security/malicious-address.md b/v1.0/Security/malicious-address.md deleted file mode 100644 index 90f915b5..00000000 --- a/v1.0/Security/malicious-address.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Malicious address" -slug: "malicious-address" -excerpt: "" -category: 65c0c8593a8063001c639eae -hidden: false -createdAt: "Mon Feb 05 2024 11:36:59 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:59 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Security/malicious-address/checkmalicousaddress.md b/v1.0/Security/malicious-address/checkmalicousaddress.md deleted file mode 100644 index 2369b893..00000000 --- a/v1.0/Security/malicious-address/checkmalicousaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Check malicous address" -slug: "checkmalicousaddress" -excerpt: "Check, if the blockchain address is malicous. Malicous address can contain assets from the DarkWeb, is connected to the scam projects or contains stolen funds.
Supported Chains: ETH, BTC, LTC
" -category: 65c0c8593a8063001c639eae -hidden: false -createdAt: "Mon Feb 05 2024 11:36:59 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:37:00 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/auction/approvenftauctionspending.md b/v1.0/Smart Contracts/auction/approvenftauctionspending.md deleted file mode 100644 index 900a14d1..00000000 --- a/v1.0/Smart Contracts/auction/approvenftauctionspending.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Allow the NFT auction or marketplace to transfer an asset" -slug: "approvenftauctionspending" -excerpt: "2 credits per API call
\nAllow the NFT auction/marketplace smart contract to transfer the asset (NFT or Multi Token) that is listed for selling.
The auction/marketplace smart contract will transfer the asset to the buyer after the asset is purchased.
This API is supported for the following blockchains:
\nSigning a transaction
\nWhen allowing the NFT auction/marketplace smart contract to transfer the asset, 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/auction/bidonauction.md b/v1.0/Smart Contracts/auction/bidonauction.md deleted file mode 100644 index 173de0e1..00000000 --- a/v1.0/Smart Contracts/auction/bidonauction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Bid for an asset at the NFT auction" -slug: "bidonauction" -excerpt: "2 credits per API call
\nBid for an asset listed on the NFT auction.
\nYou can buy the asset either for the native blockchain assets (for example, ETH, BSC, and so on) or for the fungible tokens of the blockchain.
\nAfter you have purchased the asset, it is in a pending state until the auction is settled. Settling the auction means that the asset is transferred to the buyer, the amount is transferred to the seller, and the fee is transferred to the fee recipient of the auction.
\nFor the complete information about how the bidding/purchase process at an auction works, see the API for creating an NFT auction.
\nThis API is supported for the following blockchains:
\nThe \"execution reverted\" message
\nWhen making this API call, you may get the following message:
\nAlthough one or more Error Occurred [execution reverted] Contract Execution Completed
\nThis message is a result of the auction version check and has no impact on completing the API call. You can safely ignore it.
Signing a transaction
\nWhen bidding for an asset at the NFT auction, 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:28 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/auction/cancelauction.md b/v1.0/Smart Contracts/auction/cancelauction.md deleted file mode 100644 index a7bf8c5e..00000000 --- a/v1.0/Smart Contracts/auction/cancelauction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Cancel the selling of an asset at the NFT auction" -slug: "cancelauction" -excerpt: "2 credits per API call
\nCancel the selling of an asset at the NFT auction.
\nYou can cancel the selling only if you are the seller of the asset or the auction operator. Once the selling is canceled, the asset is returned to the seller.
\nYou cannot cancel the selling if the asset has already been purchased.
\nThis API is supported for the following blockchains:
\nThe \"execution reverted\" message
\nWhen making this API call, you may get the following message:
\nAlthough one or more Error Occurred [execution reverted] Contract Execution Completed
\nThis message is a result of the auction version check and has no impact on completing the API call. You can safely ignore it.
Signing a transaction
\nWhen cancelling the selling of an asset at the NFT auction, 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:28 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/auction/createauction.md b/v1.0/Smart Contracts/auction/createauction.md deleted file mode 100644 index 0064be94..00000000 --- a/v1.0/Smart Contracts/auction/createauction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Sell an asset at the NFT auction" -slug: "createauction" -excerpt: "2 credits per API call
\nCreate new auction on the auction contract. Before operation, seller must approve spending of the NFT token for the Auction contract using Approve NFT.\nAfter auction is created, auction contract transfers the asset to the auction smart contract.\nOnly auction for existing NFTs can be created - seller must be owner of the NFT asset.
\nThis API is supported for the following blockchains:
\nA known issue on Harmony
\nOn Harmony, when you are viewing a transaction in the Harmony Blockchain Explorer, the transaction status may be displayed as the following:
\nError reverted:x0
\nThis is a known issue with the Harmony Blockchain Explorer. This status does not mean that the transaction failed. You can safely ignore it.
Signing a transaction
\nWhen selling an asset at the NFT auction, 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:27 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/auction/generateauction.md b/v1.0/Smart Contracts/auction/generateauction.md deleted file mode 100644 index 2c8d02d6..00000000 --- a/v1.0/Smart Contracts/auction/generateauction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Create an NFT auction" -slug: "generateauction" -excerpt: "2 credits per API call
\nDeploy new smart contract for NFT auction logic. Smart contract enables auction operator to create new auction for NFT (ERC-721/1155).\nOperator can set a fee in percentage, which will be paid on top of the price of the asset.\ncan be offered for native asset - ETH, BSC, etc. - or any ERC20 token - this is configurable during auction creation.\nBefore auction is created, seller must approve transfer of the NFT to the auction contract.\nBuyer will bid for the asset from the auction using native asset - send assets along the gid() smart contract call, or via ERC20 token.\nBuyer of the auction must perform approval for the smart contract to access ERC20 token, before the actual bid() method is called.\nOnce there is higher bid then the actual one, the previous bidder's funds will be returned to him and new bidder will be the current winning one.\nWhen auction ends, anyone can settle the auction - NFT will be sent to the bidder, assets to the seller and fee to the operator.
\nThis operation deploys a smart contract on the blockchain.
This API is supported for the following blockchains:
\nSigning a transaction
\nWhen creating an NFT auction, 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:27 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/auction/getauction.md b/v1.0/Smart Contracts/auction/getauction.md deleted file mode 100644 index 84bbda59..00000000 --- a/v1.0/Smart Contracts/auction/getauction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get information about an auctioned asset at the NFT auction" -slug: "getauction" -excerpt: "1 credit per API call
\nGet information about a specific auctioned asset at the NFT auction.
\nThis API is supported for the following blockchains:
\n1 credit per API call
\nGet the NFT auction fee.
\nThis API is supported for the following blockchains:
\n1 credit per API call
\nGet the recipient of the NFT auction fee.
\nThis API is supported for the following blockchains:
\n2 credits per API call
\nSettle an auction once it has ended and there is a buyer of the asset at this auction. Settling the auction means that the asset is transferred to the buyer, the amount is transferred to the seller, and the fee is transferred to the fee recipient of the auction.
Both seller and buyer can settle the auction.
This API is supported for the following blockchains:
\nThe \"execution reverted\" message
\nWhen making this API call, you may get the following message:
\nAlthough one or more Error Occurred [execution reverted] Contract Execution Completed
\nThis message is a result of the auction version check and has no impact on completing the API call. You can safely ignore it.
Signing a transaction
\nWhen settling the NFT auction, 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/auction/updateauctionfee.md b/v1.0/Smart Contracts/auction/updateauctionfee.md deleted file mode 100644 index c8bc6b91..00000000 --- a/v1.0/Smart Contracts/auction/updateauctionfee.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Update the NFT auction fee" -slug: "updateauctionfee" -excerpt: "2 credits per API call
\nUpdate the NFT auction fee.
\nThis API is supported for the following blockchains:
\nSigning a transaction
\nWhen updating the NFT auction fee, 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/auction/updateauctionfeerecipient.md b/v1.0/Smart Contracts/auction/updateauctionfeerecipient.md deleted file mode 100644 index 23c38e41..00000000 --- a/v1.0/Smart Contracts/auction/updateauctionfeerecipient.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Update the recipient of the NFT auction fee" -slug: "updateauctionfeerecipient" -excerpt: "2 credits per API call
\nUpdate the recipient of the NFT auction fee.
\nThis API is supported for the following blockchains:
\nSigning a transaction
\nWhen updating the recipient of the NFT auction, 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:28 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/fungible-tokens-erc-20-or-compatible.md b/v1.0/Smart Contracts/fungible-tokens-erc-20-or-compatible.md deleted file mode 100644 index 71c056cd..00000000 --- a/v1.0/Smart Contracts/fungible-tokens-erc-20-or-compatible.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Fungible Tokens (ERC-20 or compatible)" -slug: "fungible-tokens-erc-20-or-compatible" -excerpt: "" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/fungible-tokens-erc-20-or-compatible/erc20approve.md b/v1.0/Smart Contracts/fungible-tokens-erc-20-or-compatible/erc20approve.md deleted file mode 100644 index 47f00b8a..00000000 --- a/v1.0/Smart Contracts/fungible-tokens-erc-20-or-compatible/erc20approve.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Allow a blockchain address to transfer and burn fungible tokens" -slug: "erc20approve" -excerpt: "2 credits per API call
\nAllow a blockchain address (the spender parameter in the request body) to transfer and burn fungible tokens on behalf of the smart contract owner.
This API is supported for the following blockchains:
\nSigning a transaction
\nWhen allowing a blockchain address to transfer and burn fungible tokens, 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:29 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/fungible-tokens-erc-20-or-compatible/erc20burn.md b/v1.0/Smart Contracts/fungible-tokens-erc-20-or-compatible/erc20burn.md deleted file mode 100644 index 65889d2d..00000000 --- a/v1.0/Smart Contracts/fungible-tokens-erc-20-or-compatible/erc20burn.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Burn fungible tokens" -slug: "erc20burn" -excerpt: "2 credits per API call
\nBurn fungible tokens. Burning fungible tokens deletes the specified supply of the tokens (the amount parameter in the request body) from the smart contract (the contractAddress parameter in the request body).
This API is supported for the following blockchains:
\nSigning a transaction
\nWhen burning fungible tokens, 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/fungible-tokens-erc-20-or-compatible/erc20deploy.md b/v1.0/Smart Contracts/fungible-tokens-erc-20-or-compatible/erc20deploy.md deleted file mode 100644 index 731d978c..00000000 --- a/v1.0/Smart Contracts/fungible-tokens-erc-20-or-compatible/erc20deploy.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Deploy a fungible token smart contract" -slug: "erc20deploy" -excerpt: "2 credits per API call
\nDeploy a fungible token smart contract on the blockchain. In a deployed smart contract, you can mint and burn fungible tokens. The whole supply of fungible tokens (the supply parameter in the request body) will be transferred to the specified blockchain address (the address parameter in the request body).
\nSmart contracts are standardized and audited.
This API is supported for the following blockchains:
\nYou can review the code of a deployed smart contract here.
\nSigning a transaction
\nWhen deploying a fungible token 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:29 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/fungible-tokens-erc-20-or-compatible/erc20getbalance.md b/v1.0/Smart Contracts/fungible-tokens-erc-20-or-compatible/erc20getbalance.md deleted file mode 100644 index 185f2f2d..00000000 --- a/v1.0/Smart Contracts/fungible-tokens-erc-20-or-compatible/erc20getbalance.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get the number of fungible tokens that a blockchain address holds in a smart contract" -slug: "erc20getbalance" -excerpt: "1 credit per API call
\nGet the number of the fungible tokens minted on a specific smart contract (the contractAddress path parameter in the request endpoint URL) that a blockchain address holds.
This API is supported for the following blockchains:
\n1 credit per API call
\nGet the number of all fungible tokens that a blockchain address holds across a blockchain. The tokens are returned grouped by the smart contracts they were minted on.
\nThis API is supported for the following blockchains:
\n1 credit per API call
\nGet incoming and outgoing transactions related to fungible tokens on a blockchain address.
\nThis API is supported for the following blockchains:
\n2 credits per API call
\nCreate new fungible tokens in the smart contract (the contractAddress parameter in the request body) and transfer them to the specified blockchain address (the to parameter in the request body). You can mint new fungible tokens only if the current supply of tokens in the smart contract is lower than the total supply set for this contract.
This API is supported for the following blockchains:
\nSigning a transaction
\nWhen minting fungible tokens, 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:29 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/fungible-tokens-erc-20-or-compatible/erc20transfer.md b/v1.0/Smart Contracts/fungible-tokens-erc-20-or-compatible/erc20transfer.md deleted file mode 100644 index 36873e66..00000000 --- a/v1.0/Smart Contracts/fungible-tokens-erc-20-or-compatible/erc20transfer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Transfer fungible tokens" -slug: "erc20transfer" -excerpt: "2 credits per API call
\nTransfer a supply of fungible tokens existing in the smart contract (the contractAddress parameter in the request body) to the specified blockchain address (the to parameter in the request body).
\nTransferring fungible tokens invokes the transfer() method.
This API is supported for the following blockchains:
\nTransferring fungible tokens on Algorand
\nOn Algorand, the recipient has to agree in advance to receive your fungible tokens because Algorand charges users for storing the tokens on their addresses, and an Algorand blockchain address by default does not receive the tokens unless explicitly agreed. Before transferring the fungible tokens, make sure that the recipient has agreed to receive the NFT to their address.
Blockchain-specific APIs to transfer fungible tokens
\nYou can also use blockchain-specific APIs for transferring fungible tokens on the following blockchains:\n
Signing a transaction
\nWhen transferring fungible tokens, 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/gas-pump.md b/v1.0/Smart Contracts/gas-pump.md deleted file mode 100644 index 42999d6b..00000000 --- a/v1.0/Smart Contracts/gas-pump.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Gas pump" -slug: "gas-pump" -excerpt: "" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/gas-pump/activatednotactivatedgaspumpaddresses.md b/v1.0/Smart Contracts/gas-pump/activatednotactivatedgaspumpaddresses.md deleted file mode 100644 index 2ed59507..00000000 --- a/v1.0/Smart Contracts/gas-pump/activatednotactivatedgaspumpaddresses.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get the results of the address activation transaction" -slug: "activatednotactivatedgaspumpaddresses" -excerpt: "1 credit per API call
\nGet the results of the activation transaction after activating gas pump addresses.
\nIf the activation transaction got recorded into a block, the API returns two arrays:
\nvalid, with the activated gas pump addressesinvalid, with the gas pump addresses that for some reason did not get activated together with the reason whyIf the transaction is still being processed, the API returns an error message. In this case, repeat the call later.
\nThis API is supported for the following blockchains:
\n2 credits per API call
\nActivate the precalulated gas pump addresses. Activating a gas pump address allows this address to send funds to other addresses.
\nYou can activate up to 270 addresses in one call. If you need to activate more than 270 addresses, make several API calls. For example, if you need to activate 500 addresses, make an API call with 270 addresses (set up the range of their index values accordingly in the from and to request body parameters) and then make another API call with the remaining 230 addresses.
When to activate a gas pump address
\nBecause activating a gas pump address costs some amount of gas on a blockchain, you want to activate only those addresses that will be used for sending funds to other addresses. If you know that a gas pump address will not be used for sending funds, you can leave this address not activated. The customer who uses this address will still be able to receive funds.
Depending on your business needs and requirements, you can choose when to activate the gas pump addresses. If you know for sure that all the precalculated addresses will be sending funds, you can activate all the addresses right after they have been precalculated.
\nAlternatively, you can set up the activation in such a way so that a gas pump address gets activated only when a specific event is triggered. For example, you can activate a gas pump address:
\nAfter you make an API call to activate gas pump addresses, use the API for getting the results of the address activation transaction.
\nPaying the gas fee for activating gas pump addresses
\nYou can pay the gas fees for each activation transaction yourself, or Tatum can cover it for you.
ActivateGasPumpTatum. For example, if you are activating gas pump addresses on Ethereum and you use KMS, use the ActivateGasPumpKMS schema.\nActivateGasPumpTatum schema of the request body.\nThis API is supported for the following blockchains:
\n2 credits per API call
\nAllow another blockchain address (the spender parameter in the request body) to transfer the asset from a gas pump address on behalf of the master address.
Use this API when the customer using the gas pump address sells assets on a marketplace or auction. After the customer creates a listing of the asset, they have to allow the marketplace/auction smart contract to transfer the asset to the buyer after the asset has been bought.
\nThe asset can be one of the following types:
\nThis API is supported for the following blockchains:
\nSigning a transaction
\nWhen approving the transfer of an asset, 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:26 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/gas-pump/gaspumpaddressesactivatedornot.md b/v1.0/Smart Contracts/gas-pump/gaspumpaddressesactivatedornot.md deleted file mode 100644 index 36947753..00000000 --- a/v1.0/Smart Contracts/gas-pump/gaspumpaddressesactivatedornot.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Check whether the gas pump address with a specified index is activated" -slug: "gaspumpaddressesactivatedornot" -excerpt: "1 credit per API call
\nCheck whether the gas pump address with a specified index is activated and can send funds to other addresses.
\nYou can use this API when a customer initiates a fund transfer and you need to check whether their gas pump address is allowed to send funds.
\nThis API is supported for the following blockchains:
\nThis API is deprecated.
To start with the gas pump, use the API for precalculating the gas pump addresses.
If you built your gas pump solution using this API and the API for generating a gas pump wallet address, you can still use this API for creating more custodial addresses for your solution. However, we recommend that you switch to the API for precalculating the gas pump addresses.
2 credits per API call
\nGenerate new gas pump smart contract address on the blockchain. It's possible to enable tokens, which should be detected and supported on that address. This address enables custodial providers to\nreceive native assets, ERC20 / ERC721 / ERC1155 tokens on behalf of their customers on dedicated blockchain address, but in the same time it can initiate transfer of those assets away.
\nGas required for the transfer from that address is going to be deducted from the providers address - the one, which was used to generate the address on the blockchain.
\nThere are multiple options, how this address can be setup - it cannot be changed in the future:
\nAll of these options could be enabled with a batch mode as well - in 1 transaction, it is possible to transfer multiple different assets from that address, e.g. ETH + USDC + ERC721 token.\nWithout batch mode, 3 separate transaction must have been performed.
\nThis operation deploys a smart contract on the blockchain. More assets you will support, more intial gas will be used for address creation. Batch mode adds more gas for every type.
\nThis API is supported for the following blockchains:
\nThis API is deprecated.
To start with the gas pump, use the API for precalculating the gas pump addresses.
2 credits per API call
\nGenerate new gas pump smart contract address on the blockchain. This address enables custodial providers to receive native assets, ERC20 / ERC721 / ERC1155 tokens on behalf of their customers on dedicated blockchain address, but in the same time it can initiate transfer of those assets away. Gas required for the transfer from that address is going to be deducted from the providers address - the one, which was used to generate the address on the blockchain.
\nThis operation deploys a smart contract on the blockchain.
\nFor paid plans, it is possible to pay for the gas costs - you don't have to provide private key or signatureId. Blockchain fees will be covered by your credits.
\nThis API is supported for the following blockchains:
\n2 credits per API call
\nPrecalculate (generate) gas pump addresses that you can assign to the customers of your custodial application.
\nThis API does not make any changes on the blockchain itself, just generates addresses that follow the blockchain's requirements for the address format; therefore, no gas fee is applied.
\nThis API is supported for the following blockchains:
\nAddress index
\nEach address should be associated with its own index. Use the from and to request body parameters to set a range of index values for the addresses to precalculate. You can start with any number, but we recommend that you start from 0.
In one API call, you can precalculate:
\nIf you need more addresses than one API call can precalculate, make several API calls. For example, if you need 10,000 addresses on Ethereum, make an API call with an index range from 0 through 4,999 and then make another API call with an index range from 5,000 through 9,999.
\nThe order in which the precalculated addresses are returned in the API response is the order of the values in the index range, and the index values are assigned to the addresses accordingly.
For example, you precalculated three gas pump addresses with a range of index values from 3 to 5. The first address in the returned arrray is assigned the index value \"3\", the second one - \"4\", and the third one - \"5\".
\n[\n \"0x8cb76aed9c5e336ef961265c6079c14e9cd3d2ea\", // index is 3\n \"0x5c6079c14e9cd3d2ea8cb76aed9c5e336ef96126\", // index is 4\n \"0xc5e336ef9612614e9cd3d2ea8cb76aed95c6079c\" // index is 5\n]\n\n
The owner of the gas pump addresses
\nThe owner (also referred to as \"master address\") is the blockchain address that will own the precalculated gas pump addresses. The owner will also be paying gas fees for operations made on the gas pump addresses. You have to make sure that the owner always has enough funds to cover these gas fees.
Activated and not activated addresses
\nThe precalculated addresses can be immediately assigned to customers and can receive funds. However, they cannot be used to send funds to other addresses. This is because the addresses are not activated. To make the addresses be able to send funds, activate them.
This API is deprecated.
To start with the gas pump, use the API for precalculating the gas pump addresses.
If you built your gas pump solution using the API for generating a gas pump wallet address and API for generating a custodial wallet address, you can still use this API for getting the custodial wallet address from the transaction. However, we recommend that you switch to the API for precalculating the gas pump addresses.
1 credit per API call
\nGet gas pump smart contract addresses from deploy transaction.
\nThis API is supported for the following blockchains:
\n2 credits per API call
\nTransfer (send) an asset from a gas pump address to the other address.
\nThis operation is usually performed by users in your custodial application: a user who has a gas pump address assigned wants to transfer an asset to some address on the blockchain.
\nThe gas fee for sending the asset will be covered by crypto funds on the master address. Make sure that the master address always has enough funds to cover gas fees.
\nTo be able to send the asset:
\nWith this API, you can send only one asset per API call. If you want to send multiple assets, use the API for transferring multiple assets from a gas pump account.
\nThis API is supported for the following blockchains:
\nSigning a transaction
\nWhen transferring an asset, 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:25 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/gas-pump/transfercustodialwalletbatch.md b/v1.0/Smart Contracts/gas-pump/transfercustodialwalletbatch.md deleted file mode 100644 index 82d1f278..00000000 --- a/v1.0/Smart Contracts/gas-pump/transfercustodialwalletbatch.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Transfer multiple assets from a gas pump address" -slug: "transfercustodialwalletbatch" -excerpt: "2 credits per API call
\nTransfer (send) multiple assets from a gas pump address to one or more addresses.
\nThis operation is usually performed by users in your custodial application: a user who has a gas pump address assigned wants to transfer multiple assets to one or more addresses on the blockchain.
\nThe gas fee for sending the assets will be covered by crypto funds on the master address. Make sure that the master address always has enough funds to cover gas fees.
\nTo be able to send the assets:
\nIf you want to send only one asset, you can also use the API for transferring an asset from a gas pump account.
\nThis API is supported for the following blockchains:
\nSigning a transaction
\nWhen transferring assets, 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:25 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/general.md b/v1.0/Smart Contracts/general.md deleted file mode 100644 index 66cc130e..00000000 --- a/v1.0/Smart Contracts/general.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "General" -slug: "general" -excerpt: "" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 14:16:43 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 14:16:43 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/general/deploycontract.md b/v1.0/Smart Contracts/general/deploycontract.md deleted file mode 100644 index aa2af230..00000000 --- a/v1.0/Smart Contracts/general/deploycontract.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Deploy smart contract" -slug: "deploycontract" -excerpt: "This operation is used to create a new smart contract on the blockchain. The operation is asynchronous and returns a transaction hash. The transaction hash can be used to query the status of the transaction.2 credits per API call
\nBuy an asset listed on the NFT marketplace.
\nYou can buy the asset either for the native blockchain currency (for example, ETH, MATIC, and so on) or for the fungible tokens of the blockchain.
\namount request body parameter).This API is supported for the following blockchains:
\nThe \"execution reverted\" message
\nWhen making this API call, you may get the following message:
\nAlthough one or more Error Occurred [execution reverted] Contract Execution Completed
\nThis message is a result of the marketplace version check and has no impact on completing the API call. You can safely ignore it.
Signing a transaction
\nWhen buying an asset on the NFT marketplace, 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:27 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/marketplace/cancelsellmarketplacelisting.md b/v1.0/Smart Contracts/marketplace/cancelsellmarketplacelisting.md deleted file mode 100644 index 8d80b255..00000000 --- a/v1.0/Smart Contracts/marketplace/cancelsellmarketplacelisting.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Cancel the selling of an asset on the NFT marketplace" -slug: "cancelsellmarketplacelisting" -excerpt: "2 credits per API call
\nCancel the selling of an asset on the NFT marketplace.
\nYou can cancel the selling only if you are the seller of the asset or the marketplace operator. Once the selling is canceled, the asset is returned to the seller.
\nYou cannot cancel the selling if the asset has already been purchased.
\nThis API is supported for the following blockchains:
\nThe \"execution reverted\" message
\nWhen making this API call, you may get the following message:
\nAlthough one or more Error Occurred [execution reverted] Contract Execution Completed
\nThis message is a result of the marketplace version check and has no impact on completing the API call. You can safely ignore it.
Signing a transaction
\nWhen cancelling the selling of an asset, 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/marketplace/generatemarketplace.md b/v1.0/Smart Contracts/marketplace/generatemarketplace.md deleted file mode 100644 index 5736ce08..00000000 --- a/v1.0/Smart Contracts/marketplace/generatemarketplace.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Create an NFT marketplace" -slug: "generatemarketplace" -excerpt: "2 credits per API call
\nDeploy an NFT marketplace smart contract on the blockchain. With a deployed marketplace smart contract, you and your customers can create new listings for assets such as non-fungible tokens and combinations of token types as described by the ERC-721 and ERC-1155 standards on the Ethereum blockchain or by the equivalent standards on the other blockchains. As the marketplace operator, you can set a fee as a percentage of the asset price that will be paid on top of the asset price.
\nThe purchase process looks like the following:
\nbuyAssetFromListing() method is called against the marketplace smart contract) and send the required amount of the native assets to the marketplace smart contract.buyAssetFromListing() method is called against the marketplace smart contract).This API is supported for the following blockchains:
\nSigning a transaction
\nWhen deploying an NFT marketplace 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/marketplace/getmarketplacefee.md b/v1.0/Smart Contracts/marketplace/getmarketplacefee.md deleted file mode 100644 index d33d134b..00000000 --- a/v1.0/Smart Contracts/marketplace/getmarketplacefee.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get the NFT marketplace fee" -slug: "getmarketplacefee" -excerpt: "1 credit per API call
\nGet the NFT marketplace fee.
\nThis API is supported for the following blockchains:
\n1 credit per API call
\nGet the recipient of the NFT marketplace fee.
\nThis API is supported for the following blockchains:
\n1 credit per API call
\nGet information about an NFT marketplace on Solana.
\nThis API is in alpha and is supported only for the mainnet on Solana.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:27 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/marketplace/getmarketplacelisting.md b/v1.0/Smart Contracts/marketplace/getmarketplacelisting.md deleted file mode 100644 index 77f5c53b..00000000 --- a/v1.0/Smart Contracts/marketplace/getmarketplacelisting.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get information about a listing on the NFT marketplace" -slug: "getmarketplacelisting" -excerpt: "1 credit per API call
\nGet information about a specific listing on the NFT marketplace.
\nThis API is supported for the following blockchains:
\n1 credit per API call
\nGet the open, sold, or cancelled listings from the NFT marketplace.
\nThis API is supported for the following blockchains:
\n2 credits per API call
\nCreate a new listing for an asset on the NFT marketplace. The listing can be offered for the native blockchain assets (for example, ETH, MATIC, and so on) or for any fungible tokens.
\nAfter the listing is created, allow the marketplace smart contract to transfer the asset that you are selling.
\nYou can create a listing only for an existing asset that you own (you must be the owner of the asset).
\nThis API is supported for the following blockchains:
\nA known issue on Harmony
\nOn Harmony, when you are viewing a transaction in the Harmony Blockchain Explorer, the transaction status may be displayed as the following:
\nError reverted:x0
\nThis is a known issue with the Harmony Blockchain Explorer. This status does not mean that the transaction failed. You can safely ignore it.
The \"execution reverted\" message
\nWhen making this API call, you may get the following message:
\nAlthough one or more Error Occurred [execution reverted] Contract Execution Completed
\nThis message is a result of the marketplace version check and has no impact on completing the API call. You can safely ignore it.
Signing a transaction
\nWhen creating a new listing on the NFT marketplace, 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/marketplace/updatefee.md b/v1.0/Smart Contracts/marketplace/updatefee.md deleted file mode 100644 index 31e895ae..00000000 --- a/v1.0/Smart Contracts/marketplace/updatefee.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Update the NFT marketplace fee" -slug: "updatefee" -excerpt: "2 credits per API call
\nUpdate the NFT marketplace fee.
\nYou can update the marketplace fee only if you are the marketplace operator.
\nThis API is supported for the following blockchains:
\nSigning a transaction
\nWhen updating the NFT marketplace fee, 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:27 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/marketplace/updatefeerecipient.md b/v1.0/Smart Contracts/marketplace/updatefeerecipient.md deleted file mode 100644 index ce132df6..00000000 --- a/v1.0/Smart Contracts/marketplace/updatefeerecipient.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Update the recipient of the NFT marketplace fee" -slug: "updatefeerecipient" -excerpt: "2 credits per API call
\nUpdate the recipient of the NFT marketplace fee.
\nYou can update the fee recipient only if you are the marketplace operator.
\nThis API is supported for the following blockchains:
\nSigning a transaction
\nWhen updating the recipient of the NFT marketplace fee, 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:27 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/marketplace/updatemarketplace.md b/v1.0/Smart Contracts/marketplace/updatemarketplace.md deleted file mode 100644 index faef7a98..00000000 --- a/v1.0/Smart Contracts/marketplace/updatemarketplace.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Update an NFT marketplace on Solana" -slug: "updatemarketplace" -excerpt: "2 credits per API call
\nUpdate an NFT marketplace on Solana.
\nYou can update it only if you are the marketplace operator.
\nThis API is in alpha and is supported only for the mainnet on Solana.
\nSigning a transaction
\nWhen updating an NFT marketplace, 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:27 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/marketplace/withdrawfeefrommarketplace.md b/v1.0/Smart Contracts/marketplace/withdrawfeefrommarketplace.md deleted file mode 100644 index 7c150035..00000000 --- a/v1.0/Smart Contracts/marketplace/withdrawfeefrommarketplace.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Withdraw funds from the marketplace fee account on Solana" -slug: "withdrawfeefrommarketplace" -excerpt: "2 credits per API call
\nWithdraw funds from the NFT marketplace fee account on Solana.
\nYou can withdraw the funds only if you are the marketplace fee recipient.
\nThis API is in alpha and is supported only for the mainnet on Solana.
\nSigning a transaction
\nWhen withdrawing the funds, 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:27 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/marketplace/withdrawtreasuryfrommarketplace.md b/v1.0/Smart Contracts/marketplace/withdrawtreasuryfrommarketplace.md deleted file mode 100644 index f9a583f0..00000000 --- a/v1.0/Smart Contracts/marketplace/withdrawtreasuryfrommarketplace.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Withdraw funds from the marketplace treasury account on Solana" -slug: "withdrawtreasuryfrommarketplace" -excerpt: "2 credits per API call
\nWithdraw funds from the NFT marketplace treasury account on Solana.
\nYou can withdraw the funds only if you are the marketplace fee recipient.
\nThis API is in alpha and is supported only for the mainnet on Solana.
\nSigning a transaction
\nWhen withdrawing the funds, 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:27 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/multi-tokens-erc-1155-or-compatible.md b/v1.0/Smart Contracts/multi-tokens-erc-1155-or-compatible.md deleted file mode 100644 index 84fed023..00000000 --- a/v1.0/Smart Contracts/multi-tokens-erc-1155-or-compatible.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Multi Tokens (ERC-1155 or compatible)" -slug: "multi-tokens-erc-1155-or-compatible" -excerpt: "" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/multi-tokens-erc-1155-or-compatible/addmultitokenminter.md b/v1.0/Smart Contracts/multi-tokens-erc-1155-or-compatible/addmultitokenminter.md deleted file mode 100644 index 93406fa2..00000000 --- a/v1.0/Smart Contracts/multi-tokens-erc-1155-or-compatible/addmultitokenminter.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Add a Multi Token minter" -slug: "addmultitokenminter" -excerpt: "2 credits per API call
\nAdd Multi Token minter.
\nThis API is supported for the following blockchains:
\nSigning a transaction
\nWhen adding a Multi Token minter, 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.
\nProviding 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:28 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/multi-tokens-erc-1155-or-compatible/burnmultitoken.md b/v1.0/Smart Contracts/multi-tokens-erc-1155-or-compatible/burnmultitoken.md deleted file mode 100644 index badde8f6..00000000 --- a/v1.0/Smart Contracts/multi-tokens-erc-1155-or-compatible/burnmultitoken.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Burn a Multi Token" -slug: "burnmultitoken" -excerpt: "2 credits per API call
\nBurn a fixed amount of Multi Tokens by id. This method destroys Multi Tokens from smart contract defined in contractAddress.
\nThis API is supported for the following blockchains:
\nSigning a transaction
\nWhen burning a Multi Token, 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.
\nProviding 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:28 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/multi-tokens-erc-1155-or-compatible/burnmultitokenbatch.md b/v1.0/Smart Contracts/multi-tokens-erc-1155-or-compatible/burnmultitokenbatch.md deleted file mode 100644 index 3e2fc60f..00000000 --- a/v1.0/Smart Contracts/multi-tokens-erc-1155-or-compatible/burnmultitokenbatch.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Burn multiple Multi Tokens" -slug: "burnmultitokenbatch" -excerpt: "2 credits per API call
\nBurn multiple Multi Token Tokens by id assigned to same address in one transaction. This method destroys any Multi Tokens token from smart contract defined in contractAddress.
\nThis API is supported for the following blockchains:
\nSigning a transaction
\nWhen burning multiple Multi Tokens, 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.
\nProviding 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:28 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/multi-tokens-erc-1155-or-compatible/deploymultitoken.md b/v1.0/Smart Contracts/multi-tokens-erc-1155-or-compatible/deploymultitoken.md deleted file mode 100644 index ee319f63..00000000 --- a/v1.0/Smart Contracts/multi-tokens-erc-1155-or-compatible/deploymultitoken.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Deploy a Multi Token smart contract" -slug: "deploymultitoken" -excerpt: "2 credits per API call
\nDeploy Multi Token Smart Contract. This method creates new ERC1155 Smart Contract (Multi Tokens) on the blockchain. Smart contract is standardized and audited.\nIt is possible to mint, burn and transfer tokens. It is also possible to mint multiple tokens at once.
\nThis API is supported for the following blockchains:
\nSigning a transaction
\nWhen deploying a Multi Token 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.
\nProviding 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/multi-tokens-erc-1155-or-compatible/mintmultitoken.md b/v1.0/Smart Contracts/multi-tokens-erc-1155-or-compatible/mintmultitoken.md deleted file mode 100644 index b7a566e3..00000000 --- a/v1.0/Smart Contracts/multi-tokens-erc-1155-or-compatible/mintmultitoken.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Mint a Multi Token" -slug: "mintmultitoken" -excerpt: "2 credits per API call
\nMint a fixed amount of Multi Token and transfer it to destination account. Create and transfer any Multi Token token from smart contract defined in contractAddress. It is possible to add Metadata to the created token with a more detailed information about instead.
\nThis API is supported for the following blockchains:
\nSigning a transaction
\nWhen minting a Multi Token, 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.
\nProviding 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:28 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/multi-tokens-erc-1155-or-compatible/mintmultitokenbatch.md b/v1.0/Smart Contracts/multi-tokens-erc-1155-or-compatible/mintmultitokenbatch.md deleted file mode 100644 index 50af8512..00000000 --- a/v1.0/Smart Contracts/multi-tokens-erc-1155-or-compatible/mintmultitokenbatch.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Mint multiple Multi Tokens" -slug: "mintmultitokenbatch" -excerpt: "2 credits per API call
\nCreate a fixed amount of multiple Multi Tokens Tokens and transfer them to destination account in one transaction. Create and transfer Multi Tokens tokens from smart contract defined in contractAddress.
\nThis API is supported for the following blockchains:
\nSigning a transaction
\nWhen minting multiple Multi Tokens, 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.
\nProviding 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:28 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/multi-tokens-erc-1155-or-compatible/multitokengetaddressbalance.md b/v1.0/Smart Contracts/multi-tokens-erc-1155-or-compatible/multitokengetaddressbalance.md deleted file mode 100644 index e4bd60af..00000000 --- a/v1.0/Smart Contracts/multi-tokens-erc-1155-or-compatible/multitokengetaddressbalance.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get all Multi Tokens that a blockchain address holds" -slug: "multitokengetaddressbalance" -excerpt: "1 credit per API call
\nGet all Multi Tokens that a blockchain address holds. The Multi Tokens are returned grouped by the smart contracts they were minted on.
\nThis API is supported for the following blockchains:
\n1 credit per API call
\nGet the amount of a specific Multi Token (minted on the smart contract specified by the contractAddress path parameter in the request endpoint URL) that a blockchain address holds.
This API is supported for the following blockchains:
\n1 credit per API call
\nFor multiple blockchain addresses, get the amount of one or multiple Multi Tokens (minted on the smart contract specified by the contractAddress path parameter in the request endpoint URL) that those addresses hold.
This API is supported for the following blockchains:
\nThis endpoint is deprecated. Do not use it.
\nInstead, use this API.
1 credit per API call
\nGet Multi Token contract address from deploy transaction.
\nThis API is supported for the following blockchains:
\n1 credit per API call
\nGet Multi Token metadata.
\nThis API is supported for the following blockchains:
\n1 credit per API call
\nGet Multi Token transaction by transaction hash.
\nThis API is supported for the following blockchains:
\n1 credit per API call
\nGet incoming and outgoing Multi Token transactions on a blockchain address.
\nThis API is supported for the following blockchains:
\n2 credits per API call
\nTransfer a certain amount of Multi Token from account to another account. Transfer Multi Tokens token from smart contract defined in contractAddress.
\nOnly 1 specific token with specified tokenId and value can be transferred. This method invokes ERC1155 method safeTransfer() to transfer the token in case of ETH, Celo and blockchains.
\nThis API is supported for the following blockchains:
\nSigning a transaction
\nWhen transferring a Multi Token, 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.
\nProviding 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:28 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/multi-tokens-erc-1155-or-compatible/transfermultitokenbatch.md b/v1.0/Smart Contracts/multi-tokens-erc-1155-or-compatible/transfermultitokenbatch.md deleted file mode 100644 index 3d5585a3..00000000 --- a/v1.0/Smart Contracts/multi-tokens-erc-1155-or-compatible/transfermultitokenbatch.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Transfer multiple Multi Tokens" -slug: "transfermultitokenbatch" -excerpt: "2 credits per API call
\nTransfer Multi Token Batch from account to various other accounts in one transaction. Transfer multiple Multi Tokens token from smart contract defined in contractAddress.
\nMultiple token with specified tokenIds and values can be transferred. This method invokes ERC1155 method safeTransfer() to transfer the token in case of ETH, Celo and BSC.\n
This API is supported for the following blockchains:
\nSigning a transaction
\nWhen transferring multiple Multi Tokens, 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.
\nProviding 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:28 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/nft-erc-721-or-compatible.md b/v1.0/Smart Contracts/nft-erc-721-or-compatible.md deleted file mode 100644 index abbb813e..00000000 --- a/v1.0/Smart Contracts/nft-erc-721-or-compatible.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "NFT (ERC-721 or compatible)" -slug: "nft-erc-721-or-compatible" -excerpt: "" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/nft-erc-721-or-compatible/nftaddminter.md b/v1.0/Smart Contracts/nft-erc-721-or-compatible/nftaddminter.md deleted file mode 100644 index 6fba712f..00000000 --- a/v1.0/Smart Contracts/nft-erc-721-or-compatible/nftaddminter.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Add a blockchain address as an NFT minter to an NFT smart contract" -slug: "nftaddminter" -excerpt: "2 credits per API call
\nAllow a blockchain address (the minter parameter in the request body) to mint NFTs on your NFT smart contract (the contractAddress parameter in the request body).
NOTE: Use this API only when you are using NFT Express with your own smart contract. For more information, see \"Use your own smart contract to mint NFTs\" in Mint an NFT.
\nDo not use this API in any other case.
This API is supported for the following blockchains:
\nSigning a transaction
\nWhen allowing a blockchain address to mint NFTs, 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/nft-erc-721-or-compatible/nftburnerc721.md b/v1.0/Smart Contracts/nft-erc-721-or-compatible/nftburnerc721.md deleted file mode 100644 index 43a47455..00000000 --- a/v1.0/Smart Contracts/nft-erc-721-or-compatible/nftburnerc721.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Burn an NFT" -slug: "nftburnerc721" -excerpt: "100 credits per API call on Flow
\n2 credits per API call on the other blockchains
Destroy an NFT. Burning the NFT transfers it to an un-spendable blockchain address that no one can access.
\nThis API is supported for the following blockchains:
\nBurning NFTs on Algorand
\nYou can burn only the NFTs that were minted with the address of the manager account specified in the manager parameter in the minting call (see the MintNftExpressAlgorand, MintNftAlgorand, and MintNftAlgorandKMS schemas of the request body).
Burning NFTs on Tezos
\nYou can burn only the NFTs if you are admin or minter of the contract
Signing a transaction
\nWhen burning an NFT, 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:29 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/nft-erc-721-or-compatible/nftdeployerc721.md b/v1.0/Smart Contracts/nft-erc-721-or-compatible/nftdeployerc721.md deleted file mode 100644 index 2877cfd1..00000000 --- a/v1.0/Smart Contracts/nft-erc-721-or-compatible/nftdeployerc721.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Deploy an NFT smart contract" -slug: "nftdeployerc721" -excerpt: "100 credits per API call on Flow
\n2 credits per API call on the other blockchains
Deploy an NFT smart contract on the blockchain. In a deployed NFT smart contract, you can mint NFTs (one NFT at a time or multiple NFTs at once), burn, and transfer NFTs.
\nSmart contracts are standardized and audited. You can review the code of a deployed NFT smart contract here (if the contract is deployed on Flow) or here (if the contract is deployed on any other supported blockchain).
\nThis API is supported for the following blockchains:
\nGeneral NFT smart contracts
\nBy default, an NFT smart contract is deployed as a general NFT smart contract compatible with OpenSea royalties. This is a standard NFT contract with AccessControl and Ownable, enhanced with NFT batch minting. NFTs minted on this smart contract are compatible with OpenSea and its royalty structure.
\n
You can enable public minting for smart contracts. By default, public minting is disabled, which means that only the blockchain address whose private key was used to create the smart contract or the blockchain addresses added to the smart contract as NFT minters will be able to mint NFTs for the contract. To enable public minting and allow anyone to mint NFTs on top of the smart contract, deploy the contract with the publicMint parameter set to true in the request body.
NFT smart contracts and NFT Express
\nIf you want to use NFT Express to mint NFTs on the deployed smart contract, deploy the smart contract as a general NFT smart contract.
\nAfter you have deployed the NFT smart contract, add the Tatum minter address as an NFT minter to your smart contract.
For the complete information about using NFT Express on your smart contract, see \"Use your own smart contract to mint NFTs\" in Mint an NFT.
\nSigning a transaction
\nWhen deploying an NFT 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:29 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/nft-erc-721-or-compatible/nftgetbalanceerc721.md b/v1.0/Smart Contracts/nft-erc-721-or-compatible/nftgetbalanceerc721.md deleted file mode 100644 index a74f059b..00000000 --- a/v1.0/Smart Contracts/nft-erc-721-or-compatible/nftgetbalanceerc721.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get the NFTs from a specific smart contract that a blockchain address holds" -slug: "nftgetbalanceerc721" -excerpt: "1 credit per API call
\nGet the NFTs minted on a specific smart contract (the contractAddress path parameter in the request endpoint URL) that a blockchain address holds.
NOTE: This API works only for the NFT smart contracts deployed using the Tatum smart contract API.
\nThis API is supported for the following blockchains:
\nThis endpoint is deprecated. Do not use it.
\nInstead, use this API.
1 credit per API call
\nGet NFT contract address from deploy transaction.
\nThis API is supported for the following blockchains:
\n1 credit per API call
\nGet metadata of an NFT.
\nThis API is supported for the following blockchains:
\n1 credit per API call + 5 credits for each owned NFT
\nGet all NFTs that a blockchain address holds. The NFTs are returned grouped by the smart contracts they were minted on.
\nThis API is supported for the following blockchains:
\nOn Solana and Algorand, if a blockchain address holds fewer than 50 NFTs, the API also returns each NFT's metadata. If the metadata is not returned, you can obtain it using the API for getting NFT metadata.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:30 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/nft-erc-721-or-compatible/nftgettokensbycollectionerc721.md b/v1.0/Smart Contracts/nft-erc-721-or-compatible/nftgettokensbycollectionerc721.md deleted file mode 100644 index d0139b0f..00000000 --- a/v1.0/Smart Contracts/nft-erc-721-or-compatible/nftgettokensbycollectionerc721.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get all NFTs from a collection" -slug: "nftgettokensbycollectionerc721" -excerpt: "1 credit per API call + 5 credits for each listed NFT
\nGet all NFTs from a collection (all the NFTs that were minted on the smart contract).
\nThis API is supported for the following blockchains:
\n1 credit per API call
\nGet an NFT transaction by its hash.
\nThis API is supported for the following blockchains:
\n1 credit per API call
\nGet incoming and outgoing NFT transactions on a blockchain address.
\nThis API is supported for the following blockchains:
\n1 credit per API call
Get incoming and outgoing transactions for an NFT.
This API is supported for the following blockchains:
100 credits per API call on Flow
\n2 credits per API call on the other blockchains
You can mint NFTs using either of the following methods:
\n\nNFT Express is Tatum's feature that helps you mint NFTs easier than minting natively on a blockchain.
\nWith NFT Express, you can choose whether to mint NFTs on the pre-built NFT smart contract provided by Tatum or on your own smart contract.
\nIf you want to mint NFTs using the pre-built smart contract, you do not need to deploy your own NFT smart contract. You do not need to provide the address of the NFT smart contract and the token ID in the request body either. The address of the smart contract and the token ID are provided automatically by Tatum.
The token ID is autogenerated. It starts with 0 and is increased by 1 for each new NFT. The token ID is calculated separately for each supported blockchain and its mainnet and testnet.
\nFor more information, see our user documentation.
You can mint NFTs on the pre-built smart contract provided by Tatum on the following blockchains:
\nDepending on what blockchain you use, choose the request body schema to use in the API call.
\nMintNftExpress schema of the request body.MintNftExpressAlgorand schema of the request body.manager parameter.MintNftExpressTezos schema of the request body. In order to use this function, it is necessary to deploy the contract using NFT Express transferNftAlgoExpress schema of the request body).MintNftExpressSolana schema of the request body.to parameter of the request body). This address is returned in the nftAccountAddress parameter in the response body, is owned by the recipient's address, and has the same private key.nftAddress parameter.If you want to mint NFTs using your own smart contract, you are going to use an NTF minter, a special blockchain address provided by Tatum that will cover the minting fees. The number of credits equivalent to the fees will be then deducted from the monthly credit allowance of your paid pricing plan.\n
For more information, see our user documentation and the article in the Tatum blog.
\nYou can mint NFTs on your own smart contract on the following blockchains:
\nTo mint NFTs using your own smart contract, do the following:
\nMintNftMinter schema of the request body.chain is the blockchain that you use.to is the blockchain address where to send the minted NFT to.url is the URL of the NFT metadata.minter is the address of the NFT minter that you found in Step 1.contractAddress is the address of your NFT smart contract.tokenId is the the token ID of the NFT.\n{\n \"chain\": \"CELO\",\n \"to\": \"0x8ce4e40889a13971681391aad29e88efaf91f784\",\n \"url\": \"ipfs://QmXJJ6UF5WkF4WTJvsdhiA1etGwBLfpva7Vr9AudGMe3pj\",\n \"contractAddress\": \"0x687422eEA2cB73B5d3e242bA5456b782919AFc85\",\n \"tokenId\": \"0123\",\n \"minter\": \"0xBC2eBA680EE50d685cc4Fe65f102AA70AfB27D3F\"\n}\n\nWhen you make an API call with this request body, the private key of the NFT minter will be added to the request body automatically:\n\n{\n \"chain\": \"CELO\",\n \"to\": \"0x8ce4e40889a13971681391aad29e88efaf91f784\",\n \"url\": \"ipfs://QmXJJ6UF5WkF4WTJvsdhiA1etGwBLfpva7Vr9AudGMe3pj\",\n \"contractAddress\": \"0x687422eEA2cB73B5d3e242bA5456b782919AFc85\",\n \"tokenId\": \"0123\",\n \"minter\": \"0xBC2eBA680EE50d685cc4Fe65f102AA70AfB27D3F\",\n \"fromPrivateKey\": \"0x05e150c73f1920ec14caa1e0b6aa09940899678051a78542840c2668ce5080c2\"\n}\n \nThe following table lists the blockchain addresses of the Tatum NFT minters for the testnet and mainnet of the supported blockchains:
\n| Blockchain | \nMinter address - testnet* | \nMinter address - mainnet** | \n
|---|---|---|
| BNB Smart Chain | \n0xc16ae5e8c985b906935a0cadf4e24f0400531883 | \n0x49678AAB11E001eb3cB2cBD9aA96b36DC2461A94 | \n
| Celo | \n0xBC2eBA680EE50d685cc4Fe65f102AA70AfB27D3F | \n0x49678AAB11E001eb3cB2cBD9aA96b36DC2461A94 | \n
| Ethereum | \n0x53e8577C4347C365E4e0DA5B57A589cB6f2AB848 | \n0x49678AAB11E001eb3cB2cBD9aA96b36DC2461A94 | \n
| Harmony | \n0x8906f62d40293ddca77fdf6714c3f63265deddf0 | \n0x49678AAB11E001eb3cB2cBD9aA96b36DC2461A94 | \n
| Klaytn | \n0x80d8bac9a6901698b3749fe336bbd1385c1f98f2 | \n0x49678AAB11E001eb3cB2cBD9aA96b36DC2461A94 | \n
| Polygon | \n0x542b9ac4945a3836fd12ad98acbc76a0c8b743f5 | \n0x49678AAB11E001eb3cB2cBD9aA96b36DC2461A94 | \n
| Horizen Eon | \n0x53e8577c4347c365e4e0da5b57a589cb6f2ab848 | \n0x625805bf8fe714589ea8c90dbc294e656104c7b3 | \n
*If a minter blockchain address on the testnet does not have sufficient funds to cover the transaction fee, add some amount to it using a crypto faucet of the blockchain.
\n**To be able to use NFT Express on the mainnet, you have to have a paid pricing plan.
For Ethereum specifically, we recommend an Enterprise Plan because transaction fees on Ethereum are very high.
When minting an NFT natively on a blockchain, you are using your own 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.
\nProviding 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.
\nFor 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.
\nYou can mint NFTs natively on the following blockchains:
\nDepending on what blockchain you use, choose the request body schema to use in the API call.
\nMintNftAlgorand schema of the request body.MintNftAlgorandKMS schema of the request body.manager parameter.MintNft schema of the request body.MintNftKMS schema of the request body.MintNftCelo schema of the request body.MintNftKMSCelo schema of the request body.MintNftFlowPK schema of the request body.MintNftFlowMnemonic schema of the request body.MintNftFlowKMS schema of the request body.MintNftSolana schema of the request body.MintNftSolanaKMS schema of the request body.MintNftTron schema of the request body.MintNftKMSTron schema of the request body.MintNftTezos schema of the request body.100 credits per API call on Flow
\n2 credits per API call on the other blockchains
Create multiple NFT Tokens and transfer them to destination account. Create and transfer any NFT tokens from smart contract defined in contractAddress.
\nThis API is supported for the following blockchains:
\n{\n \"to\": [\"0x80d8bac9a6901698b3749fe336bbd1385c1f98f2\"],\n \"url\": [\"ipfs://QmXJJ6UF5WkF4WTJvsdhiA1etGwBLfpva7Vr9AudGMe3pj\"],\n \"tokenId\": [\"9876541124516\"],\n \"contractAddress\":\"0xcd2ada00c48a27faa5cc67f9a1ed55b89ddf7f77\",\n \"minter\": \"0x542b9ac4945a3836fd12ad98acbc76a0c8b743f5\",\n \"chain\": \"MATIC\"\n}\nThe blockchain fee of the performed transaction is paid from the address connected with built-in private key and is debited in form of credits. The credits are debited only if NFT mint requests are performed with paid API key plan.\nWe transform fee to the credits in accordance to the rates provided by the Tatum.\nIf you want to batch mint on ERC-721 contract which is not deployed via Tatum API, your smart contract must contain this method:\nmintMultiple(address[] to, uint256[] tokenId, string[] uri): boolean\nYou can use addresses specified in the bellow table to be used as a minter.\n
| Chain | \nTestnet address | \nMainnet Address | \n
|---|---|---|
| MATIC | \n0x542b9ac4945a3836fd12ad98acbc76a0c8b743f5 | \n0xcf9e127455d28e7362380aec1b92ddee8200b295 | \n
| BSC | \n0xc16ae5e8c985b906935a0cadf4e24f0400531883 | \n0xcf9e127455d28e7362380aec1b92ddee8200b295 | \n
| ONE | \n0x8906f62d40293ddca77fdf6714c3f63265deddf0 | \n0xcf9e127455d28e7362380aec1b92ddee8200b295 | \n
| ETH | \n0x53e8577C4347C365E4e0DA5B57A589cB6f2AB848 | \n0xcf9e127455d28e7362380aec1b92ddee8200b295 | \n
| CELO | \n0xBC2eBA680EE50d685cc4Fe65f102AA70AfB27D3F | \n0xcf9e127455d28e7362380aec1b92ddee8200b295 | \n
| KLAY | \n0x80d8bac9a6901698b3749fe336bbd1385c1f98f2 | \n0xcf9e127455d28e7362380aec1b92ddee8200b295 | \n
100 credits per API call on Flow
\n2 credits per API call on the other blockchains
Transfer an NFT from the smart contract (the contractAddress parameter in the request body) to the specified blockchain address (the to parameter in the request body).
In one API call, you can transfer only one NFT.
\nThis API is supported for the following blockchains:
\nFor Ethereum, Celo, and BNB Smart Chain, transferring NFTs invokes the safeTransfer() method.
Transferring NFTs on Algorand
\ntransferNftAlgoExpress schema of the request body.Transferring NFTs on Solana
\nIf you want to transfer an NFT that was minted using NFT Express, use the transferNftSolana or transferNftSolanaKMS schema of the request body. In the request body:\n
from parameter to the address that you used in the to parameter in the request body of the minting call.to parameter to the recipient's address.contractAddress parameter to the address from the nftAddress parameter returned in the response body of the minting call.fromPrivateKey/signatureId parameter to the private key/signature ID of the blockchain address that you specified in the from parameter.Signing a transaction
\nWhen transferring an NFT, 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.
\nFor 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.
\nNOTE: This does not apply to transferring NFTs that were minted on Algorand using NFT Express (see earlier in this section).
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:29 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Smart Contracts/nft-erc-721-or-compatible/nftverifyincollection.md b/v1.0/Smart Contracts/nft-erc-721-or-compatible/nftverifyincollection.md deleted file mode 100644 index 2af96a01..00000000 --- a/v1.0/Smart Contracts/nft-erc-721-or-compatible/nftverifyincollection.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Verify an NFT in an NFT collection on Solana" -slug: "nftverifyincollection" -excerpt: "2 credits per API call
\nVerify an NFT in an NFT collection on Solana. Verifying an NFT sets the Verified parameter to true for the NFT, which means that the NFT is really a part of the collection. To know more about Solana collections and verification, refer to the Solana user documentation.
The collection must be a sized collection that was introduced in Version 1.3 of the Metaplex Token Metadata program. The NFT must have been minted in this collection.
\nThis API is supported only for Solana.
\nSigning a transaction
\nWhen verifying an NFT, 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.
\nFor 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.
" -category: 65c0c834f1cd450023eab1ed -hidden: false -createdAt: "Mon Feb 05 2024 11:36:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:36:29 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Storage/blockchain-storage.md b/v1.0/Storage/blockchain-storage.md deleted file mode 100644 index 9b8f2960..00000000 --- a/v1.0/Storage/blockchain-storage.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Blockchain storage" -slug: "blockchain-storage" -excerpt: "" -category: 65c0c8703a8063001c639edf -hidden: false -createdAt: "Mon Feb 05 2024 11:37:22 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:37:22 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Storage/blockchain-storage/getlog.md b/v1.0/Storage/blockchain-storage/getlog.md deleted file mode 100644 index 699b335e..00000000 --- a/v1.0/Storage/blockchain-storage/getlog.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get a log record" -slug: "getlog" -excerpt: "1 credit per API call
\nGet a log data record from the Ethereum blockchain (only the mainnet or the Sepolia testnet).
" -category: 65c0c8703a8063001c639edf -hidden: false -createdAt: "Mon Feb 05 2024 11:37:22 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:37:22 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Storage/blockchain-storage/storelog.md b/v1.0/Storage/blockchain-storage/storelog.md deleted file mode 100644 index 5b6d58d9..00000000 --- a/v1.0/Storage/blockchain-storage/storelog.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Store a log record" -slug: "storelog" -excerpt: "2 credits per API call + additional credits based on the size of the stored data and the type of the blockchain
\nStore data on the blockchain.
\nThe total cost of a transaction on Ethereum (in credits) depends on the size of the data. The data is stored as a string in the hexadecimal format, and the maximum size of the data is approximately 130 kB on the mainnet and 30 kB on testnet. Every 5 characters cost 1 credit.
\nTherefore, one API call with 1 kB of data (1024 characters) would cost 205 credits.
This API is supported for the following blockchains:
\nGets data from the IPFS.
" -category: 65c0c8703a8063001c639edf -hidden: false -createdAt: "Mon Feb 05 2024 11:37:22 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:37:22 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Storage/ipfs/storeipfs.md b/v1.0/Storage/ipfs/storeipfs.md deleted file mode 100644 index 77001e6d..00000000 --- a/v1.0/Storage/ipfs/storeipfs.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Store data to IPFS" -slug: "storeipfs" -excerpt: "Stores file on the IPFS. We are leveraging web3.storage from Protocol Labs for free storage on the IPFS.
" -category: 65c0c8703a8063001c639edf -hidden: false -createdAt: "Mon Feb 05 2024 11:37:22 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:37:22 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Subscriptions/notification-subscriptions.md b/v1.0/Subscriptions/notification-subscriptions.md deleted file mode 100644 index b95f5af1..00000000 --- a/v1.0/Subscriptions/notification-subscriptions.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Notification subscriptions" -slug: "notification-subscriptions" -excerpt: "" -category: 65c0c7b84eb96b0034e72a50 -hidden: false -createdAt: "Mon Feb 05 2024 11:34:18 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:34:18 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Subscriptions/notification-subscriptions/createsubscription.md b/v1.0/Subscriptions/notification-subscriptions/createsubscription.md deleted file mode 100644 index e857578d..00000000 --- a/v1.0/Subscriptions/notification-subscriptions/createsubscription.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Create a subscription" -slug: "createsubscription" -excerpt: "Please expand below notification types to see more details.\n\n---\n\n2 credits per API call + credits spent on subscriptions themselves
\nEach subscription type consumes a different number of credits.
For Free plans, there is a monthly limit of sent webhooks, which is 1000.
\nIf the webhook is sent unsuccessfully, it will be retried. The number of retries depends on the plan.
\nCreate a subscription as an HTTP web hook.
\nThe following subscription types are available:
\n| Chain | \nTestnet/Mainnet | \nToken assets support | \nPlan limitation | \nCredit consumption / day / address | \n
|---|---|---|---|---|
| Solana | \nYes/Yes | \nSOL, SPL and NFTs | \nFree plans - 10 addresses across all blockchains, Paid plans - unlimited addresses across all blockchains | \n50 credits / day / address | \n
| Ethereum | \nYes (Sepolia, Goerli)/Yes | \nETH, Internal transfers, ERC20, ERC721, ERC1155 | \nFree plans - 10 addresses across all blockchains, Paid plans - unlimited addresses across all blockchains | \n25 credits / day / address | \n
| Polygon | \nYes/Yes | \nMATIC, ERC20, ERC721, ERC1155 | \nFree plans - 10 addresses across all blockchains, Paid plans - unlimited addresses across all blockchains | \n40 credits / day / address | \n
| Celo | \nYes/Yes | \nCELO, Internal transfers, ERC20, ERC721, ERC1155 | \nFree plans - 10 addresses across all blockchains, Paid plans - unlimited addresses across all blockchains | \n25 credits / day / address | \n
| Klaytn | \nYes/Yes | \nKlay, ERC20, ERC721, ERC1155 | \nFree plans - 10 addresses across all blockchains, Paid plans - unlimited addresses across all blockchains | \n25 credits / day / address | \n
| Bitcoin | \nYes/Yes | \nBTC | \nFree plans - 10 addresses across all blockchains, Paid plans - unlimited addresses across all blockchains | \n5 credits / day / address | \n
| Litecoin | \nYes/Yes | \nLTC | \nFree plans - 10 addresses across all blockchains, Paid plans - unlimited addresses across all blockchains | \n7 credits / day / address | \n
| Bitcoin Cash | \nYes/Yes | \nBCH, only incoming transactions | \nFree plans - 10 addresses across all blockchains, Paid plans - unlimited addresses across all blockchains | \n5 credits / day / address | \n
| Dogecoin | \nYes/Yes | \nDOGE, only incoming transactions | \nFree plans - 10 addresses across all blockchains, Paid plans - unlimited addresses across all blockchains | \n7 credits / day / address | \n
| Tron | \nYes/Yes | \nTron, TRC10/TRC20 | \nFree plans - 10 addresses across all blockchains, Paid plans - unlimited addresses across all blockchains | \n30 credits / day / address | \n
| Binance Smart Chain | \nYes/Yes | \nBSC, BEP20, ERC721, ERC1155 | \nFree plans - 10 addresses across all blockchains, Paid plans - unlimited addresses across all blockchains | \n40 credits / day / address | \n
{\n \"address\": \"FykfMwA9WNShzPJbbb9DNXsfgDgS3XZzWiFgrVXfWoPJ\", // the address on which the transaction occurs; for EVM-based chains, this is the sender's address\n \"txId\": \"2rdy3YCZHSwvpWtuDom1d4Jjy5UU9STLxF3ffXau6GToReDkfw8wEgX541fvzvh6btVC5D8iNapcKTXfPsoDBk7A\", // the transaction ID\n \"blockNumber\": 110827114, // the block number; does not appear if the transaction is in the mempool (for EVM-based blockchains)\n \"asset\": \"3gUeeR3BfVhukYJMwtHownRtRkGcf1bvwiV8TbKMZBVz\", // the asset of the transaction: for token assets, this is the token address; for native blochckain assets, this is the name of the asset (for example, SOL)\n \"amount\": \"1\", // the amount of the asset that was credited to (+) or debited from (-) the address; for EVM-based chains, when \"counterAddress\" is present, the amount is always positive\n \"tokenId\": \"1\", // (ERC-721 / ERC-1155 only) the ID of the transferred token\n \"type\": \"token\", // the type of the transaction; can be either \"native\" or \"token\"\n \"mempool\": true, // (EVM-based blockchains only) if appears and set to \"true\", the transaction is in the mempool; if set to \"false\" or does not appear at all, the transaction has been added to a block\n \"counterAddress\": undefined // an optional counter party address of the transaction; for EVM-based blockchains, this is the recipient's address\n \"addressesRiskRatio\": [ // (optional, subject to change; for Solana mainnet only) risk levels assigned to the addresses with which the address communicated within the transaction; the addresses are assessed using the AML/CFT solution by blockmate.io, see https://docs.blockmate.io/docs/risk-API/sources\n {\"vTEfAhXTmvgFmepgfhzBbRrJ4EtUP9adbMJjpzLsDMk\": 0},\n {\"zBbRrJ4EtUP9adbMJjpzLsDMkvTEfAhXTmvgFmepgfh\": 100}\n ]\n}\n5 credits are debited for each fired web hook.| Chain | \nAvailable chains (the \"chain\" parameter in the response payload) | \nCredit consumption / day | \n
|---|---|---|
| Ethereum | \nethereum-sepolia / ethereum-goerli / ethereum-mainnet | \n500,000 credits / day | \n
| Polygon | \npolygon-mumbai / polygon-mainnet | \n500,000 credits / day | \n
| Celo | \ncelo-testnet / celo-mainnet | \n500,000 credits / day | \n
| Klaytn | \nklaytn-baobab / klaytn-cypress | \n500,000 credits / day | \n
| BNB Smart Chain | \nbsc-testnet / bsc-mainnet | \n500,000 credits / day | \n
{\n \"events\": [\n {\n \"timestamp\": 1661961758000,\n \"from\": \"0x0000000000000000000000000000000000000000\",\n \"to\": \"0xfa4e7035b34294407e5df1603215983d65e5a773\",\n \"tokenId\": \"14671\",\n \"txId\": \"0x916fcf878656f7a3772317697e6d2740ac8b1b7dbe6d029aa79592fd72f3fb0b\",\n \"contractAddress\": \"0x55a2430e32dcebc3649120f26f917d1f0686f74c\",\n \"type\": \"erc721\",\n \"amount\": \"1\",\n \"logIndex\": 578,\n \"metadataURI\": \"https://graphigo.prd.galaxy.eco/metadata/0x55a2430e32dcebc3649120f26f917d1f0686f74c/14671.json\"\n }\n ],\n \"blockNumber\": 32522207,\n \"chain\": \"polygon-mainnet\",\n \"subscriptionType\": \"CONTRACT_NFT_TXS_PER_BLOCK\"\n }\n1 credit is debited for each fired web hook.| Chain | \nAvailable chains (the \"chain\" parameter in the response payload) | \nCredit consumption / day | \n
|---|---|---|
| Ethereum | \nethereum-sepolia / ethereum-goerli / ethereum-mainnet | \n500,000 credits / day | \n
| Polygon | \npolygon-mumbai / polygon-mainnet | \n500,000 credits / day | \n
| Celo | \ncelo-testnet / celo-mainnet | \n500,000 credits / day | \n
| Klaytn | \nklaytn-baobab / klaytn-cypress | \n500,000 credits / day | \n
| BNB Smart Chain | \nbsc-testnet / bsc-mainnet | \n500,000 credits / day | \n
{\n \"events\": [\n {\n \"timestamp\": 1661961758000,\n \"from\": \"0x85bd970cf0e49acd572f9c2d608713bc55b5ee0e\",\n \"to\": \"0x9ab31230d5413e4af01af9bb697651a3c70c95c9\",\n \"tokenId\": \"1450000023306\",\n \"txId\": \"0x565b9ca6b7b5ff1b1ce0725acd785dbf5ff0930d5ff547bad044c0960291555f\",\n \"contractAddress\": \"0xdb6290f355a528a7284bdd528b05a78fb05226ca\",\n \"type\": \"erc1155\",\n \"amount\": \"1\",\n \"logIndex\": 571,\n \"metadataURI\": \"https://touhao.bj.bcebos.com/nft/metadata/1450000023306.json\"\n }\n ],\n \"blockNumber\": 32522207,\n \"chain\": \"polygon-mainnet\",\n \"subscriptionType\": \"CONTRACT_MULTITOKEN_TXS_PER_BLOCK\"\n}\n1 credit is debited for each fired web hook.| Chain | \nAvailable chains (the \"chain\" parameter in the response payload) | \nCredit consumption / day | \n
|---|---|---|
| Ethereum | \nethereum-sepolia / ethereum-goerli / ethereum-mainnet | \n50,000 credits / day | \n
| Polygon | \npolygon-mumbai / polygon-mainnet | \n50,000 credits / day | \n
| Celo | \ncelo-testnet / celo-mainnet | \n50,000 credits / day | \n
| Klaytn | \nklaytn-baobab / klaytn-cypress | \n50,000 credits / day | \n
| BNB Smart Chain | \nbsc-testnet / bsc-mainnet | \n50,000 credits / day | \n
{\n \"events\": [\n {\n \"txId\": \"0xc98307f09ed527d5cff8305e8f65226b790e3317ded10b9e58f6f07286dcf8f1\",\n \"logIndex\": 326,\n \"timestamp\": 1661774265000,\n \"address\": \"0xc2132d05d31c914a87c6611c10748aeb04b58e8f\",\n \"topic_0\": \"0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef\",\n \"topic_1\": \"0x000000000000000000000000a91ab7d77892a559d2a95baaf1d748fc97c65d29\",\n \"topic_2\": \"0x0000000000000000000000009b08288c3be4f62bbf8d1c20ac9c5e6f9467d8b7\",\n \"topic_3\": null,\n \"data\": \"0x0000000000000000000000000000000000000000000000000000000002c9e3e4\"\n }\n ],\n \"blockNumber\": 32447538,\n \"chain\": \"polygon-mumbai\",\n \"subscriptionType\": \"CONTRACT_LOG_EVENT\"\n}\n1 credit is debited for each fired web hook.{\n \"date\": 1619176527481,\n \"amount\": \"0.005\",\n \"currency\": \"BTC\",\n \"subscriptionType\":\"ACCOUNT_INCOMING_BLOCKCHAIN_TRANSACTION\",\n \"accountId\": \"6082ab462936b4478117c6a0\",\n \"reference: \"c9875708-4ba3-41c9-a4cd-271048b41b9a\", // the reference of the transaction in the virtual account\n \"txId\": \"45af182a0ffab58e5ba32fee57b297b2260c6e23a1de5ddc76c7ee22d72dea99\",\n \"blockHash\": \"45af182a0ffab58e5ba32fee57b297b2260c6e23a1de5ddc76c7ee22d72dea99\", // the hash of the block, might not be present every time\n \"blockHeight\": 12345,\n \"from\": \"SENDER_ADDRESS\", // might not be present every time; not present for UTXO-based blockchains\n \"to\": \"RECIPIENT_ADDRESS_CONNECTED_TO_LEDGER_ACCOUNT\", // the blockchain address of the recipient\n \"index\": 5 // for UTXO-based blockchains (BCH, BTC, DOGE, LTC), this is the index of the output in the transaction\n}\n1 credit is debited for each monitored account every day.{\n \"date\": 1619176527481,\n \"amount\": \"0.005\",\n \"currency\": \"BTC\",\n \"accountId\": \"6082ab462936b4478117c6a0\",\n \"reference: \"c9875708-4ba3-41c9-a4cd-271048b41b9a\", // the reference of the transaction in the virtual account\n \"txId\": \"45af182a0ffab58e5ba32fee57b297b2260c6e23a1de5ddc76c7ee22d72dea99\",\n \"blockHash\": \"45af182a0ffab58e5ba32fee57b297b2260c6e23a1de5ddc76c7ee22d72dea99\", // the hash of the block, might not be present every time; if set to \"null\", the transaction is in the mempool (for EVM-based blockchains)\n \"blockHeight\": 12345, // if set to \"null\", the transaction is in the mempool (for EVM-based blockchains)\n \"from\": \"SENDER_ADDRESS\", // might not be present every time; not present for UTXO-based blockchains (BCH, BTC, DOGE, LTC)\n \"to\": \"RECIPIENT_ADDRESS_CONNECTED_TO_LEDGER_ACCOUNT\", // the blockchain address of the recipient\n \"index\": 5 // for UTXO-based blockchains (BCH, BTC, DOGE, LTC), this is the index of the output in the transaction\n}\n1 credit is debited for each monitored account every day.{\n \"created\": 1619176527481,\n \"amount\": \"0.005\",\n \"price\": \"0.02\",\n \"type\": \"SELL\",\n \"pair\": \"VC_CHF/VC_CHF3\",\n \"id\": \"6082ab462936b4478117c6a0\", // id of the trade\n \"currency1AccountId\": \"6082ab462936b4478117c6a0\",\n \"currency2AccountId\": \"6082ab512936b4478117c6a2\",\n \"fee\": null,\n \"feeAccountId\": null,\n \"isMaker\": true,\n \"expiredWithoutMatch\": false\n}\n10 credits will be debited for every monitored customer every day.{\n \"created\": 1619176527481,\n \"amount\": \"0.005\",\n \"orderAmount\": \"0.1\",\n \"price\": \"0.02\",\n \"type\": \"SELL\",\n \"pair\": \"VC_CHF/VC_CHF3\",\n \"id\": \"6082ab462936b4478117c6a0\", // id of the trade\n \"currency1AccountId\": \"6082ab462936b4478117c6a0\",\n \"currency2AccountId\": \"6082ab512936b4478117c6a2\",\n \"fee\": null,\n \"feeAccountId\": null,\n \"isMaker\": true,\n \"expiredWithoutMatch\": false\n}\n10 credits will be debited for every monitored customer every day.\n {\n \"txId\": \"0x026f4f05b972c09279111da13dfd20d8df04eff436d7f604cd97b9ffaa690567\",\n \"reference\": \"90270634-5b07-4fad-b17b-f82899953533\",\n \"accountId\": \"6086ed0744c45b24d4fbd039\",\n \"currency\": \"BSC\",\n \"withdrawalId\": \"608fe5b73a893234ba379ab2\",\n \"address\": \"0x8ce4e40889a13971681391AAd29E88eFAF91f784\",\n \"amount\": \"0.1\",\n \"blockHeight\": 8517664\n }\n10 credits will be debited every day, 1 credit for every included transaction notified via web hook.{\n \"signatureId\": \"6082ab462936b4478117c6a0\",\n \"error\": \"Error message from the KMS\"\n}\n10 credits will be debited every day.{\n \"signatureId\": \"6082ab462936b4478117c6a0\",\n \"txId\": \"0x7bb7d3b90567e89f999f2e3d263bc3738a018dbbcfa9f5397678cf17cdf0235f\"\n}\n10 credits will be debited every day.Cancel existing subscription.
" -category: 65c0c7b84eb96b0034e72a50 -hidden: false -createdAt: "Mon Feb 05 2024 11:34:18 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:34:19 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Subscriptions/notification-subscriptions/disablewebhookhmac.md b/v1.0/Subscriptions/notification-subscriptions/disablewebhookhmac.md deleted file mode 100644 index 77e4abb3..00000000 --- a/v1.0/Subscriptions/notification-subscriptions/disablewebhookhmac.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Disable HMAC webhook digest" -slug: "disablewebhookhmac" -excerpt: "Disable HMAC hash ID on the fired webhooks from Tatum API.
" -category: 65c0c7b84eb96b0034e72a50 -hidden: false -createdAt: "Mon Feb 05 2024 11:34:18 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:34:19 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Subscriptions/notification-subscriptions/enablewebhookhmac.md b/v1.0/Subscriptions/notification-subscriptions/enablewebhookhmac.md deleted file mode 100644 index 5b48165b..00000000 --- a/v1.0/Subscriptions/notification-subscriptions/enablewebhookhmac.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Enable HMAC webhook digest" -slug: "enablewebhookhmac" -excerpt: "Enable HMAC hash ID on the fired webhooks from Tatum API.\nIn order to make sure that a webhook is sent by us, we have the possibility to sign it with the HMAC Sha512 Hex algorithm.
\nTo verify that a webhook is sent by us\n
JSON.stringify(req.body)
require('crypto').createHmac('sha512', hmacSecret).update(JSON.stringify(req.body)).digest('base64').List all webhooks.
" -category: 65c0c7b84eb96b0034e72a50 -hidden: false -createdAt: "Mon Feb 05 2024 11:34:18 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:34:19 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Subscriptions/notification-subscriptions/getallwebhookscount.md b/v1.0/Subscriptions/notification-subscriptions/getallwebhookscount.md deleted file mode 100644 index 4d948893..00000000 --- a/v1.0/Subscriptions/notification-subscriptions/getallwebhookscount.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Count of found entities for get webhook request" -slug: "getallwebhookscount" -excerpt: "Count of webhooks that were found from /v3/subscription/webhook
" -category: 65c0c7b84eb96b0034e72a50 -hidden: false -createdAt: "Mon Feb 05 2024 11:34:18 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:34:19 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Subscriptions/notification-subscriptions/getsubscriptionreport.md b/v1.0/Subscriptions/notification-subscriptions/getsubscriptionreport.md deleted file mode 100644 index 875dbe1c..00000000 --- a/v1.0/Subscriptions/notification-subscriptions/getsubscriptionreport.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Obtain report for subscription" -slug: "getsubscriptionreport" -excerpt: "Obtain report from subscription based on its type. Following reports are supported:\n
List all active subscriptions.
" -category: 65c0c7b84eb96b0034e72a50 -hidden: false -createdAt: "Mon Feb 05 2024 11:34:18 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:34:19 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Subscriptions/notification-subscriptions/getsubscriptionscount.md b/v1.0/Subscriptions/notification-subscriptions/getsubscriptionscount.md deleted file mode 100644 index 2f9457f4..00000000 --- a/v1.0/Subscriptions/notification-subscriptions/getsubscriptionscount.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Count of subscriptions" -slug: "getsubscriptionscount" -excerpt: "Count of subscriptions that were found from /v3/subscription
" -category: 65c0c7b84eb96b0034e72a50 -hidden: false -createdAt: "Mon Feb 05 2024 11:34:18 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:34:19 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/TROUBLESHOOTING/blockchain-operations-1.md b/v1.0/TROUBLESHOOTING/blockchain-operations-1.md deleted file mode 100644 index 076c8c9a..00000000 --- a/v1.0/TROUBLESHOOTING/blockchain-operations-1.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "Blockchain Operations" -slug: "blockchain-operations-1" -excerpt: "" -category: 65ae6349f216f9001c42cc4d -hidden: false -createdAt: "Mon Jan 29 2024 07:39:43 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Fri Feb 09 2024 08:53:08 GMT+0000 (Coordinated Universal Time)" ---- -This section covers all the error you might face when you are broadcasting a transaction on chain. - -Check this page if your transaction is stuck on chain. diff --git a/v1.0/TROUBLESHOOTING/blockchain-operations-1/algorand-1.md b/v1.0/TROUBLESHOOTING/blockchain-operations-1/algorand-1.md deleted file mode 100644 index 4e33e563..00000000 --- a/v1.0/TROUBLESHOOTING/blockchain-operations-1/algorand-1.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Algorand" -slug: "algorand-1" -excerpt: "" -category: 65ae6349f216f9001c42cc4d -hidden: false -createdAt: "Mon Feb 12 2024 12:12:33 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 12 2024 12:12:33 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/TROUBLESHOOTING/blockchain-operations-1/algorand-1/algo-get-account-transactions.md b/v1.0/TROUBLESHOOTING/blockchain-operations-1/algorand-1/algo-get-account-transactions.md deleted file mode 100644 index 5337e970..00000000 --- a/v1.0/TROUBLESHOOTING/blockchain-operations-1/algorand-1/algo-get-account-transactions.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: "Algo - Get Account Transactions" -slug: "algo-get-account-transactions" -excerpt: "" -category: 65ae6349f216f9001c42cc4d -hidden: false -createdAt: "Mon Feb 12 2024 12:13:05 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 12 2024 12:15:25 GMT+0000 (Coordinated Universal Time)" ---- -Getting all Account transactions in from an Algorand address is possible via an RPC node request. - -### Example request - -```curl cURL -curl --location --request GET 'https://api.tatum.io/v3/blockchain/node/ALGO/v2/accounts/MLD3LCNGOK2SXAVNUYMW3WVG5LBN4Z5HFARB3VLMZCENFW############/transactions?nodeType=INDEXER' \ ---header 'x-api-key: {API_KEY}' -//Response: -{ - "current-round": 26834617, - "next-token": "0DOZAQAAAAAMAAAA", - "transactions": [ - { - "asset-transfer-transaction": { - "amount": 0, - "asset-id": 27165954, - "close-amount": 0, - "receiver": "MLD3LCNGOK2SXAVNUYMW3WVG5LBN4Z5HFARB3VLMZCENFW############" - }, - "close-rewards": 0, - "closing-amount": 0, - "confirmed-round": 26834571, - "fee": 1000, - "first-valid": 26834569, -... -``` - -## Good to Know - -- Algorand RPC node method `/v2/accounts/{account-id}/transactions` looks up account transactions, returning newest to oldest. -- This request requires a redirect to the `INDEXER` node via `?nodeType=INDEXER` diff --git a/v1.0/TROUBLESHOOTING/blockchain-operations-1/cancel-or-replace-a-blockchain-transaction.md b/v1.0/TROUBLESHOOTING/blockchain-operations-1/cancel-or-replace-a-blockchain-transaction.md deleted file mode 100644 index 5f4db7c8..00000000 --- a/v1.0/TROUBLESHOOTING/blockchain-operations-1/cancel-or-replace-a-blockchain-transaction.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: "Cancel or Replace a blockchain transaction" -slug: "cancel-or-replace-a-blockchain-transaction" -excerpt: "" -category: 65ae6349f216f9001c42cc4d -hidden: false -createdAt: "Mon Jan 29 2024 10:11:40 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 08:42:10 GMT+0000 (Coordinated Universal Time)" ---- -In some cases, you may want to cancel or replace a transaction. - -- **Cancel**: for EVM chains (like Ethereum), it may be possible to replace a pending transaction in the mempool via another one with value zero (0) to your own address. UTXO transactions can't be "canceled". -- **Replace**: for UTXO chains (like Bitcoin), it may be possible to increase the fee of a pending transaction via [RBF](https://tatumdocs.readme.io/docs/bitcoin-replace-by-fee-and-stuck-transactions-in-the-mempool) (if enabled) or via [CPFP](https://tatumdocs.readme.io/docs/bitcoin-cpfp-and-stuck-transactions-in-the-mempool). For EVM chains, it may be possible to replace a pending transaction. - -## Cancelling a transaction - -EVM chains allow a bit of a trick to cancel a pending (unconfirmed) transaction in the mempool: - -1. Verify the transaction you want to cancel is not confirmed yet and is still pending in the mempool. Check an Explorer. -2. Verify the nonce value of the unconfirmed transaction you want to cancel. -3. Create a new transaction where the sender and receiver blockchain address is the same with a zero (0) amount. Use the same nonce value you got from step 2 and put a much higher fee. -4. Broadcast this transaction. Ideally, the miners will prioritize this new transaction over the original due to a higher fee. -5. If all worked well, your new transaction will get confirmed first and the original will be dropped due to invalid. - -## Replacing a transaction - -UTXO chains may allow [RBF](https://tatumdocs.readme.io/docs/bitcoin-replace-by-fee-and-stuck-transactions-in-the-mempool) or in some cases [CPFP](https://tatumdocs.readme.io/docs/bitcoin-cpfp-and-stuck-transactions-in-the-mempool) on pending (unconfirmed) transactions. - -EVM chains may allow replacing a transaction using the same method as if you were to cancel it: - -1. Verify the transaction you want to cancel is not confirmed yet and is still pending in the mempool. Check an Explorer. -2. Verify the nonce value of the unconfirmed transaction you want to replace. -3. Create a new transaction where the receiver blockchain address may or may not be the same as in the original to replace. Use the same nonce value you got from step 2 and put a much higher fee. -4. Broadcast this transaction. Ideally, the miners will prioritize this new transaction over the original due to a higher fee. -5. If all works well, your new transaction will get confirmed first and the original will be dropped due to invalid. - -## Good to know - -- Incorrectly executed transactions may result in the loss of funds. -- Blockchain transactions, once confirmed, are irreversible. There's no guarantee of success in canceling or replacing them. diff --git a/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1.md b/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1.md deleted file mode 100644 index ea968cb0..00000000 --- a/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "EVM (like Ethereum)" -slug: "evm-like-ethereum-1" -excerpt: "" -category: 65ae6349f216f9001c42cc4d -hidden: false -createdAt: "Tue Feb 06 2024 16:35:09 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Tue Feb 06 2024 16:35:23 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1/bnb-beacon-chain-account-balance-attributes.md b/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1/bnb-beacon-chain-account-balance-attributes.md deleted file mode 100644 index 315de45f..00000000 --- a/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1/bnb-beacon-chain-account-balance-attributes.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: "BNB - Beacon Chain Account Balance Attributes" -slug: "bnb-beacon-chain-account-balance-attributes" -excerpt: "" -category: 65ae6349f216f9001c42cc4d -hidden: false -createdAt: "Sun Feb 25 2024 11:44:34 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Sun Feb 25 2024 11:44:39 GMT+0000 (Coordinated Universal Time)" ---- -BNB Beacon Chain Account balance comes with additional balance attributes - -- **Available**: the amount of tokens that can be transferred, and spent to swap (buy) other assets -- **Locked**: the amount of tokens that has been used in any outstanding orders. Once the order terminates (either filled, canceled or expired), the locked amount will decrease. -- **Frozen**: the amount of tokens that has been frozen via Freeze transactions. - -> 📘 Additional information is available at [the following link](https://docs.bnbchain.org/docs/beaconchain/learn/accounts/#account-balance). diff --git a/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1/bnb-bep2-and-bep20-token-transfers.md b/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1/bnb-bep2-and-bep20-token-transfers.md deleted file mode 100644 index 72f58b77..00000000 --- a/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1/bnb-bep2-and-bep20-token-transfers.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: "BNB - BEP2 and BEP20 Token Transfers" -slug: "bnb-bep2-and-bep20-token-transfers" -excerpt: "" -category: 65ae6349f216f9001c42cc4d -hidden: false -createdAt: "Sun Feb 25 2024 11:48:13 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Sun Feb 25 2024 11:48:18 GMT+0000 (Coordinated Universal Time)" ---- -It's possible to transfer NBN BEP2 and BEP20 tokens with Tatum: - -### v3 REST API endpoints: - -- [Send BEP2 over BNB](https://apidoc.tatum.io/tag/BNB-Beacon-Chain/#operation/BnbBlockchainTransfer) -- [Send BEP20 over BSC](https://apidoc.tatum.io/tag/BNB-Smart-Chain/#operation/BscBlockchainTransfer) - - Alternative: [Send BEP20 token via compatible ERC-20](https://apidoc.tatum.io/tag/Fungible-Tokens-(ERC-20-or-compatible)/#operation/Erc20Transfer) method, where **Request Body Schema** is `ChainTransferBscBep20` and chain is BSC diff --git a/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1/bnb-transactions-over-beacon-chain-and-smart-chain.md b/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1/bnb-transactions-over-beacon-chain-and-smart-chain.md deleted file mode 100644 index c0c6adf2..00000000 --- a/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1/bnb-transactions-over-beacon-chain-and-smart-chain.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: "BNB - Transactions over Beacon Chain and Smart Chain" -slug: "bnb-transactions-over-beacon-chain-and-smart-chain" -excerpt: "" -category: 65ae6349f216f9001c42cc4d -hidden: false -createdAt: "Sun Feb 25 2024 11:56:01 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Sun Feb 25 2024 11:56:05 GMT+0000 (Coordinated Universal Time)" ---- -Binance has two types of chains: - -1. BNB Beacon Chain -2. BSC Smart Chain. - -> 📘 BNB is the native asset of both chains. - -## BNB Smart Chain (BSC) - BEP20 - -- In the Tatum v3 REST API, we call its currency with the symbol "`BSC`". -- BSC chain supports smart contracts and decentralized applications (DApps) since it's EVM compatible. -- BSC chain addresses follow the EVM address format. BSC chain addresses start with the prefix `0x` -- [BSC Explorer](https://bscscan.com/) -- [BSC chain API documentation link](https://apidoc.tatum.io/tag/BNB-Smart-Chain/) -- v3 REST API endpoint to make a BSC transfer: "`/v3/bsc/transaction`" - -## BNB Beacon Chain (BNB) - BEP2 - -- In the Tatum v3 REST API, we call its currency with the symbol "`BNB`". -- The BNB chain is standalone, not EVM-compatible. -- BNB chain addresses start with the prefix `bnb` -- [BNB Explorer](https://explorer.bnbchain.org/) -- [BNB chain v3 REST API documentation link](https://apidoc.tatum.io/tag/BNB-Beacon-Chain/) -- v3 REST API endpoint to make a BNB transfer: "`/v3/bnb/transaction`" diff --git a/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1/fee-estimate-gasprice-and-insufficient-funds.md b/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1/fee-estimate-gasprice-and-insufficient-funds.md deleted file mode 100644 index 7f3e73ff..00000000 --- a/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1/fee-estimate-gasprice-and-insufficient-funds.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -title: "Fee Estimate, GasPrice and Insufficient funds Error" -slug: "fee-estimate-gasprice-and-insufficient-funds" -excerpt: "" -category: 65ae6349f216f9001c42cc4d -hidden: false -createdAt: "Sun Feb 25 2024 11:04:59 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Sun Feb 25 2024 11:05:14 GMT+0000 (Coordinated Universal Time)" ---- -When building a transaction over EVM chains (like Ethereum), a common pitfall in using manual fees is adding `gasPrice` in `Wei` instead of `Gwei`. When this happens, you will likely get an error looking as follows: - -```json -ERROR: { - statusCode: 403, - errorCode: 'eth.tx.preparation', - message: 'Transaction preparation failure.', - cause: 'Insufficient funds send transaction from account ####### -> available balance is 1800000000000000, required balance is 7.233615778886385e+23' -} - -``` - -## Fee Estimate - -Tatum Fee estimates endpoints return values in `Wei`. - -- Estimate the fee for an Ethereum transaction - [v3 REST API endpoint](https://apidoc.tatum.io/tag/Blockchain-fees#operation/EthEstimateGas) -- Estimate the fee for multiple Ethereum transactions - [v3 REST API endpoint](https://apidoc.tatum.io/tag/Blockchain-fees#operation/EthEstimateGasBatch) - -### Example ETH Fee Estimate: - -```json cURL -curl --location 'https://api.tatum.io/v3/ethereum/gas' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "from": "0xBF5c7e33a316cf7D86eBF4014bCf798c6962####", - "to": "0xce864aaec47f07ee8ba7e60a37ff141298f7####", - "amount": "0.018" -}' -//response: -{ - "gasLimit": "21000", - "gasPrice": "43698096524", //The unit hereis in Wei! - "estimations": { - "safe": "43698096524", - "standard": "43698096524", - "fast": "43698096524", - "baseFee": "43914769922" - } -} -``` - -## Sending Ethereum with manual fees - -When building an Ethereum transaction, if you want to input the transaction fee manually, make sure the `gasPrice` is in `Gwei`. - -> 📘 1 Gwei (Giga-wei) is equal to 1,000,000,000 Wei. Therefore, to convert Wei to Gwei, you have to divide the amount in Wei by 1,000,000,000. Alternatively, you may use an online conversion such as [eth-converter.com](https://eth-converter.com/) - -### Example ETH transaction with Manual Fees: - -```json cURL -curl --location 'https://api.tatum.io/v3/ethereum/transaction' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: ##Mainnet_API_KEY' \ ---data '{ - "to": "0xd2c4b6434410e4af062ee3c280327c8ece11####", - "currency": "ETH", - "amount": "0.0017", - "fromPrivateKey": "****", - "fee": { - "gasLimit": "21000", - "gasPrice": "44" //unit in Gwei! -> Estimate returned "fast": "43698096524", - } -}' -``` diff --git a/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1/get-erc-20-or-compatibletoken-balance.md b/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1/get-erc-20-or-compatibletoken-balance.md deleted file mode 100644 index 67a460a1..00000000 --- a/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1/get-erc-20-or-compatibletoken-balance.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: "Get ERC-20 (or compatible)Token Balance" -slug: "get-erc-20-or-compatibletoken-balance" -excerpt: "" -category: 65ae6349f216f9001c42cc4d -hidden: false -createdAt: "Sun Feb 25 2024 11:49:44 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Sun Feb 25 2024 11:50:57 GMT+0000 (Coordinated Universal Time)" ---- -[Getting the ERC-20 Token balance](https://apidoc.tatum.io/tag/Fungible-Tokens-(ERC-20-or-compatible)/#operation/Erc20GetBalance) of an address is possible via the following dedicated v3 REST API endpoint. diff --git a/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1/getting-the-contractaddress-or-tokenaddress-from-a-transaction-hash.md b/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1/getting-the-contractaddress-or-tokenaddress-from-a-transaction-hash.md deleted file mode 100644 index bd172af7..00000000 --- a/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1/getting-the-contractaddress-or-tokenaddress-from-a-transaction-hash.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: "Get the contractaddress or tokenaddress from a transaction hash" -slug: "getting-the-contractaddress-or-tokenaddress-from-a-transaction-hash" -excerpt: "" -category: 65ae6349f216f9001c42cc4d -hidden: false -createdAt: "Mon Feb 12 2024 12:21:27 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Sun Feb 25 2024 07:26:39 GMT+0000 (Coordinated Universal Time)" ---- -When you deploy a Smart Contract, you get as a response a transaction hash. - -### Example response - -```json JSON -{ - "txId": "0x532cb74e9b5388a6ae46cf6d68e38f3ed28738c80949726b2b8b641bad58783f" -} -``` - -To get the `contractAddress`, you can use [the following REST API endpoint](https://apidoc.tatum.io/tag/Blockchain-utils#operation/SCGetContractAddress). - -### Example request (Polygon - testnet) - -```curl -curl --location 'https://api.tatum.io/v3/blockchain/sc/address/MATIC/0x532cb74e9b5388a6ae46cf6d68e38f3ed28738c80949726b2b8b641bad58783f' \ ---header 'x-api-key: {API_KEY}' -//response: -{"contractAddress":"0x5775f95675e23062e3e4a0683f03f22f012df7ce"} -``` diff --git a/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1/invoke-method-in-a-smart-contract.md b/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1/invoke-method-in-a-smart-contract.md deleted file mode 100644 index ca2fe200..00000000 --- a/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1/invoke-method-in-a-smart-contract.md +++ /dev/null @@ -1,170 +0,0 @@ ---- -title: "Invoke method in a Smart Contract" -slug: "invoke-method-in-a-smart-contract" -excerpt: "" -category: 65ae6349f216f9001c42cc4d -hidden: false -createdAt: "Sun Feb 11 2024 20:44:37 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Sun Feb 11 2024 20:44:37 GMT+0000 (Coordinated Universal Time)" ---- -You can [invoke a method in a Smart Contract (SC)](https://apidoc.tatum.io/tag/Ethereum/#operation/EthBlockchainSmartContractInvocation) to read or write. This is done through the ABI (Application Binary Interface) method. - -- **Read**: could be used to read the balance of a specific token on that smart contract. -- **Write**: could be used to do something like burning some of the total minted tokens when the contract was originally deployed. - -## Disclaimer - -Tatum ensures the endpoint "Invoke a method in an SC" works against the blockchain. - -> 🚧 Troubleshooting issues in successfully invoking a method in an SC is out of the scope of Tatum's staff. Users may check the related SC code, and ABI documentation and reach out to the SC creator. - -## How to invoke a Smart Contract - -Example with a minted smart contract for ERC20 on BSC. - -1. Deploy Smart Contract - ```json cURL - curl --location --request POST 'https://api.tatum.dev/v3/blockchain/token/deploy' \ - --header 'X-Api-Key: {API_KEY}' \ - --header 'Content-Type: application/json' \ - --data-raw '{ - "chain": "BSC", - "symbol": "invoke_Token", - "name": "invToken", - "totalCap": "10000000", - "supply": "10000000", - "digits": 18, - "address": "0x6b598e8be2629380c7dc0a95ca5b59923a136436", - "fromPrivateKey": "0x200cc2960b8b75e1fe4cf461e6e02d1b9da869c7d46995709671232b228e6346" - }' - //Response - { - "txId": "0x86fe1d7f65c7c80a67ad85aeb5ec92df4b5cbabae82955da1bf3eb1fae1eb2cb" - } - ``` -2. Get the SC address from the explorer. Example: [`0x3fc5facec56e5b40df4a8abcebf7873259e340b6`] -3. Click on the [Contract] tab: - - [block:image]{"images":[{"image":["https://files.readme.io/5ac2196-sc_code_1.png","",""],"align":"center"}]}[/block] - - [block:image]{"images":[{"image":["https://files.readme.io/cbf2ea6-sc_code_2.png","",""],"align":"center"}]}[/block] -4. On the "**Code Decompilation result**", grab the related info from decompiled code. If you know the type of SC, use its public ABI to figure out what the JSON body looks like for a specific method. -5. **READ** method example: `balanceOf` >> to get balance of that token. - ```json cURL - { - "contractAddress": "0x3fc5facec56e5b40df4a8abcebf7873259e340b6", - "methodName": "balanceOf", - "methodABI": { - "constant": true, - "inputs": [ - { - "name": "owner", - "type": "address" - } - ], - "name": "balanceOf", - "outputs": [ - { - "name": "", - "type": "uint256" - } - ], - "payable": false, - "stateMutability": "view", - "type": "function" - }, - "params": [ - "{{address1}}" - ] - } - //Response - { - "data": "10000000000000000000000000" >> which matches the original minted tokens - } - ``` -6. **WRITE** method example: `burn` >> to decrease #original minted tokens - ```json cURL - { - "contractAddress": "0x3fc5facec56e5b40df4a8abcebf7873259e340b6", - "methodName": "burn", - "methodABI": { - "constant": false, - "inputs": [ - { - "name": "to", - "type": "uint256" - } - ], - "name": "burn", - "outputs": [ - { - "name": "", - "type": "bool" - } - ], - "payable": false, - "stateMutability": "nonpayable", - "type": "function" - }, - "params": [ - 10 - ], - "fromPrivateKey": "{{pk1}}" - } - //Response - { - "txId": "0x1d77e9ed8a8ed84444f0b818f666c488eb6de77aef7329e324685cd2e84fd968" - } - ``` - -- Check in the Explorer to find burn transaction: - - [block:image]{"images":[{"image":["https://files.readme.io/cd23957-cs_invoke_burn.png","",""],"align":"center"}]}[/block] - -## ERC-20 ABI Documentation - -- [ERC-20 ABI](https://gist.github.com/veox/8800debbf56e24718f9f483e1e40c35c) -- [ERC-20 OpenZeppelin](https://docs.openzeppelin.com/contracts/2.x/api/token/erc20) - -## About Smart Contract code format - -Smart Contracts are applications inside the blockchain with an interaction interface, where ABI can be described with JSON. - -For ERC-20 and using this interface, you can do some actions with it. Every entry of it shows the corresponding method available to call. The only difference compared to the usual method call in a programming language is that it has expanded definitions. - -### Example: - -```json cURL -{ - "constant": false, - "inputs": [ - { - "name": "_from", - "type": "address" - }, - { - "name": "_to", - "type": "address" - }, - { - "name": "_value", - "type": "uint256" - } - ], - "name": "transferFrom", - "outputs": [ - { - "name": "", - "type": "bool" - } - ], - "payable": false, - "stateMutability": "nonpayable", - "type": "function" - }, - -//This is the same as this: -transferFrom(_from: address, _to: address, _value: uint256): bool -``` - -Other flags show if stateMutability is required (we may say tx on chain, for further reading - solidity state mutability), or if it is a constant of SC or more. diff --git a/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1/multi-tokens-erc-1155-name-and-symbol.md b/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1/multi-tokens-erc-1155-name-and-symbol.md deleted file mode 100644 index 86b9f518..00000000 --- a/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1/multi-tokens-erc-1155-name-and-symbol.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: "Multi tokens (ERC-1155) name and symbol" -slug: "multi-tokens-erc-1155-name-and-symbol" -excerpt: "" -category: 65ae6349f216f9001c42cc4d -hidden: false -createdAt: "Sun Feb 11 2024 21:50:48 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Sun Feb 11 2024 21:50:52 GMT+0000 (Coordinated Universal Time)" ---- -By definition, `name` and `symbol` found in the ERC-20 and ERC-721 standards are not available. - -### Name - -The name function (for human-readable asset names, on-chain) was removed from the standard to allow the Metadata JSON to be the definitive asset name and reduce duplication of data. - -### Symbol - -The symbol function was not included since creators did not believe this is a globally useful piece of data to identify a generic virtual item/asset and is also prone to collisions. Short-hand symbols are used in tickers and currency trading, but they aren’t as useful outside of that space. - -> 📘 Find additional information ar [the following link](https://eips.ethereum.org/EIPS/eip-1155#rationale). - -## Good to know - -To get `name` and `symbol`, you need to deploy and use your own smart contract via [the following endpoint](https://apidoc.tatum.io/tag/Multi-Tokens-(ERC-1155-or-compatible)/#operation/DeployMultiToken). - -The mentioned endpoint contains the parameter `URI` on which you will be able to enter an IPFS URL from an uploaded \*.json file in the same way you would do when minting an ERC-712 NFT. - -### Example: - -```json JSON -//Endpoint: /v3/multitoken/deploy, where: - -"uri": "https://bafkreiebg3ugqtumak2ueyf2j2sbggt47hxjvbozkxbgyssebufmbgp3fa", -``` diff --git a/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1/nonce-what-is-it-and-optional-use.md b/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1/nonce-what-is-it-and-optional-use.md deleted file mode 100644 index 800631fb..00000000 --- a/v1.0/TROUBLESHOOTING/blockchain-operations-1/evm-like-ethereum-1/nonce-what-is-it-and-optional-use.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: "Nonce - What is it and optional use" -slug: "nonce-what-is-it-and-optional-use" -excerpt: "" -category: 65ae6349f216f9001c42cc4d -hidden: false -createdAt: "Tue Feb 06 2024 17:43:30 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 26 2024 06:59:50 GMT+0000 (Coordinated Universal Time)" ---- -In blockchain technology, the `nonce` is a transaction counter that helps to prevent double-spending and replay attacks on a blockchain network. This value is attached to each Ethereum and EVM-compatible chain sender address. - -Ethereum and other EVM-compatible blockchains require the `nonce` value for each transaction to ensure that the same transaction is not executed twice and that no one can replay a previously sent transaction. - -With Tatum, when the `nonce` is not specified when making a transaction on Ethereum and other EVM-compatible chains, our Engine automatically adds it based on the sender's address. - -> 📘 The Tatum engine has a delay when automatically calculating the nonce. Users with a high transaction broadcast volume should use a manual nonce value. Otherwise, errors about "replacement transaction" will be common. - -## Finding the nonce value - -### v3 REST API - -You can get the current nonce value for their Ethereum sender address by making an API call. - -- Endpoint:1 credit per API call
\nGet an estimated block height (number) for some future point in time.
\nNote that this API returnes an estimation of what the block height might be and not the exact block height.
\nThis API is supported for the following blockchains:
\n1 credit per API call
\nGet the blockchain address of a smart contract by the ID of its deployment transaction.
\nThis API is supported for the following blockchains:
\n1 credit per API call
\nGet the current exchange rate for exchanging fiat/crypto assets.
\nBy default, the base pair (the target asset) is EUR. When obtaining the exchange rate for an asset (for example, BTC), the value returned by the API expresses the amount of EUR that can be currently exchanged into 1 BTC.
" -category: 65c0c8ebe177ab0016cda349 -hidden: false -createdAt: "Mon Feb 05 2024 11:39:25 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:26 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Utils/exchange-rate/getexchangerates.md b/v1.0/Utils/exchange-rate/getexchangerates.md deleted file mode 100644 index 0bc23d4b..00000000 --- a/v1.0/Utils/exchange-rate/getexchangerates.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get the current exchange rates for exchanging fiat/crypto assets" -slug: "getexchangerates" -excerpt: "1 credit per pair per API call
\nGet the current exchange rates for exchanging fiat/crypto assets.
\nWhen obtaining the exchange rate for an asset (for example, BTC), the value returned by the API expresses the amount of EUR that can be currently exchanged into 1 BTC.
" -category: 65c0c8ebe177ab0016cda349 -hidden: false -createdAt: "Mon Feb 05 2024 11:39:25 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:26 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Utils/service-utils.md b/v1.0/Utils/service-utils.md deleted file mode 100644 index b3d6a2ca..00000000 --- a/v1.0/Utils/service-utils.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Service utils" -slug: "service-utils" -excerpt: "" -category: 65c0c8ebe177ab0016cda349 -hidden: false -createdAt: "Mon Feb 05 2024 11:39:25 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:25 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Utils/service-utils/freezeapikey.md b/v1.0/Utils/service-utils/freezeapikey.md deleted file mode 100644 index 6f7ea9b1..00000000 --- a/v1.0/Utils/service-utils/freezeapikey.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Freeze API Key" -slug: "freezeapikey" -excerpt: "Freeze the API Key.\nIt's not possible to perform sensitive operations like send ledger transaction, send off-chain transaction, send blockchain transaction,\nbroadcast blockchain transaction, perform Order book trade or create blockage. Only read operations are permitted.
" -category: 65c0c8ebe177ab0016cda349 -hidden: false -createdAt: "Mon Feb 05 2024 11:39:25 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:26 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Utils/service-utils/getcredits.md b/v1.0/Utils/service-utils/getcredits.md deleted file mode 100644 index eb6d529b..00000000 --- a/v1.0/Utils/service-utils/getcredits.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get information about your credit consumption for the last month" -slug: "getcredits" -excerpt: "1 credit per API call
\nGet information about your credit consumption for the last month (used credits per day).
" -category: 65c0c8ebe177ab0016cda349 -hidden: false -createdAt: "Mon Feb 05 2024 11:39:25 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:26 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Utils/service-utils/getversion.md b/v1.0/Utils/service-utils/getversion.md deleted file mode 100644 index 015b7886..00000000 --- a/v1.0/Utils/service-utils/getversion.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get API version" -slug: "getversion" -excerpt: "Get current version of the API.
" -category: 65c0c8ebe177ab0016cda349 -hidden: false -createdAt: "Mon Feb 05 2024 11:39:25 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:26 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Utils/service-utils/unfreezeapikey.md b/v1.0/Utils/service-utils/unfreezeapikey.md deleted file mode 100644 index c8260607..00000000 --- a/v1.0/Utils/service-utils/unfreezeapikey.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Unfreeze API Key" -slug: "unfreezeapikey" -excerpt: "Unfreeze the API Key.\nIt's possible to perform sensitive operations like send ledger transaction, send off-chain transaction, send blockchain transaction,\nbroadcast blockchain transaction, perform Order book trade or create blockage again.
" -category: 65c0c8ebe177ab0016cda349 -hidden: false -createdAt: "Mon Feb 05 2024 11:39:25 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:39:26 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/account.md b/v1.0/Virtual Accounts/account.md deleted file mode 100644 index c2f10186..00000000 --- a/v1.0/Virtual Accounts/account.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Account" -slug: "account" -excerpt: "" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/account/activateaccount.md b/v1.0/Virtual Accounts/account/activateaccount.md deleted file mode 100644 index 30b0f82d..00000000 --- a/v1.0/Virtual Accounts/account/activateaccount.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Activate account" -slug: "activateaccount" -excerpt: "Activates an account.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/account/blockamount.md b/v1.0/Virtual Accounts/account/blockamount.md deleted file mode 100644 index 1bf1eaa3..00000000 --- a/v1.0/Virtual Accounts/account/blockamount.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Block an amount in an account" -slug: "blockamount" -excerpt: "Blocks an amount in an account. Any number of distinct amounts can be blocked in one account.\nEvery new blockage has its own distinct ID, which is used as a reference. When the amount is blocked, it is debited from the available balance of the account.\nThe account balance remains the same. The account balance represents the total amount of funds in the account. The available balance represents the total amount of funds that can be used to perform transactions. When an account is frozen, the available balance is set to 0 minus all blockages for the account.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:11 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/account/createaccount.md b/v1.0/Virtual Accounts/account/createaccount.md deleted file mode 100644 index cb377746..00000000 --- a/v1.0/Virtual Accounts/account/createaccount.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Create a virtual account" -slug: "createaccount" -excerpt: "2 credits per API call
\nCreate a new virtual account for a customer.
\nYou can create a virtual account for any supported cryptocurrency, fiat currency, Tatum virtual currency, or fungible tokens created within Tatum. Once the currency/asset is set for a virtual account, it cannot be changed.
\nVirtual account balance
\nA virtual account has its own balance. The balance can be logically presented by the account balance and available balance:
\naccountBalance) represents all assets on the account, both available and blocked.availableBalance) represents the account balance minus the blocked assets. Use the available balance to determine how much a customer can send or withdraw from their virtual account.Cryptocurrency virtual accounts
\nWhen you create a virtual account based on a cryptocurrency (for example, BTC or ETH), you have to provide the extended public key (xpub) of the blockchain wallet that will be connected to this account.
NOTE: Adding xpub to the virtual account does not connect any specific blockchain address to this account. xpub is a generator of addresses, not an address itself.
Not all blockchains provide xpub for wallets, or Tatum may not support wallets on some blockchains. In such cases, use the wallet address or the account address instead.
xpub provided; use address from the generated wallet instead.xpub from the generated wallet.xpub provided; use address from the generated wallet instead.xpub from the generated wallet instead.xpub from the generated wallet instead.xpub from the generated wallet.xpub from the generated wallet.xpub provided; use address from the generated blockchain address instead.xpub from the generated wallet.xpub from the generated wallet.xpub from the generated wallet.xpub from the generated wallet.xpub from the generated wallet.xpub from the generated wallet.xpub provided; use address from the generated wallet instead.xpub from the generated wallet.xpub from the generated wallet.xpub provided; use address from the generated account instead.xpub provided; use address from the generated account instead.Connect a virtual account to the blockchain
\nxpub, generate a new blockchain address for this account.xpub, assign an existing blockchain address to this account.You can connect multiple blockchain addresses to one virtual account.
\nDigital assets:
\n0x2791bca1f2de4661ed88a30c99a7a9449aa84174 on Polygon mainnet.0x3c499c542cef5e3811e1192ce70d8cc03d5c3359 on Polygon mainnet.Creates new accounts for the customer in a batch call.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:11 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/account/deactivateaccount.md b/v1.0/Virtual Accounts/account/deactivateaccount.md deleted file mode 100644 index 7bae8b7e..00000000 --- a/v1.0/Virtual Accounts/account/deactivateaccount.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Deactivate account" -slug: "deactivateaccount" -excerpt: "Deactivates an account. Only accounts with account and available balances of zero can be deactivated. Deactivated accounts are not visible in the list of accounts, it is not possible to send funds to these accounts or perform transactions. However, they are still present in the ledger and all transaction histories.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/account/deleteallblockamount.md b/v1.0/Virtual Accounts/account/deleteallblockamount.md deleted file mode 100644 index da3d1163..00000000 --- a/v1.0/Virtual Accounts/account/deleteallblockamount.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Unblock all blocked amounts in an account" -slug: "deleteallblockamount" -excerpt: "Unblocks previously blocked amounts in an account. Increases the available balance in the account where the amount was blocked.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/account/deleteblockamount.md b/v1.0/Virtual Accounts/account/deleteblockamount.md deleted file mode 100644 index 26bdf4f6..00000000 --- a/v1.0/Virtual Accounts/account/deleteblockamount.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Unblock a blocked amount in an account" -slug: "deleteblockamount" -excerpt: "Unblocks a previously blocked amount in an account. Increases the available balance in the account where the amount was blocked.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/account/freezeaccount.md b/v1.0/Virtual Accounts/account/freezeaccount.md deleted file mode 100644 index 510b8675..00000000 --- a/v1.0/Virtual Accounts/account/freezeaccount.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Freeze account" -slug: "freezeaccount" -excerpt: "Disables all outgoing transactions. Incoming transactions to the account are available. When an account is frozen, its available balance is set to 0. This operation will create a new blockage of type ACCOUNT_FROZEN, which is automatically deleted when the account is unfrozen.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:12 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/account/getaccountbalance.md b/v1.0/Virtual Accounts/account/getaccountbalance.md deleted file mode 100644 index 6ff0d0a0..00000000 --- a/v1.0/Virtual Accounts/account/getaccountbalance.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get account balance" -slug: "getaccountbalance" -excerpt: "Get balance for the account.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:11 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/account/getaccountbyaccountid.md b/v1.0/Virtual Accounts/account/getaccountbyaccountid.md deleted file mode 100644 index 8d4da9ac..00000000 --- a/v1.0/Virtual Accounts/account/getaccountbyaccountid.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get account by ID" -slug: "getaccountbyaccountid" -excerpt: "Gets active account by ID. Displays all information regarding the given account.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:11 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/account/getaccounts.md b/v1.0/Virtual Accounts/account/getaccounts.md deleted file mode 100644 index 05752f20..00000000 --- a/v1.0/Virtual Accounts/account/getaccounts.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "List all accounts" -slug: "getaccounts" -excerpt: "Lists all accounts. Inactive accounts are also visible.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/account/getaccountsbycustomerid.md b/v1.0/Virtual Accounts/account/getaccountsbycustomerid.md deleted file mode 100644 index 749c88ad..00000000 --- a/v1.0/Virtual Accounts/account/getaccountsbycustomerid.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "List all customer accounts" -slug: "getaccountsbycustomerid" -excerpt: "Lists all accounts associated with a customer. Only active accounts are visible.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:11 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/account/getaccountscount.md b/v1.0/Virtual Accounts/account/getaccountscount.md deleted file mode 100644 index d6a6bd9b..00000000 --- a/v1.0/Virtual Accounts/account/getaccountscount.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Count of found entities for get accounts request" -slug: "getaccountscount" -excerpt: "Count of accounts that were found from /v3/ledger/account
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/account/getblockamount.md b/v1.0/Virtual Accounts/account/getblockamount.md deleted file mode 100644 index 5a8dcea1..00000000 --- a/v1.0/Virtual Accounts/account/getblockamount.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get blocked amounts in an account" -slug: "getblockamount" -excerpt: "Gets blocked amounts for an account.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/account/getblockamountbyid.md b/v1.0/Virtual Accounts/account/getblockamountbyid.md deleted file mode 100644 index ab8306ea..00000000 --- a/v1.0/Virtual Accounts/account/getblockamountbyid.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get blocked amount by ID" -slug: "getblockamountbyid" -excerpt: "Gets blocked amount by id.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/account/unblockamountwithtransaction.md b/v1.0/Virtual Accounts/account/unblockamountwithtransaction.md deleted file mode 100644 index 0bc4e45c..00000000 --- a/v1.0/Virtual Accounts/account/unblockamountwithtransaction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Unblock an amount in an account and perform a transaction" -slug: "unblockamountwithtransaction" -excerpt: "Unblocks a previously blocked amount in an account and invokes a ledger transaction from that account to a different recipient.\nIf the request fails, the amount is not unblocked.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:11 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/account/unfreezeaccount.md b/v1.0/Virtual Accounts/account/unfreezeaccount.md deleted file mode 100644 index ddbb97b5..00000000 --- a/v1.0/Virtual Accounts/account/unfreezeaccount.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Unfreeze account" -slug: "unfreezeaccount" -excerpt: "Unfreezes a previously frozen account. Unfreezing a non-frozen account not affect the account.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:12 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/account/updateaccountbyaccountid.md b/v1.0/Virtual Accounts/account/updateaccountbyaccountid.md deleted file mode 100644 index b7c786e1..00000000 --- a/v1.0/Virtual Accounts/account/updateaccountbyaccountid.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Update account" -slug: "updateaccountbyaccountid" -excerpt: "Update account by ID. Only a small number of fields can be updated.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:11 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/blockchain-addresses.md b/v1.0/Virtual Accounts/blockchain-addresses.md deleted file mode 100644 index f40e040c..00000000 --- a/v1.0/Virtual Accounts/blockchain-addresses.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Blockchain addresses" -slug: "blockchain-addresses" -excerpt: "" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/blockchain-addresses/addressexists.md b/v1.0/Virtual Accounts/blockchain-addresses/addressexists.md deleted file mode 100644 index 5555c631..00000000 --- a/v1.0/Virtual Accounts/blockchain-addresses/addressexists.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Check whether a blockchain address is assigned to a virtual account" -slug: "addressexists" -excerpt: "1 credit per API call
\nCheck whether a blockchain address with the specified cryptocurrency is registered within Tatum and is assigned to a virtual account (that is, whether this blockchain address is a deposit address associated with the virtual account).
\nIf the blockchain address is assigned to a virtual account, information about this account is returned. Otherwise, an error message is returned.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:14 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/blockchain-addresses/assignaddress.md b/v1.0/Virtual Accounts/blockchain-addresses/assignaddress.md deleted file mode 100644 index 3dc3a2d2..00000000 --- a/v1.0/Virtual Accounts/blockchain-addresses/assignaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Assign a blockchain address to a virtual account" -slug: "assignaddress" -excerpt: "2 credits per API call
\nAssign an existing blockchain address to a virtual account. The blockchain address becomes a deposit address associated with this account.Use this API when the virtual account has no default extended public key (xpub) and deposit addresses are handled manually.
You can assign multiple blockchain addresses to one virtual account. When you have multiple blockchain addresses assigned to the same virtual account, you aggregate various blockchain transactions from different addresses under a single account.
You can deposit funds from another blockchain address to a deposit address associated with the virtual account, and the funds will be credited to that virtual account.
Scanning for incoming deposits
\nBy default, deposit addresses are scanned for incoming deposits. Deposit addresses are automatically synchronized with the associated virtual account, and you can see incoming deposits on the virtual account.
Scanning deposit addresses for incoming deposits consumes 20 credits per address per day.
If you want to be notified about certain events occurring on the deposit addresses, subscribe for notifications.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/blockchain-addresses/generatedepositaddress.md b/v1.0/Virtual Accounts/blockchain-addresses/generatedepositaddress.md deleted file mode 100644 index 13c27e42..00000000 --- a/v1.0/Virtual Accounts/blockchain-addresses/generatedepositaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Create a deposit address for a virtual account" -slug: "generatedepositaddress" -excerpt: "2 credits per API call
\nOn Flow, additional 3000 credits are consumed for each created address.
Create a deposit address associated with a virtual account.
\nYou can create multiple deposit addresses for one virtual account. When you have multiple deposit addresses created for the same virtual account, you aggregate various blockchain transactions from different addresses under a single account.
You can deposit funds from another blockchain address to a deposit address associated with the virtual account, and the funds will be credited to that virtual account.
Scanning for incoming deposits
\nBy default, deposit addresses are scanned for incoming deposits. Deposit addresses are automatically synchronized with the associated virtual account, and you can see incoming deposits on the virtual account.
Scanning deposit addresses for incoming deposits consumes 20 credits per address per day.
If you want to be notified about certain events occurring on the deposit addresses, subscribe for notifications.
\nVirtual account cryptocurrency
\nDepending on the cryptocurrency of the virtual account, this API generates:
\nFor fore information about supported blockchains and address types, see the API for creating virtual accounts.
\nDeposit addresses are generated in the natural order of the extended public key provided in the virtual account. The derivation index is the representation of that order; it starts from 0 and ends at 2^31.
\nWhen a new deposit address is generated, the last not used index is used to generate the address. You can skip some addresses to a different index, which means all the skipped addresses will no longer be used.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/blockchain-addresses/generatedepositaddressesbatch.md b/v1.0/Virtual Accounts/blockchain-addresses/generatedepositaddressesbatch.md deleted file mode 100644 index f6f76d54..00000000 --- a/v1.0/Virtual Accounts/blockchain-addresses/generatedepositaddressesbatch.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Create multiple deposit addresses for a virtual account" -slug: "generatedepositaddressesbatch" -excerpt: "2 credits per API call + 1 credit for each created address
\nOn Flow, additional 3000 credits are consumed for each created address.
Create multiple deposit addresses associated with a virtual account.
\nWhen you have multiple deposit addresses created for the same virtual account, you aggregate various blockchain transactions from different addresses under a single account.
You can deposit funds from another blockchain address to a deposit address associated with the virtual account, and the funds will be credited to that virtual account.
Scanning for incoming deposits
\nBy default, deposit addresses are scanned for incoming deposits. Deposit addresses are automatically synchronized with the associated virtual account, and you can see incoming deposits on the virtual account.
Scanning deposit addresses for incoming deposits consumes 20 credits per address per day.
If you want to be notified about certain events occurring on the deposit addresses, subscribe for notifications.
\nVirtual account cryptocurrency
\nDepending on the cryptocurrency of the virtual account, this API generates:
\nFor fore information about supported blockchains and address types, see the API for creating virtual accounts.
\nDeposit addresses are generated in the natural order of the extended public key provided in the virtual account. The derivation index is the representation of that order; it starts from 0 and ends at 2^31.
\nWhen a new deposit address is generated, the last not used index is used to generate the address. You can skip some addresses to a different index, which means all the skipped addresses will no longer be used.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/blockchain-addresses/getalldepositaddresses.md b/v1.0/Virtual Accounts/blockchain-addresses/getalldepositaddresses.md deleted file mode 100644 index d19c2614..00000000 --- a/v1.0/Virtual Accounts/blockchain-addresses/getalldepositaddresses.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get all deposit addresses for a virtual account" -slug: "getalldepositaddresses" -excerpt: "1 credit per API call
\nGet all deposit addresses generated for a virtual account.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:14 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/blockchain-addresses/removeaddress.md b/v1.0/Virtual Accounts/blockchain-addresses/removeaddress.md deleted file mode 100644 index 910c3062..00000000 --- a/v1.0/Virtual Accounts/blockchain-addresses/removeaddress.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Remove a deposit address from a virtual account" -slug: "removeaddress" -excerpt: "1 credit per API call
\nRemove a deposit address from the virtual account.
\nThe deposit address will no longer be scanned for incoming deposits. You will no longer be able to generate this address again.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:14 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/blockchain-operations-2.md b/v1.0/Virtual Accounts/blockchain-operations-2.md deleted file mode 100644 index 40493247..00000000 --- a/v1.0/Virtual Accounts/blockchain-operations-2.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Blockchain operations" -slug: "blockchain-operations-2" -excerpt: "" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/blockchain-operations-2/adatransferoffchain.md b/v1.0/Virtual Accounts/blockchain-operations-2/adatransferoffchain.md deleted file mode 100644 index d3782b53..00000000 --- a/v1.0/Virtual Accounts/blockchain-operations-2/adatransferoffchain.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send ADA from a virtual account to the blockchain" -slug: "adatransferoffchain" -excerpt: "Send ADA (Cardano) from a virtual account to the blockchain. This will create Tatum internal withdrawal request with ID. If every system works as expected, withdrawal request is marked as complete and transaction id is assigned to it.\n
4 credits per API call
\nDeploy an Algorand ERC-20-equivalent smart contract. This is a helper method, which is combination of\nRegister new Algorand ERC20 token in the ledger and Deploy blockchain ERC20.
\nAfter deploying a contract to blockchain, the contract address will become available and must be stored within Tatum. Otherwise, it will not be possible to interact with it and starts automatic blockchain synchronization.
\nSigning a transaction
\nWhen deploying an Algorand ERC-20-equivalent smart contract to the blockchain and a virtual account, 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.
\nFor 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.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/blockchain-operations-2/algotransfer.md b/v1.0/Virtual Accounts/blockchain-operations-2/algotransfer.md deleted file mode 100644 index bf902e90..00000000 --- a/v1.0/Virtual Accounts/blockchain-operations-2/algotransfer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send ALGO from a virtual account to the blockchain" -slug: "algotransfer" -excerpt: "4 credits per API call
\nSend Algos or ERC-20-equivalent Algorand tokens from a virtual account (even from a virtual account without deposit addresses adssigned) to the Algorand blockchain.
\nThe recipient has to agree in advance to receive assets because Algorand charges users for storing assets on their addresses, and an Algorand blockchain address by default does not receive assets unless explicitly agreed. Before sending any asset from a virtual account to the blockchain, make sure that the recipient has agreed to receive the assets to their address.
\nSending Algorand assets creates an internal Tatum withdrawal request with an ID. If everything works as expected, the withdrawal request is marked as complete and a transaction ID is assigned to it.
\nSigning a transaction
\nWhen sending Algos or ERC-20-equivalent Algorand tokens, 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.
\nFor 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.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:17 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/blockchain-operations-2/bchtransfer.md b/v1.0/Virtual Accounts/blockchain-operations-2/bchtransfer.md deleted file mode 100644 index d54cd013..00000000 --- a/v1.0/Virtual Accounts/blockchain-operations-2/bchtransfer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send BCH from a virtual account to the blockchain" -slug: "bchtransfer" -excerpt: "Send BCH (Bitcoin Cash) from a virtual account to the blockchain. This will create Tatum internal withdrawal request with ID. If every system works as expected, withdrawal request is marked as complete and transaction id is assigned to it.\n
\n
Create a BNB-based asset in a virtual account. The asset must first be created and configured on BNB Beacon Chain blockhain.
\nThis API call will create an internal virtual currency. You can create virtual accounts with off-chain support.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:16 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/blockchain-operations-2/bnbtransfer.md b/v1.0/Virtual Accounts/blockchain-operations-2/bnbtransfer.md deleted file mode 100644 index 6fcd5b89..00000000 --- a/v1.0/Virtual Accounts/blockchain-operations-2/bnbtransfer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send BNB from a virtual account to the blockchain" -slug: "bnbtransfer" -excerpt: "\n
Send BNB (BNB Beacon Chain) or BNB assets from a virtual account to the blockchain. This will create Tatum internal withdrawal request with ID. When every system works as expected,\nwithdrawal request is marked as complete and transaction id is assigned to it.\n
4 credits per API call
\nDeploy a BNB Smart Chain BEP-20 smart contract. This is a helper method, which is combination of\nRegister new BEP20 token in the ledger and Deploy blockchain ERC20.
\nAfter deploying a contract to blockchain, the contract address will become available and must be stored within Tatum. Otherwise, it will not be possible to interact with it and starts automatic blockchain synchronization.
\nSigning a transaction
\nWhen deploying a BNB Smart Chain BEP-20 smart contract to the blockchain and a virtual account, 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.
\nFor 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.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:15 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/blockchain-operations-2/bscorbeptransfer.md b/v1.0/Virtual Accounts/blockchain-operations-2/bscorbeptransfer.md deleted file mode 100644 index 074a2163..00000000 --- a/v1.0/Virtual Accounts/blockchain-operations-2/bscorbeptransfer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send BSC from a virtual account to the blockchain" -slug: "bscorbeptransfer" -excerpt: "Send BSC (BNB Smart Chain) or BEP-20 tokens from a virtual account to the blockchain. This will create Tatum internal withdrawal request with ID. If every system works as expected, withdrawal request is marked as complete and transaction id is assigned to it.\n
\n
\n
Send BTC (Bitcoin) from a virtual account to the blockchain. This will create Tatum internal withdrawal request with ID. If every system works as expected, withdrawal request is marked as complete and transaction id is assigned to it.\n
4 credits per API call
\nDeploy a Celo ERC-20-equivalent smart contract. This is a helper method, which is combination of\nRegister new Celo ERC-20 token in the ledger and Deploy blockchain ERC20.
\nAfter deploying a contract to blockchain, the contract address will become available and must be stored within Tatum. Otherwise, it will not be possible to interact with it and starts automatic blockchain synchronization.
\nSigning a transaction
\nWhen deploying a Celo ERC-20-equivalent smart contract to the blockchain and a virtual account, 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.
\nFor 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.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:16 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/blockchain-operations-2/celoorerc20transfer.md b/v1.0/Virtual Accounts/blockchain-operations-2/celoorerc20transfer.md deleted file mode 100644 index 936bcd55..00000000 --- a/v1.0/Virtual Accounts/blockchain-operations-2/celoorerc20transfer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send CELO from a virtual account to the blockchain" -slug: "celoorerc20transfer" -excerpt: "Send CELO (Celo), ERC-20-equivalent Celo tokens, cUSD, or cEUR from a virtual account to the blockchain. This will create Tatum internal withdrawal request with ID. If every system works as expected, withdrawal request is marked as complete and transaction id is assigned to it.\n
\n
\n
This method is deprecated.
Use this method instead.
First step to create new BEP20 token with given supply on BSC blockchain with support of Tatum's private ledger.
\n
\n
\nThis method only creates Tatum Private ledger virtual currency with predefined parameters. It will not generate any blockchain smart contract.
\nThe whole supply of BEP20 token is stored in the customer's newly created account. Then it is possible to create new Tatum accounts with BEP20 token name as account's currency.
\nNewly created account is frozen until the specific BEP20 smart contract address is linked with the Tatum virtual currency, representing the token.
\nOrder of the steps to create BEP20 smart contract with Tatum private ledger support:\n
This method is deprecated.
Use this method instead.
First step to create new ERC-20 token with given supply on Celo blockchain with support of Tatum's private ledger.
\n
\n
\nThis method only creates Tatum Private ledger virtual currency with predefined parameters. It will not generate any blockchain smart contract.
\nThe whole supply of ERC-20 token is stored in the customer's newly created account. Then it is possible to create new Tatum accounts with ERC-20 token name as account's currency.
\nNewly created account is frozen until the specific ERC-20 smart contract address is linked with the Tatum virtual currency, representing the token.
\nOrder of the steps to create ERC-20 smart contract with Tatum private ledger support:\n
This method is deprecated.
Use this method instead.
First step to create new ERC20 token with given supply on Ethereum blockchain with support of Tatum's private ledger.
\nThis method only creates Tatum Private ledger virtual currency with predefined parameters. It will not generate any blockchain smart contract.
\nThe whole supply of ERC20 token is stored in the customer's newly created account. Then it is possible to create new Tatum accounts with ERC20 token name as account's currency.
\nNewly created account is frozen until the specific ERC20 smart contract address is linked with the Tatum virtual currency, representing the token.
\nOrder of the steps to create ERC20 smart contract with Tatum private ledger support:\n
This method is deprecated.
Use this method instead.
First step to create new HRM20 token with given supply on ONE blockchain with support of Tatum's private ledger.
\n
\n
\nThis method only creates Tatum Private ledger virtual currency with predefined parameters. It will not generate any blockchain smart contract.
\nThe whole supply of HRM20 token is stored in the customer's newly created account. Then it is possible to create new Tatum accounts with HRM20 token name as account's currency.
\nNewly created account is frozen until the specific HRM20 smart contract address is linked with the Tatum virtual currency, representing the token.
\nOrder of the steps to create HRM20 smart contract with Tatum private ledger support:\n
First step to create new TRC 10/20 token with given supply on the Tron blockchain with support of Tatum's private ledger.
\nThis method only creates Tatum Private ledger virtual currency with predefined parameters. It will not generate any blockchain smart contract.
\nThe whole supply of TRC 10/20 token is stored in the customer's newly created account. Then it is possible to create new Tatum accounts with TRC 10/20 token name as account's currency.
\nNewly created account is frozen until the specific TRC 10/20 smart contract address is linked with the Tatum virtual currency, representing the token.
\nOrder of the steps to create TRC 10/20 smart contract with Tatum private ledger support:\n
This method is deprecated.
Use this method instead.
First step to create new ERC20 token with given supply on XDC blockchain with support of Tatum's private ledger.
\nThis method only creates Tatum Private ledger virtual currency with predefined parameters. It will not generate any blockchain smart contract.
\nThe whole supply of ERC20 token is stored in the customer's newly created account. Then it is possible to create new Tatum accounts with ERC20 token name as account's currency.
\nNewly created account is frozen until the specific ERC20 smart contract address is linked with the Tatum virtual currency, representing the token.
\nOrder of the steps to create ERC20 smart contract with Tatum private ledger support:\n
Send DOGE (Dogecoin) from a virtual account to the blockchain. This will create Tatum internal withdrawal request with ID. If every system works as expected, withdrawal request is marked as complete and transaction id is assigned to it.\n
Send EGLD from a virtual account to the blockchain. This will create Tatum internal withdrawal request with ID. If every system works as expected, withdrawal request is marked as complete and transaction id is assigned to it.\n
\n
\n
4 credits per API call
\nDeploy an Ethereum ERC-20 smart contract. This is a helper method, which is combination of\nRegister new ERC20 token in the ledger and Deploy blockchain ERC20.
\nAfter deploying a contract to blockchain, the contract address will become available and must be stored within Tatum. Otherwise, it will not be possible to interact with it and starts automatic blockchain synchronization.
\nSigning a transaction
\nWhen deploying an Ethereum ERC-20 smart contract to the blockchain and a virtual account, 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.
\nFor 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.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/blockchain-operations-2/ethtransfer.md b/v1.0/Virtual Accounts/blockchain-operations-2/ethtransfer.md deleted file mode 100644 index 5cd68520..00000000 --- a/v1.0/Virtual Accounts/blockchain-operations-2/ethtransfer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send ETH from a virtual account to the blockchain" -slug: "ethtransfer" -excerpt: "Send ETH (Ethereum) from a virtual account to the blockchain. This will create Tatum internal withdrawal request with ID. If every system works as expected, withdrawal request is marked as complete and transaction id is assigned to it.\n
Send Ethereum ERC-20 tokens from a virtual account to the blockchain. This will create Tatum internal withdrawal request with ID. If every system works as expected, withdrawal request is marked as complete and transaction id is assigned to it.\n
Send FLOW (Flow) or FUSD from a virtual account to the blockchain. This will create Tatum internal withdrawal request with ID. If every system works as expected, withdrawal request is marked as complete and transaction id is assigned to it.\n
4 credits per API call
\nDeploy a KuCoin Community Chain (KCC) ERC-20-equivalent smart contract. This is a helper method, which is combination of\nRegister new Kcs ERC20 token in the ledger and Deploy blockchain ERC20.
\nAfter deploying a contract to blockchain, the contract address will become available and must be stored within Tatum. Otherwise, it will not be possible to interact with it and starts automatic blockchain synchronization.
\nSigning a transaction
\nWhen deploying a KCC ERC-20-equivalent smart contract to the blockchain and a virtual account, 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.
\nFor 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.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:16 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/blockchain-operations-2/kcstransfer.md b/v1.0/Virtual Accounts/blockchain-operations-2/kcstransfer.md deleted file mode 100644 index 66448de9..00000000 --- a/v1.0/Virtual Accounts/blockchain-operations-2/kcstransfer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send KCS from a virtual account to the blockchain" -slug: "kcstransfer" -excerpt: "Send KCS (KuCoin Community Chain (KCC)) or ERC-20-equivalent KCC tokens from a virtual account to the blockchain. This will create Tatum internal withdrawal request with ID. If every system works as expected, withdrawal request is marked as complete and transaction id is assigned to it.\n
4 credits per API call
\nDeploy a Klaytn ERC-20-equivalent smart contract. This is a helper method, which is combination of\nRegister new ERC20 token in the ledger and Deploy blockchain ERC20.
\nAfter deploying a contract to blockchain, the contract address will become available and must be stored within Tatum. Otherwise, it will not be possible to interact with it and starts automatic blockchain synchronization.
\nSigning a transaction
\nWhen deploying a Klaytn ERC-20-equivalent smart contract to the blockchain and a virtual account, 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.
\nFor 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.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/blockchain-operations-2/klaytransfer.md b/v1.0/Virtual Accounts/blockchain-operations-2/klaytransfer.md deleted file mode 100644 index 592f13cb..00000000 --- a/v1.0/Virtual Accounts/blockchain-operations-2/klaytransfer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send KLAY from a virtual account to the blockchain" -slug: "klaytransfer" -excerpt: "Send KLAY or ERC-20-equivalent tokens from a virtual account to the blockchain. This will create Tatum internal withdrawal request with ID. If every system works as expected, withdrawal request is marked as complete and transaction id is assigned to it.\n
\n
\n
Send LTC (Litecoin) from a virtual account to the blockchain. This will create Tatum internal withdrawal request with ID. If every system works as expected, withdrawal request is marked as complete and transaction id is assigned to it.\n
4 credits per API call
\nDeploy a Harmony HRM-20 smart contract. This is a helper method, which is combination of\nRegister new HRM20 token in the ledger and Deploy blockchain ERC20.
\nAfter deploying a contract to blockchain, the contract address will become available and must be stored within Tatum. Otherwise, it will not be possible to interact with it and starts automatic blockchain synchronization.
\nSigning a transaction
\nWhen deploying a Harmony HRM-20 smart contract to the blockchain and a virtual account, 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.
\nFor 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.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/blockchain-operations-2/onetransfer.md b/v1.0/Virtual Accounts/blockchain-operations-2/onetransfer.md deleted file mode 100644 index 11922835..00000000 --- a/v1.0/Virtual Accounts/blockchain-operations-2/onetransfer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send ONE from a virtual account to the blockchain" -slug: "onetransfer" -excerpt: "Send ONE (Harmony) or HRM-20 tokens from a virtual account to the blockchain. This will create Tatum internal withdrawal request with ID. If every system works as expected, withdrawal request is marked as complete and transaction id is assigned to it.\n
\n
\n
Send MATIC (Polygon) or ERC-20-equivalent Polygon tokens from a virtual account to the blockchain. This will create Tatum internal withdrawal request with ID. If every system works as expected, withdrawal request is marked as complete and transaction id is assigned to it.\n
This is the first step to create a new ERC-20 or ERC-20 equivalent token with some supply in a virtual account.
\n
\n
\nThis method only creates Tatum Private ledger virtual currency with predefined parameters. It will not generate any blockchain smart contract.
\nThe whole supply of token is stored in the customer's newly created account. Then it is possible to create new Tatum accounts with token name as account's currency.
\nNewly created account is frozen until the specific smart contract address is linked with the Tatum virtual currency, representing the token.
\nOrder of the steps to create smart contract with Tatum private ledger support:\n
10 credits per API call
\nSend SOL (Solana), USDC_SOL, or custom SPL tokens from a virtual account to the blockchain. This will create Tatum internal withdrawal request with ID. When every system works as expected,\nwithdrawal request is marked as complete and transaction id is assigned to it.
\nIt is possible to perform ledger to blockchain transaction for ledger accounts without blockchain address assigned to them.
\nThis 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.\nNo one should ever send it's own private keys to the internet because there is a strong possibility of stealing keys and losing funds. In this method, it is possible to enter privateKey\nor signatureId. PrivateKey should be used only for quick development on testnet versions of blockchain when there is no risk of losing funds. In production,\nTatum KMS should be used for the highest security standards, and signatureId should be present in the request.\nAlternatively, using the Tatum client library for supported languages.\n
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:16 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/blockchain-operations-2/storeceloerc20address.md b/v1.0/Virtual Accounts/blockchain-operations-2/storeceloerc20address.md deleted file mode 100644 index c83a90c7..00000000 --- a/v1.0/Virtual Accounts/blockchain-operations-2/storeceloerc20address.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Set the contract address of a Celo ERC-20-equivalent token" -slug: "storeceloerc20address" -excerpt: "This method is deprecated.
Use this method instead.
2 credits per API call
\nSet the contract address of an ERC-20, ERC-20-equivalent (for example, BEP-20, HRM-20, and so on), or TRC-10 token to be able to communicate with the smart contract.
\nAfter creating and deploying the token to the blockchain, the smart contract address is generated and must be set within Tatum. If the address is not set, the Tatum platform will not be able to detect incoming deposits of the tokens and transfer the tokens from virtual accounts to blockchain addresses.
\nNOTE:
\nassetId), for example, 55351976.tokenId), for example, 1234567.This method is deprecated.
Use this method instead.
10 credits per API call
\nDeploy a TRON TRC-10 or TRC-20 smart contract. This is a helper method, which is combination of\nRegister new TRC-10/20 token in the ledger and Deploy blockchain TRC20 or Deploy blockchain TRC10.
\nAfter deploying a contract to blockchain, the contract address will become available and must be stored within Tatum. Otherwise, it will not be possible to interact with it and starts automatic blockchain synchronization.
\nSigning a transaction
\nWhen deploying a TRON TRC-10 or TRC-20 smart contract to the blockchain and a virtual account, 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.
\nFor 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.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:16 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/blockchain-operations-2/trontransferoffchain.md b/v1.0/Virtual Accounts/blockchain-operations-2/trontransferoffchain.md deleted file mode 100644 index 3212b333..00000000 --- a/v1.0/Virtual Accounts/blockchain-operations-2/trontransferoffchain.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send TRON from a virtual account to the blockchain" -slug: "trontransferoffchain" -excerpt: "Send TRON or TRX assets from a virtual account to the blockchain. This will create Tatum internal withdrawal request with ID. If every system works as expected, withdrawal request is marked as complete and transaction id is assigned to it.\n
4 credits per API call
\nDeploy a XinFin ERC-20-equivalent smart contract. This is a helper method, which is combination of\nRegister new ERC20 token in the ledger and Deploy blockchain ERC20.
\nAfter deploying a contract to blockchain, the contract address will become available and must be stored within Tatum. Otherwise, it will not be possible to interact with it and starts automatic blockchain synchronization.
\nSigning a transaction
\nWhen deploying a XinFin ERC-20-equivalent smart contract to the blockchain and a virtual account, 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.
\nFor 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.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/blockchain-operations-2/xdctransfer.md b/v1.0/Virtual Accounts/blockchain-operations-2/xdctransfer.md deleted file mode 100644 index c8e8fdad..00000000 --- a/v1.0/Virtual Accounts/blockchain-operations-2/xdctransfer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send XDC from a virtual account to the blockchain" -slug: "xdctransfer" -excerpt: "Send XDC (XinFin) or ERC-20-equivalent XinFin tokens from a virtual account to the blockchain. This will create Tatum internal withdrawal request with ID. If every system works as expected, withdrawal request is marked as complete and transaction id is assigned to it.\n
\n
\n
Create an XLM-based asset in a virtual account. The asset must be created and configured on the Stellar blockchain before creating a trust line.
\nThis API call will create an internal virtual currency. You can create virtual accounts with off-chain support.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:16 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/blockchain-operations-2/xlmtransfer.md b/v1.0/Virtual Accounts/blockchain-operations-2/xlmtransfer.md deleted file mode 100644 index 8c386ad1..00000000 --- a/v1.0/Virtual Accounts/blockchain-operations-2/xlmtransfer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send XLM from a virtual account to the blockchain" -slug: "xlmtransfer" -excerpt: "10 credits per API call
\nSend XLM (Stellar) or XLM-based assets from a virtual account to the blockchain. This will create Tatum internal withdrawal request with ID. When every system works as expected,\nwithdrawal request is marked as complete and transaction id is assigned to it.
\nIt is possible to perform ledger to blockchain transaction for ledger accounts without blockchain address assigned to them.
\nThis 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.\nNo one should ever send it's own private keys to the internet because there is a strong possibility of stealing keys and losing funds. In this method, it is possible to enter privateKey\nor signatureId. PrivateKey should be used only for quick development on testnet versions of blockchain when there is no risk of losing funds. In production,\nTatum KMS should be used for the highest security standards, and signatureId should be present in the request.\nAlternatively, using the Tatum client library for supported languages.\n
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/blockchain-operations-2/xrpassetoffchain.md b/v1.0/Virtual Accounts/blockchain-operations-2/xrpassetoffchain.md deleted file mode 100644 index f678e161..00000000 --- a/v1.0/Virtual Accounts/blockchain-operations-2/xrpassetoffchain.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Create XRP based Asset" -slug: "xrpassetoffchain" -excerpt: "\n
Create an XRP-based asset in a virtual account. The asset must be created and configured on the XRPL blockchain before creating a trust line.
\nThis API call will create an internal virtual currency. You can create virtual accounts with off-chain support.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:16 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/blockchain-operations-2/xrptransfer.md b/v1.0/Virtual Accounts/blockchain-operations-2/xrptransfer.md deleted file mode 100644 index 5e053406..00000000 --- a/v1.0/Virtual Accounts/blockchain-operations-2/xrptransfer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send XRP from a virtual account to the blockchain" -slug: "xrptransfer" -excerpt: "\n
Send XRP from a virtual account to the blockchain. This will create Tatum internal withdrawal request with ID. When every system works as expected, withdrawal request is marked as complete and transaction id is assigned to it.\n
Activated customer is able to do any operation.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:13 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/customer/deactivatecustomer.md b/v1.0/Virtual Accounts/customer/deactivatecustomer.md deleted file mode 100644 index d11d1145..00000000 --- a/v1.0/Virtual Accounts/customer/deactivatecustomer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Deactivate customer" -slug: "deactivatecustomer" -excerpt: "Deactivate customer is not able to do any operation. Customer can be deactivated only when all their accounts are already deactivated.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/customer/disablecustomer.md b/v1.0/Virtual Accounts/customer/disablecustomer.md deleted file mode 100644 index d87fd83f..00000000 --- a/v1.0/Virtual Accounts/customer/disablecustomer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Disable customer" -slug: "disablecustomer" -excerpt: "Disabled customer cannot perform end-user operations, such as create new accounts or send transactions. Available balance on all accounts is set to 0. Account balance will stay untouched.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/customer/enablecustomer.md b/v1.0/Virtual Accounts/customer/enablecustomer.md deleted file mode 100644 index 204a6ecc..00000000 --- a/v1.0/Virtual Accounts/customer/enablecustomer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Enable customer" -slug: "enablecustomer" -excerpt: "Enabled customer can perform all operations. By default all customers are enabled. All previously blocked account balances will be unblocked.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:13 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/customer/findallcustomers.md b/v1.0/Virtual Accounts/customer/findallcustomers.md deleted file mode 100644 index f81b4ec1..00000000 --- a/v1.0/Virtual Accounts/customer/findallcustomers.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "List all customers" -slug: "findallcustomers" -excerpt: "List of all customers. Also inactive an disabled customers are present.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:12 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/customer/getcustomerbyexternalorinternalid.md b/v1.0/Virtual Accounts/customer/getcustomerbyexternalorinternalid.md deleted file mode 100644 index 81462eda..00000000 --- a/v1.0/Virtual Accounts/customer/getcustomerbyexternalorinternalid.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get customer details" -slug: "getcustomerbyexternalorinternalid" -excerpt: "Using anonymized external ID or internal customer ID you can access customer detail information. Internal ID is needed to call other customer related methods.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:12 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/customer/updatecustomer.md b/v1.0/Virtual Accounts/customer/updatecustomer.md deleted file mode 100644 index a1c8efff..00000000 --- a/v1.0/Virtual Accounts/customer/updatecustomer.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Update customer" -slug: "updatecustomer" -excerpt: "This method is helpful in case your primary system will change ID's or customer will change the country he/she is supposed to be in compliance with.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/deposit.md b/v1.0/Virtual Accounts/deposit.md deleted file mode 100644 index a644887f..00000000 --- a/v1.0/Virtual Accounts/deposit.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Deposit" -slug: "deposit" -excerpt: "" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/deposit/getdeposits.md b/v1.0/Virtual Accounts/deposit/getdeposits.md deleted file mode 100644 index 40147a56..00000000 --- a/v1.0/Virtual Accounts/deposit/getdeposits.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "List all deposits for product" -slug: "getdeposits" -excerpt: "Lists all deposits for API key.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:12 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/deposit/getdepositscount.md b/v1.0/Virtual Accounts/deposit/getdepositscount.md deleted file mode 100644 index 245c3f54..00000000 --- a/v1.0/Virtual Accounts/deposit/getdepositscount.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Count of found entities for get deposits request" -slug: "getdepositscount" -excerpt: "Counts total entities found by get deposits request.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:12 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/order-book.md b/v1.0/Virtual Accounts/order-book.md deleted file mode 100644 index 7fb9b4ba..00000000 --- a/v1.0/Virtual Accounts/order-book.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Order Book" -slug: "order-book" -excerpt: "" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/order-book/chartrequest.md b/v1.0/Virtual Accounts/order-book/chartrequest.md deleted file mode 100644 index 6ab00eaa..00000000 --- a/v1.0/Virtual Accounts/order-book/chartrequest.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Obtain chart data from historical closed trades" -slug: "chartrequest" -excerpt: "Obtain data from the closed trades for entering in the chart. Time interval is set between from and to and there is defined time frame. There can be obtained at most 200 time points in the time interval.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:13 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/order-book/deleteaccounttrades.md b/v1.0/Virtual Accounts/order-book/deleteaccounttrades.md deleted file mode 100644 index 3e5638e5..00000000 --- a/v1.0/Virtual Accounts/order-book/deleteaccounttrades.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Cancel all existing trades for account" -slug: "deleteaccounttrades" -excerpt: "Cancel all trades for account.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:14 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/order-book/deletetrade.md b/v1.0/Virtual Accounts/order-book/deletetrade.md deleted file mode 100644 index cb170d46..00000000 --- a/v1.0/Virtual Accounts/order-book/deletetrade.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Cancel existing trade" -slug: "deletetrade" -excerpt: "Cancel existing trade.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/order-book/getbuytrades.md b/v1.0/Virtual Accounts/order-book/getbuytrades.md deleted file mode 100644 index f65c7420..00000000 --- a/v1.0/Virtual Accounts/order-book/getbuytrades.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "List all active buy trades" -slug: "getbuytrades" -excerpt: "List all active buy trades.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/order-book/getbuytradesbody.md b/v1.0/Virtual Accounts/order-book/getbuytradesbody.md deleted file mode 100644 index f5878f57..00000000 --- a/v1.0/Virtual Accounts/order-book/getbuytradesbody.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "List all active buy trades" -slug: "getbuytradesbody" -excerpt: "List all active buy trades.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:14 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/order-book/gethistoricaltrades.md b/v1.0/Virtual Accounts/order-book/gethistoricaltrades.md deleted file mode 100644 index 4cce427f..00000000 --- a/v1.0/Virtual Accounts/order-book/gethistoricaltrades.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "List all historical trades" -slug: "gethistoricaltrades" -excerpt: "List all historical trades. It is possible to list all trades, trades for specific trading pair and/or account.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:13 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/order-book/gethistoricaltradesbody.md b/v1.0/Virtual Accounts/order-book/gethistoricaltradesbody.md deleted file mode 100644 index d3941941..00000000 --- a/v1.0/Virtual Accounts/order-book/gethistoricaltradesbody.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "List all historical trades" -slug: "gethistoricaltradesbody" -excerpt: "List all historical trades. It is possible to list all trades, trades for specific trading pair and/or account.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/order-book/getmatchedtrades.md b/v1.0/Virtual Accounts/order-book/getmatchedtrades.md deleted file mode 100644 index 3d58416c..00000000 --- a/v1.0/Virtual Accounts/order-book/getmatchedtrades.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "List all matched orders from FUTURE_SELL/FUTURE_BUY trades" -slug: "getmatchedtrades" -excerpt: "List all matched orders from the FUTURE_BUY OR FUTURE_SELL orders.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/order-book/getselltrades.md b/v1.0/Virtual Accounts/order-book/getselltrades.md deleted file mode 100644 index 5694e033..00000000 --- a/v1.0/Virtual Accounts/order-book/getselltrades.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "List all active sell trades" -slug: "getselltrades" -excerpt: "List all active sell trades.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:14 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/order-book/getselltradesbody.md b/v1.0/Virtual Accounts/order-book/getselltradesbody.md deleted file mode 100644 index 69b73b95..00000000 --- a/v1.0/Virtual Accounts/order-book/getselltradesbody.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "List all active sell trades" -slug: "getselltradesbody" -excerpt: "List all active sell trades.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:14 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/order-book/gettradebyid.md b/v1.0/Virtual Accounts/order-book/gettradebyid.md deleted file mode 100644 index 7f17e0a0..00000000 --- a/v1.0/Virtual Accounts/order-book/gettradebyid.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get existing trade" -slug: "gettradebyid" -excerpt: "Get existing opened trade.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:14 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/order-book/storetrade.md b/v1.0/Virtual Accounts/order-book/storetrade.md deleted file mode 100644 index 5d872177..00000000 --- a/v1.0/Virtual Accounts/order-book/storetrade.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Store buy / sell trade" -slug: "storetrade" -excerpt: "Store new buy / sell trade. If there is trade already available to fill, fill as much trades as possible.
\nIt is possible to charge fees for the trades. Fees are an extra amount on top of the trade amount and are paid in the currency that you going to block\ne.g.:\n- BUY BTC/USDT - fees will be paid in USDT\n- SELL BTC/ETH - fees will be paid in BTC\n
\nIf you fill type of the trade with FUTURE_BUY or FUTURE_SELL the trade will behave as a trade future. The trade is concluded now but will be fulfilled in future.\nThe date of fulfillment is by the “Seal Date” field. You can also block a percentage of the amount until the future trade has expired.\n
\nFutures can also penalize contracting parties if they don’t have the agreed balance available in their accounts.\nThe penalty is calculated in the following way: Penalty amount = (Percentage of incomplete deal amount because of shortage from user) × (Maximum Penalty percentage of futures deal based on blocked amount and time interval) × (total blocked value).\n
\nExample of the BTC/USDT trade future:
\nThe maker creates a sell with the following properties: 1 BTC at a price of 60000 USDT, with a blocking percentage of 22%, a penalty percentage of 45%, a system commision of 1% and with an expiration time of within 12 hours.
\n\n{\n \"type\": \"FUTURE_SELL\",\n \"price\": \"60000\",\n \"amount\": \"1\",\n \"pair\": \"BTC/USDT\",\n \"currency1AccountId\": \"60a236db1b57f60d62612bf3\",\n \"currency2AccountId\": \"609d0696bf835c241ac2920f\",\n \"fee\": 1,\n \"feeAccountId\": \"609d0696bf835c251ac2920a\",\n \"attr\": {\n \"sealDate\": 1621990960631,\n \"percentBlock\": 22,\n \"percentPenalty\": 45\n }\n}\n\n\nThe taker accepts the offer with a buy and blocks 13200 USDT (60000 USDT × 0.22) in their account.\n\n{\n \"type\": \"FUTURE_BUY\",\n \"price\": \"60000\",\n \"amount\": \"1\",\n \"pair\": \"BTC/USDT\",\n \"currency1AccountId\": \"60a236db1b57f60d62612bf2\",\n \"currency2AccountId\": \"609d0696bf835c241ac2920a\",\n \"attr\": {\n \"sealDate\": 1621990960631,\n \"percentBlock\": 22,\n \"percentPenalty\": 45\n }\n}\n\nAt the time of the trade, the maker and taker have the following conditions.\nThe maker has 0.65 BTC (35% deficit) in their account and the taker has 49200 USDT (18% deficit) in their account.\n
\n\n\nThe maker penalty is equal to 0.35 × 0.22 × (0.45 × 1 BTC) = 0.03465 BTC.\nThe taker penalty is equal to 0.18 × 0.22 × (0.45 × 60000 USDT) = 1069.2 USDT.\n
\n\nThe system commission for the maker is 1 BTC × 1% = 0.01 BTC.\nThe system commission for the taker is 60000 USDT × 1% = 600 USDT.\n
\n\nThe maker’s assets after deducting penalties and commissions equals 0.65 - 0.03465 - 0.01 = 0.60535 BTC. The taker’s assets after deducting penalties and commissions equals 49200 - 1069.2 - 600 = 47530.8 USDT.\n
\n\nThe amount received by the maker after the trade is (0.60535 × 60000) + 1069.2 = 37390.2 USDT and the taker receives 0.60535 + 0.03465 = 0.64 BTC.\n
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:13 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/transaction.md b/v1.0/Virtual Accounts/transaction.md deleted file mode 100644 index 4a4082d1..00000000 --- a/v1.0/Virtual Accounts/transaction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Transaction" -slug: "transaction" -excerpt: "" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/transaction/gettransactions-1.md b/v1.0/Virtual Accounts/transaction/gettransactions-1.md deleted file mode 100644 index c51f304a..00000000 --- a/v1.0/Virtual Accounts/transaction/gettransactions-1.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Find transactions within the ledger." -slug: "gettransactions-1" -excerpt: "Find transactions across whole ledger.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:12 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/transaction/gettransactionsbyaccountid.md b/v1.0/Virtual Accounts/transaction/gettransactionsbyaccountid.md deleted file mode 100644 index 56f03e5c..00000000 --- a/v1.0/Virtual Accounts/transaction/gettransactionsbyaccountid.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Find transactions for account." -slug: "gettransactionsbyaccountid" -excerpt: "Finds transactions for the account identified by the given account ID.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/transaction/gettransactionsbycustomerid.md b/v1.0/Virtual Accounts/transaction/gettransactionsbycustomerid.md deleted file mode 100644 index 99d9910e..00000000 --- a/v1.0/Virtual Accounts/transaction/gettransactionsbycustomerid.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Find transactions for a customer across all of the customer's accounts." -slug: "gettransactionsbycustomerid" -excerpt: "Finds transactions for all accounts of the customer identified by the given internal customer ID.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:12 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/transaction/gettransactionsbyreference.md b/v1.0/Virtual Accounts/transaction/gettransactionsbyreference.md deleted file mode 100644 index a75d799f..00000000 --- a/v1.0/Virtual Accounts/transaction/gettransactionsbyreference.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Find transactions with a given reference across all accounts." -slug: "gettransactionsbyreference" -excerpt: "Finds transactions for all accounts with the given reference.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:12 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/transaction/sendtransaction.md b/v1.0/Virtual Accounts/transaction/sendtransaction.md deleted file mode 100644 index 444e8638..00000000 --- a/v1.0/Virtual Accounts/transaction/sendtransaction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Send payment" -slug: "sendtransaction" -excerpt: "Sends a payment within Tatum Private Ledger. All assets are settled instantly.
\nWhen a transaction is settled, 2 transaction records are created, 1 for each of the participants. These 2 records are connected via a transaction reference, which is the same for both of them.
\nThis method is only used for transferring assets between accounts within Tatum and will not send any funds to blockchain addresses.
\nIf there is an insufficient balance in the sender account, no transaction is recorded.
\nIt is possible to perform an anonymous transaction where the sender account is not visible for the recipient.
\nThe FIAT currency value of every transaction is calculated automatically. The FIAT value is based on the accountingCurrency of the account connected to the transaction and is available in the marketValue parameter of the transaction.
Sends the N payments within Tatum Private Ledger. All assets are settled instantly.
\nWhen a transaction is settled, 2 transaction records are created, 1 for each of the participants. These 2 records are connected via a transaction reference, which is the same for both of them.
\nThis method is only used for transferring assets between accounts within Tatum and will not send any funds to blockchain addresses.
\nIf there is an insufficient balance in the sender account, no transaction is recorded.
\nIt is possible to perform an anonymous transaction where the sender account is not visible for the recipient.
\nThe FIAT currency value of every transaction is calculated automatically. The FIAT value is based on the accountingCurrency of the account connected to the transaction and is available in the marketValue parameter of the transaction.
2 credits per API call
\nCreate new virtual currency with given supply stored in account. This will create Tatum internal virtual currency. Every virtual currency must be prefixed with VC_.
\nEvery virtual currency must be pegged to existing FIAT or supported cryptocurrency. 1 unit of virtual currency has then the same amount as 1 unit of the base currency it is pegged to. It is possible to set a custom base rate for the virtual currency. (baseRate = 2 => 1 VC unit = 2 basePair units)
\nTatum virtual currency acts as any other asset within Tatum. To create a fungible token, see the API for deploying a fungible token smart contract.
\nThis operation returns the newly created Tatum Ledger account with an initial balance set to the virtual currency's total supply. Total supply can be changed in the future.
\nDigital assets:
\n0x2791bca1f2de4661ed88a30c99a7a9449aa84174 on Polygon mainnet.0x3c499c542cef5e3811e1192ce70d8cc03d5c3359 on Polygon mainnet.1 credit per API call
\nGet detail of virtual currency.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:13 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/virtual-currency/mintcurrency.md b/v1.0/Virtual Accounts/virtual-currency/mintcurrency.md deleted file mode 100644 index 3ebddb19..00000000 --- a/v1.0/Virtual Accounts/virtual-currency/mintcurrency.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Create new supply of virtual currency" -slug: "mintcurrency" -excerpt: "2 credits per API call
\nCreate new supply of virtual currency linked on the given accountId. Method increases the total supply of the currency.
\nThis method creates Ledger transaction with operationType MINT with undefined counterAccountId.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:13 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/virtual-currency/revokecurrency.md b/v1.0/Virtual Accounts/virtual-currency/revokecurrency.md deleted file mode 100644 index 955d0a1f..00000000 --- a/v1.0/Virtual Accounts/virtual-currency/revokecurrency.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Destroy supply of virtual currency" -slug: "revokecurrency" -excerpt: "Destroy supply of virtual currency linked on the given accountId. Method decreases the total supply of the currency.
\nThis method creates Ledger transaction with operationType REVOKE with undefined counterAccountId.
Change base pair and/or base rate of existing virtual currency.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:13 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/withdrawal.md b/v1.0/Virtual Accounts/withdrawal.md deleted file mode 100644 index 4fabad75..00000000 --- a/v1.0/Virtual Accounts/withdrawal.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Withdrawal" -slug: "withdrawal" -excerpt: "" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/withdrawal/broadcastblockchaintransaction.md b/v1.0/Virtual Accounts/withdrawal/broadcastblockchaintransaction.md deleted file mode 100644 index 3ccc49a7..00000000 --- a/v1.0/Virtual Accounts/withdrawal/broadcastblockchaintransaction.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Broadcast signed transaction and complete withdrawal" -slug: "broadcastblockchaintransaction" -excerpt: "Broadcast signed raw transaction end complete withdrawal associated with it.\nWhen broadcast succeeded but it is impossible to complete withdrawal, transaction id of transaction is returned and withdrawal must be completed manually.\n
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:15 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/withdrawal/cancelinprogresswithdrawal.md b/v1.0/Virtual Accounts/withdrawal/cancelinprogresswithdrawal.md deleted file mode 100644 index ea8f53c7..00000000 --- a/v1.0/Virtual Accounts/withdrawal/cancelinprogresswithdrawal.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Cancel withdrawal" -slug: "cancelinprogresswithdrawal" -excerpt: "This method is helpful if you need to cancel the withdrawal if the blockchain transaction fails or is not yet processed.\nThis does not cancel already broadcast blockchain transaction, only Tatum internal withdrawal, and the ledger transaction, that was linked to this withdrawal.
\nBy default, the transaction fee is included in the reverted transaction. There are situations, like sending ERC20 on ETH, TRC token on TRON, XLM or XRP based assets, when the fee should not be reverted, because e.g. the fee is in calculated\nin Ethereum and transaction was in ERC20 currency. In this situation, only the transaction amount should be reverted, not the fee.\n
Invoke complete withdrawal as soon as blockchain transaction ID is available. All other withdrawals for the same currency will be pending unless the last one is processed and marked as completed.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:14 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/withdrawal/getwithdrawals.md b/v1.0/Virtual Accounts/withdrawal/getwithdrawals.md deleted file mode 100644 index 5e55e9fe..00000000 --- a/v1.0/Virtual Accounts/withdrawal/getwithdrawals.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Get withdrawals" -slug: "getwithdrawals" -excerpt: "Get withdrawals.
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/Virtual Accounts/withdrawal/storewithdrawal.md b/v1.0/Virtual Accounts/withdrawal/storewithdrawal.md deleted file mode 100644 index bce0dbc0..00000000 --- a/v1.0/Virtual Accounts/withdrawal/storewithdrawal.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Store withdrawal" -slug: "storewithdrawal" -excerpt: "Create a withdrawal from Tatum Ledger account to the blockchain.
\n\n When withdrawal from Tatum is executed, all deposits, which are not processed yet are used as an input and\n change is moved to pool address 0 of wallet for defined account's xpub. If there are no unspent deposits, only last pool address 0 UTXO is used.\n If balance of wallet is not sufficient, it is impossible to perform withdrawal from this account -> funds were transferred to another\n linked wallet within system or outside of Tatum visibility.
\n For the first time of withdrawal from wallet, there must be some deposit made and funds are obtained from that. Since\n there is no withdrawal, there was no transfer to pool address 0 and thus it is not present in vIn. Pool transfer is identified by missing data.address property in response.\n When last not cancelled withdrawal is not completed and thus there is no tx id of output transaction given,\n we cannot perform next withdrawal.\n
\n Withdrawal from Tatum can be processed only from 1 account. In Ethereum Blockchain, each address is recognized as an account and only funds from that account can be sent in 1 transaction.\n Example: Account A has 0.5 ETH, Account B has 0.3 ETH. Account A is linked to Tatum Account 1, Account B is linked to Tatum Account 2. Tatum Account 1 has balance 0.7 Ethereum and\n Tatum Account 2 has 0.1 ETH. Withdrawal from Tatum Account 1 can be at most 0.5 ETH, even though balance in Tatum Private Ledger is 0.7 ETH.\n Because of this Ethereum Blockchain limitation, withdrawal request should always contain sourceAddress, from which withdrawal will be made. To get available balances for Ethereum wallet accounts, use hint endpoint.\n
\n\n XRP withdrawal can contain DestinationTag except of address, which is placed in attr parameter of withdrawal request.\nSourceTag of the blockchain transaction should be withdrawal ID for autocomplete purposes of withdrawals.\n
\n\n XLM withdrawal can contain memo except of address, which is placed in attr parameter of withdrawal request. XLM blockchain does not have possibility to enter source account information.\n It is possible to create memo in format 'destination|source', which is supported way of memo in Tatum and also there is information about the sender account in the blockchain.\n
\n\nWhen withdrawal is created, all other withdrawals with the same currency are pending, unless the current one is marked as complete or cancelled.
\nTatum ledger transaction is created for every withdrawal request with operation type WITHDRAWAL. The value of the transaction is the withdrawal amount + blockchain fee, which should be paid.\nIn the situation, when there is withdrawal for ERC20, XLM, or XRP based custom assets, the fee is not included in the transaction because it is paid in different assets than the withdrawal itself.\n
" -category: 65c0c89f01bfc0001709afa1 -hidden: false -createdAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 11:38:10 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/getting started/authentication.md b/v1.0/getting started/authentication.md deleted file mode 100644 index a7581e71..00000000 --- a/v1.0/getting started/authentication.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: "Authentication" -slug: "authentication" -excerpt: "" -category: 65c0d4b7d716fe004091a1c9 -hidden: false -createdAt: "Mon Feb 05 2024 12:31:11 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Mon Feb 05 2024 12:31:20 GMT+0000 (Coordinated Universal Time)" ---- -When using the Tatum API, you authenticate yourself with an API key. - -X-API-Key - -The API key represents your pricing plan and defines how many API calls you can make per second and what the total number of API calls per month is available for you. - -One API key must be used by only one person. - -Choose one of the following authentication methods: - -Provide the API key in each API call. - -To obtain the API key, create a Tatum account. Once you are logged in, you are automatically assigned the Free plan. - -With the Free plan: - -You get two API keys, one tied to the testnet of a blockchain and the other to the mainnet. -You can make up to five API calls per second. -When making an API call, provide the appropriate API key (testnet or mainnet) as either an HTTP header. - -If you ever need your API keys, you can find them in your Tatum account. -Get an auto-generated API key attached to API calls. - -Make an API call without any API key provided. The API key will be generated and tied to your IP address. This API key is stored within the Tatum platform and is automatically attached to all your API calls. - -With the auto-generated API key: - -You can make up to five API calls per second. -These limits are applied to both the testnet and mainnet. - -By default, API calls with the auto-generated API key are executed against the mainnet. To make an API call to the testnet, add the type query parameter set to testnet to the endpoint URL, for example: - -