Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandAlgod, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_ALGOD });
-
-// Define the input parameters in a single object
-const params = {
- broadcastTransaction: 'RAW_TRANSACTION', // Specify the byte encoded signed transaction to broadcast to network.
-};
-
-// Broadcast raw transaction to Algorand network
-const transactionId = await tatum.rpc.broadcastTransaction(params);
-
-// Log the transaction ID
-console.log('Algorand Transaction ID:', transactionId);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `broadcastTransaction` method allows you to broadcast a raw transaction or transaction group to the Algorand network.
-
-### Example Use Cases
-
-1. **Transaction Broadcasting**: Developers can use this method to directly broadcast a byte encoded signed transaction to the Algorand network for further processing.
-
-### Request Parameters
-
-The `broadcastTransaction` method requires the following parameters:
-
-- `broadcastTransaction` (string, required): The byte encoded signed transaction to broadcast to the Algorand network.
-
-### Return Object
-
-The method returns an object representing the transaction ID of the submitted transaction on the Algorand network.
-
-Please note that the structure of the returned object may change in different Algorand RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccount.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccount.md
deleted file mode 100644
index 9773a7e5..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccount.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: "getAccount"
-slug: "rpc-algorand-getaccount"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:05 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-\\n
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandIndexer, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_INDEXER });
-
-// Define the input parameters as an object
-const accountAddress = { address: 'ALGORAND_ACCOUNT_ADDRESS' }; // Replace with the Algorand account address you want to retrieve information for.
-
-// Retrieve account information using the Algorand Indexer
-const accountInfo = await tatum.rpc.getAccount(accountAddress);
-
-// Log the account information
-console.log('Algorand Account Information:', accountInfo);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getAccount` method allows you to retrieve detailed information about a specific Algorand account based on its account address.
-
-### Example Use Cases
-
-1. **Account Balance**: Developers can use this method to check the balance of a specific Algorand account by providing its address.
-
-2. **Account Details**: Retrieve various details of an Algorand account, including its transactions, assets, and more, for further analysis.
-
-### Request Parameters
-
-The `getAccount` method requires the following parameter:
-
-- `account-address` (string, required): The Algorand account address for which you want to retrieve account information.
-
-### Return Object
-
-The method returns an object representing the detailed information of the specified Algorand account, including various parameters.
-
-Please note that the structure of the returned object may change in different Algorand RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccountapplicationinfo.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccountapplicationinfo.md
deleted file mode 100644
index cbe8da71..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccountapplicationinfo.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: "getAccountApplicationInfo"
-slug: "rpc-algorand-getaccountapplicationinfo"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:05 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandAlgod, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_ALGOD });
-
-// Define the input parameters in a single object
-const params = {
- address: 'ALGORAND_PUBLIC_KEY', // Specify the Algorand account public key.
- applicationId: 12345, // Specify the application identifier.
- format: 'json' // Optional: Configures whether the response object is JSON or MessagePack encoded (enum: json, msgpack).
-};
-
-// Retrieve account application information for the Algorand account
-const accountApplicationInfo = await tatum.rpc.getAccountApplicationInfo(params);
-
-// Log the account application information
-console.log('Algorand Account Application Information:', accountApplicationInfo);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getAccountApplicationInfo` method allows you to retrieve the account's application local state and global state for a specific Algorand account and application ID.
-
-### Example Use Cases
-
-1. **Retrieve Application State**: Developers can use this method to retrieve the application state (local and global) for a specific Algorand account.
-
-### Request Parameters
-
-The `getAccountApplicationInfo` method requires the following parameters:
-
-- `address` (string, required): An Algorand account public key.
-- `applicationId` (number, required): An application identifier.
-- `format` (enum: json, msgpack, optional): Configures whether the response object is JSON or MessagePack encoded.
-
-### Return Object
-
-The method returns an object representing the account's application local state and global state (if exists) for the specified Algorand account and application ID.
-
-Please note that the structure of the returned object may change in different Algorand RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccountapplications.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccountapplications.md
deleted file mode 100644
index c27a7e6b..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccountapplications.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: "getAccountApplications"
-slug: "rpc-algorand-getaccountapplications"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:04 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandIndexer, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_INDEXER });
-
-// Define the input parameters in a single object
-const params = {
- accountId: 'ALGORAND_ACCOUNT_ID', // Specify the Algorand account ID for which you want to retrieve created applications.
- applicationId: 123, // Optional: Specify the application ID (number) for filtering.
- includeAll: true, // Optional: Include all items, including closed accounts, deleted applications, destroyed assets, opted-out asset holdings, and closed-out application local states (boolean).
- limit: 100, // Optional: Maximum number of results to return (number).
- next: 'NEXT_PAGE_TOKEN' // Optional: The next page of results. Use the next token provided by the previous results (string).
-};
-
-// Retrieve created application parameters for the Algorand account
-const createdApplications = await tatum.rpc.getAccountApplications(params);
-
-// Log the created application parameters
-console.log('Algorand Account Created Applications:', createdApplications);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getAccountApplications` method allows you to retrieve the created application parameters of a specific Algorand account.
-
-### Example Use Cases
-
-1. **Application Parameters**: Developers can use this method to retrieve the parameters of applications created by an Algorand account, including information about specific applications and their details.
-
-### Request Parameters
-
-The `getAccountApplications` method requires the following parameters:
-
-- `accountId` (string, required): Specify the Algorand account ID for which you want to retrieve created application parameters.
-- `applicationId` (number, optional): Specify the application ID for filtering the results.
-- `includeAll` (boolean, optional): Include all items, including closed accounts, deleted applications, destroyed assets, opted-out asset holdings, and closed-out application local states.
-- `limit` (number, optional): Maximum number of results to return.
-- `next` (string, optional): The next page of results. Use the next token provided by the previous results.
-
-### Return Object
-
-The method returns an object representing the created application parameters of the specified Algorand account, including information about specific applications and their details.
-
-Please note that the structure of the returned object may change in different Algorand RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccountapsslocalstate.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccountapsslocalstate.md
deleted file mode 100644
index edf2a7de..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccountapsslocalstate.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: "getAccountApssLocalState"
-slug: "rpc-algorand-getaccountapsslocalstate"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:03 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandIndexer, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_INDEXER });
-
-// Define optional query parameters
-const params = {
- accountId: 'ALGORAND_ACCOUNT_ID', // Replace with the Algorand account ID for which you want to retrieve local application state.
- applicationId: 123, // Optional: Specify the application ID (number) for filtering.
- includeAll: true, // Optional: Include all items, including closed accounts, deleted applications, destroyed assets, opted-out asset holdings, and closed-out application local states (boolean).
- limit: 100, // Optional: Maximum number of results to return (number).
- next: 'NEXT_PAGE_TOKEN' // Optional: The next page of results. Use the next token provided by the previous results (string).
-};
-
-// Retrieve local application state for the Algorand account
-const appsLocalState = await tatum.rpc.getAccountAppsLocalState(params);
-
-// Log the local application state information
-console.log('Algorand Account Local Application State:', appsLocalState);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getAccountAppsLocalState` method allows you to retrieve the local application state of a specific Algorand account.
-
-### Example Use Cases
-
-1. **Application State**: Developers can use this method to retrieve the local application state of an Algorand account, including information about its asset holdings and applications.
-
-### Request Parameters
-
-The `getAccountAppsLocalState` method requires the following parameters:
-
-- `account-id` (string, required): The Algorand account ID for which you want to retrieve local application state.
-- `application-id` (number, optional): Specify the application ID for filtering the results.
-- `include-all` (boolean, optional): Include all items, including closed accounts, deleted applications, destroyed assets, opted-out asset holdings, and closed-out application local states.
-- `limit` (number, optional): Maximum number of results to return.
-- `next` (string, optional): The next page of results. Use the next token provided by the previous results.
-
-### Return Object
-
-The method returns an object representing the local application state of the specified Algorand account, including information about asset holdings and applications.
-
-Please note that the structure of the returned object may change in different Algorand RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccountassetinfo.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccountassetinfo.md
deleted file mode 100644
index da76cb90..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccountassetinfo.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: "getAccountAssetInfo"
-slug: "rpc-algorand-getaccountassetinfo"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:01 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandAlgod, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_ALGOD });
-
-// Define the input parameters in a single object
-const params = {
- address: 'ALGORAND_ACCOUNT_ADDRESS', // Specify the Algorand account address for which you want to retrieve asset information.
- assetId: 123, // Specify the asset ID for which you want to retrieve information.
- format: 'json' // Optional: Configures whether the response object is JSON or MessagePack encoded. Defaults to JSON.
-};
-
-// Retrieve asset information for the Algorand account
-const assetInformation = await tatum.rpc.getAccountAssetInformation(params);
-
-// Log the asset information
-console.log('Algorand Account Asset Information:', assetInformation);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getAccountAssetInformation` method allows you to retrieve asset holding and asset parameters (if applicable) for a specific asset ID and account address.
-
-### Example Use Cases
-
-1. **Asset Holdings**: Developers can use this method to retrieve the asset holdings of a specific Algorand account, including information about the asset and its parameters.
-
-### Request Parameters
-
-The `getAccountAssetInformation` method requires the following parameters:
-
-- `address` (string, required): Specify the Algorand account address for which you want to retrieve asset information.
-- `assetId` (number, required): Specify the asset ID for which you want to retrieve information.
-- `format` (enum: json, msgpack, optional): Configures whether the response object is JSON or MessagePack encoded. Defaults to JSON.
-
-### Return Object
-
-The method returns an object representing the asset holding and asset parameters (if applicable) for the specified asset ID and account address.
-
-Please note that the structure of the returned object may change in different Algorand RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccountassets.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccountassets.md
deleted file mode 100644
index 4c431fe4..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccountassets.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: "getAccountAssets"
-slug: "rpc-algorand-getaccountassets"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:36 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandIndexer, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_INDEXER });
-
-// Define the input parameters in a single object
-const params = {
- accountId: 'ALGORAND_ACCOUNT_ID', // Specify the Algorand account ID for which you want to retrieve asset holdings.
- assetId: 123, // Optional: Specify the asset ID (number) for filtering.
- includeAll: true, // Optional: Include all items, including closed accounts, deleted applications, destroyed assets, opted-out asset holdings, and closed-out application local states (boolean).
- limit: 100, // Optional: Maximum number of results to return (number).
- next: 'NEXT_PAGE_TOKEN' // Optional: The next page of results. Use the next token provided by the previous results (string).
-};
-
-// Retrieve asset holdings for the Algorand account
-const accountAssets = await tatum.rpc.getAccountAssets(params);
-
-// Log the asset holdings information
-console.log('Algorand Account Asset Holdings:', accountAssets);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getAccountAssets` method allows you to retrieve the asset holdings of a specific Algorand account.
-
-### Example Use Cases
-
-1. **Asset Holdings**: Developers can use this method to retrieve the asset holdings of an Algorand account, including information about specific assets held by the account.
-
-### Request Parameters
-
-The `getAccountAssets` method requires the following parameters:
-
-- `accountId` (string, required): Specify the Algorand account ID for which you want to retrieve asset holdings.
-- `assetId` (number, optional): Specify the asset ID for filtering the results.
-- `includeAll` (boolean, optional): Include all items, including closed accounts, deleted applications, destroyed assets, opted-out asset holdings, and closed-out application local states.
-- `limit` (number, optional): Maximum number of results to return.
-- `next` (string, optional): The next page of results. Use the next token provided by the previous results.
-
-### Return Object
-
-The method returns an object representing the asset holdings of the specified Algorand account, including information about specific assets and their quantities.
-
-Please note that the structure of the returned object may change in different Algorand RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccountcreatedassets.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccountcreatedassets.md
deleted file mode 100644
index 101e0e54..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccountcreatedassets.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: "getAccountCreatedAssets"
-slug: "rpc-algorand-getaccountcreatedassets"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:03 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandIndexer, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_INDEXER });
-
-// Define the input parameters in a single object
-const params = {
- accountId: 'ALGORAND_ACCOUNT_ID', // Specify the Algorand account ID for which you want to retrieve created asset parameters.
- assetId: 123, // Optional: Specify the asset ID (number) for filtering.
- includeAll: true, // Optional: Include all items, including closed accounts, deleted applications, destroyed assets, opted-out asset holdings, and closed-out application local states (boolean).
- limit: 100, // Optional: Maximum number of results to return (number).
- next: 'NEXT_PAGE_TOKEN' // Optional: The next page of results. Use the next token provided by the previous results (string).
-};
-
-// Retrieve created asset parameters for the Algorand account
-const createdAssets = await tatum.rpc.getAccountCreatedAssets(params);
-
-// Log the created asset parameters
-console.log('Algorand Account Created Assets:', createdAssets);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getAccountCreatedAssets` method allows you to retrieve the created asset parameters of a specific Algorand account.
-
-### Example Use Cases
-
-1. **Asset Parameters**: Developers can use this method to retrieve the parameters of assets created by an Algorand account, including information about specific assets and their details.
-
-### Request Parameters
-
-The `getAccountCreatedAssets` method requires the following parameters:
-
-- `accountId` (string, required): Specify the Algorand account ID for which you want to retrieve created asset parameters.
-- `assetId` (number, optional): Specify the asset ID for filtering the results.
-- `includeAll` (boolean, optional): Include all items, including closed accounts, deleted applications, destroyed assets, opted-out asset holdings, and closed-out application local states.
-- `limit` (number, optional): Maximum number of results to return.
-- `next` (string, optional): The next page of results. Use the next token provided by the previous results.
-
-### Return Object
-
-The method returns an object representing the created asset parameters of the specified Algorand account, including information about specific assets and their details.
-
-Please note that the structure of the returned object may change in different Algorand RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccountinfo.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccountinfo.md
deleted file mode 100644
index c62028bc..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccountinfo.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-title: "getAccountInfo"
-slug: "rpc-algorand-getaccountinfo"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:00 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandAlgod, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_ALGOD });
-
-// Define the input parameters in a single object
-const params = {
- address: 'ALGORAND_ADDRESS', // Specify the Algorand public key for which you want to retrieve account information.
- format: 'json', // Optional: Configures whether the response object is JSON or MessagePack encoded (enum: json, msgpack).
- exclude: 'none' // Optional: When set to 'all' will exclude asset holdings, application local state, created asset parameters, any created application parameters. Defaults to 'none' (enum: all, none).
-};
-
-// Retrieve account information for the Algorand account
-const accountInfo = await tatum.rpc.getAccountInformation(params);
-
-// Log the account information
-console.log('Algorand Account Information:', accountInfo);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getAccountInformation` method allows you to retrieve the status, balance, and spendable amounts of a specific Algorand account.
-
-### Example Use Cases
-
-1. **Account Balance**: Developers can use this method to retrieve the balance and spendable amounts of an Algorand account.
-2. **Account Status**: Users can check the status of their Algorand account, including the account public key and other related information.
-
-### Request Parameters
-
-The `getAccountInformation` method requires the following parameters:
-
-- `address` (string, required): Specify the Algorand public key for which you want to retrieve account information.
-- `format` (enum: json, msgpack, optional): Configures whether the response object is JSON or MessagePack encoded. If not provided, defaults to JSON.
-- `exclude` (enum: all, none, optional): When set to 'all', it will exclude asset holdings, application local state, created asset parameters, and any created application parameters. Defaults to 'none'.
-
-### Return Object
-
-The method returns an object representing the account information of the specified Algorand account, including the account status, balance, and spendable amounts.
-
-Please note that the structure of the returned object may change in different Algorand RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccounts.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccounts.md
deleted file mode 100644
index 6db7a7c6..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccounts.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: "getAccounts"
-slug: "rpc-algorand-getaccounts"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:05 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules
-import { TatumSDK, AlgorandIndexer, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_INDEXER });
-
-// Define the input parameters
-const address = { address: 'ALGORAND_ADDRESS' }; // Replace with the Algorand address you want to retrieve account information for.
-
-// Retrieve account information using the Algorand Indexer
-const accountInfo = await tatum.rpc.getAccounts(address);
-
-// Log the account information
-console.log('Algorand Account Information:', accountInfo);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getAccounts` method from the Algorand Indexer API allows you to retrieve detailed information about an Algorand account based on its address.
-
-### Example Use Cases
-
-1. **Account Balance**: Developers can use this method to check the balance of an Algorand account by providing its address.
-
-2. **Account Details**: You can retrieve various details of an Algorand account, including its transactions, assets, and more, for further analysis.
-
-### Request Parameters
-
-The `getAccounts` method requires the following parameter:
-
-- `address` (string, required): The Algorand address for which you want to retrieve account information.
-
-### Return Object
-
-The method returns an object representing the detailed information of the specified Algorand account, including various parameters.
-
-Please note that the structure of the returned object may change in different Algorand RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccounttransactions.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccounttransactions.md
deleted file mode 100644
index d6eabcba..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getaccounttransactions.md
+++ /dev/null
@@ -1,93 +0,0 @@
----
-title: "getAccountTransactions"
-slug: "rpc-algorand-getaccounttransactions"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:05 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandIndexer, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_INDEXER });
-
-// Define the input parameters in a single object
-const params = {
- accountId: 'ALGORAND_ACCOUNT_ID', // Specify the Algorand account ID for which you want to retrieve transactions.
- afterTime: 'RFC3339_DATETIME', // Optional: Include results after the given time (string in RFC 3339 format).
- assetId: 123, // Optional: Specify the asset ID (number) for filtering.
- beforeTime: 'RFC3339_DATETIME', // Optional: Include results before the given time (string in RFC 3339 format).
- currencyGreaterThan: 1000, // Optional: Results should have an amount greater than this value (number).
- currencyLessThan: 5000, // Optional: Results should have an amount less than this value (number).
- limit: 100, // Optional: Maximum number of results to return (number).
- maxRound: 10000, // Optional: Include results at or before the specified max-round (number).
- minRound: 9000, // Optional: Include results at or after the specified min-round (number).
- next: 'NEXT_PAGE_TOKEN', // Optional: The next page of results. Use the next token provided by the previous results (string).
- notePrefix: 'NOTE_PREFIX', // Optional: Specifies a prefix which must be contained in the note field (string).
- rekeyTo: true, // Optional: Include results which include the rekey-to field (boolean).
- round: 8000, // Optional: Include results for the specified round (number).
- sigType: 'sig', // Optional: SigType filters just results using the specified type of signature (enum: sig, msig, lsig).
- txType: 'pay', // Optional: Filters results by transaction type (enum: pay, keyreg, acfg, axfer, afrz, appl, stpf).
- txId: 'TRANSACTION_ID' // Optional: Lookup the specific transaction by ID (string).
-};
-
-// Retrieve account transactions for the Algorand account
-const accountTransactions = await tatum.rpc.getAccountTransactions(params);
-
-// Log the account transactions
-console.log('Algorand Account Transactions:', accountTransactions);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getAccountTransactions` method allows you to retrieve transactions of a specific Algorand account.
-
-### Example Use Cases
-
-1. **Transaction History**: Developers can use this method to retrieve the transaction history of an Algorand account, including information about specific transactions and their details.
-
-### Request Parameters
-
-The `getAccountTransactions` method requires the following parameters:
-
-- `accountId` (string, required): Specify the Algorand account ID for which you want to retrieve transactions.
-- `afterTime` (string in RFC 3339 format, optional): Include results after the given time.
-- `assetId` (number, optional): Specify the asset ID for filtering.
-- `beforeTime` (string in RFC 3339 format, optional): Include results before the given time.
-- `currencyGreaterThan` (number, optional): Results should have an amount greater than this value.
-- `currencyLessThan` (number, optional): Results should have an amount less than this value.
-- `limit` (number, optional): Maximum number of results to return.
-- `maxRound` (number, optional): Include results at or before the specified max-round.
-- `minRound` (number, optional): Include results at or after the specified min-round.
-- `next` (string, optional): The next page of results. Use the next token provided by the previous results.
-- `notePrefix` (string, optional): Specifies a prefix which must be contained in the note field.
-- `rekeyTo` (boolean, optional): Include results which include the rekey-to field.
-- `round` (number, optional): Include results for the specified round.
-- `sigType` (enum: sig, msig, lsig, optional): Filters just results using the specified type of signature.
-- `txType` (enum: pay, keyreg, acfg, axfer, afrz, appl, stpf, optional): Filters results by transaction type.
-- `txId` (string, optional): Lookup the specific transaction by ID.
-
-### Return Object
-
-The method returns an object representing the transactions of the specified Algorand account, including information about specific transactions and their details.
-
-Please note that the structure of the returned object may change in different Algorand RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getapplication.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getapplication.md
deleted file mode 100644
index c95e299b..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getapplication.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: "getApplication"
-slug: "rpc-algorand-getapplication"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:38 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandIndexer, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_INDEXER });
-
-// Define the input parameters in a single object
-const params = {
- applicationId: 123, // Specify the application ID (number) you want to lookup.
- includeAll: true // Optional: Include all items, including closed accounts, deleted applications, destroyed assets, opted-out asset holdings, and closed-out application local states (boolean).
-};
-
-// Lookup the Algorand application
-const applicationInfo = await tatum.rpc.getApplication(params);
-
-// Log the application information
-console.log('Algorand Application Information:', applicationInfo);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getApplication` method allows you to lookup an Algorand application.
-
-### Example Use Cases
-
-1. **Application Information**: Developers can use this method to retrieve detailed information about a specific Algorand application, including its status and details.
-
-### Request Parameters
-
-The `getApplication` method requires the following parameters:
-
-- `applicationId` (number, required): Specify the application ID you want to lookup.
-- `includeAll` (boolean, optional): Include all items, including closed accounts, deleted applications, destroyed assets, opted-out asset holdings, and closed-out application local states.
-
-### Return Object
-
-The method returns an object representing the information about the specified Algorand application, including its status and details.
-
-Please note that the structure of the returned object may change in different Algorand RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getapplicationbox.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getapplicationbox.md
deleted file mode 100644
index f00910e6..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getapplicationbox.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: "getApplicationBox"
-slug: "rpc-algorand-getapplicationbox"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:40 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandIndexer, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_INDEXER });
-
-// Define the input parameters in a single object
-const params = {
- applicationId: 123, // Specify the application ID (number) for which you want to get the box information.
- name: 'int:1234' // Specify the box name in goal-arg form (string).
-};
-
-// Get the box information for the Algorand application
-const boxInfo = await tatum.rpc.getApplicationBox(params);
-
-// Log the box information
-console.log('Algorand Application Box Information:', boxInfo);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getApplicationBox` method allows you to get box information for a given Algorand application.
-
-### Example Use Cases
-
-1. **Box Information**: Developers can use this method to retrieve base64 encoded box name and value for a specific box within an Algorand application.
-
-### Request Parameters
-
-The `getApplicationBox` method requires the following parameters:
-
-- `applicationId` (number, required): Specify the application ID for which you want to get the box information.
-- `name` (string, required): Specify the box name in goal-arg form, such as 'int:1234', 'b64:A==', 'str:hello', or 'addr:XYZ...'.
-
-### Return Object
-
-The method returns an object representing the base64 encoded box name and value for the specified box within the Algorand application.
-
-Please note that the structure of the returned object may change in different Algorand RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getapplicationboxes.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getapplicationboxes.md
deleted file mode 100644
index 29a87c9e..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getapplicationboxes.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: "getApplicationBoxes"
-slug: "rpc-algorand-getapplicationboxes"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:44 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandIndexer, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_INDEXER });
-
-// Define the input parameters in a single object
-const params = {
- applicationId: 123, // Specify the application ID (number) for which you want to get box names.
- limit: 100, // Optional: Maximum number of results to return (number).
- next: 'NEXT_TOKEN' // Optional: The next page of results. Use the next token provided by the previous results (string).
-};
-
-// Get the box names for the Algorand application
-const boxNames = await tatum.rpc.getApplicationBoxes(params);
-
-// Log the box names
-console.log('Algorand Application Box Names:', boxNames);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getApplicationBoxes` method allows you to get box names for a given Algorand application.
-
-### Example Use Cases
-
-1. **Box Names**: Developers can use this method to retrieve the box names of an Algorand application sorted lexicographically.
-
-### Request Parameters
-
-The `getApplicationBoxes` method requires the following parameters:
-
-- `applicationId` (number, required): Specify the application ID for which you want to get box names.
-- `limit` (number, optional): Maximum number of results to return.
-- `next` (string, optional): The next page of results. Use the next token provided by the previous results.
-
-### Return Object
-
-The method returns an array of box names for the specified Algorand application, sorted lexicographically.
-
-Please note that the structure of the returned object may change in different Algorand RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getapplicationdetails.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getapplicationdetails.md
deleted file mode 100644
index aaa330dc..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getapplicationdetails.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: "getApplicationDetails"
-slug: "rpc-algorand-getapplicationdetails"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:02 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandIndexer, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_INDEXER });
-
-// Define the input parameters in a single object
-const params = {
- applicationId: 'APPLICATION_ID', // Application ID to filter the applications (number, optional).
- creator: 'CREATOR_ADDRESS', // Filter applications by the creator address (string, optional).
- includeAll: true, // Include all items like closed accounts and deleted applications (boolean, optional).
- limit: 100, // Maximum number of results to return (number, optional).
- next: 'NEXT_PAGE_TOKEN' // The next page of results. Use the next token from previous results (string, optional).
-};
-
-// Retrieve details of the specified Algorand application
-const applicationDetails = await tatum.rpc.getApplicationDetails(params);
-
-// Log the details of the Algorand application
-console.log('Algorand Application Details:', applicationDetails);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getApplicationDetails` method fetches details for Algorand applications, with the ability to filter based on the application ID, creator, and other criteria.
-
-### Request Parameters
-
-- `applicationId` (number, optional): Application ID to filter the applications.
-- `creator` (string, optional): Filter applications by the creator address.
-- `includeAll` (boolean, optional): Include all related items in the results.
-- `limit` (number, optional): Maximum number of results to return.
-- `next` (string, optional): The next page of results, using the next token from previous results.
-
-### Return Object
-
-The method returns detailed information about the specified Algorand applications based on the provided filters.
-
-Please note that the structure of the returned object may change in different Algorand RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getapplicationlogs.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getapplicationlogs.md
deleted file mode 100644
index b60e8273..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getapplicationlogs.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: "getApplicationLogs"
-slug: "rpc-algorand-getapplicationlogs"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:05 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandIndexer, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_INDEXER });
-
-// Define the input parameters in a single object
-const params = {
- applicationId: 123, // Specify the application ID (number) for which you want to lookup logs.
- limit: 100, // Optional: Maximum number of results to return (number).
- maxRound: 10000, // Optional: Include results at or before the specified max-round (number).
- minRound: 9000, // Optional: Include results at or after the specified min-round (number).
- next: 'NEXT_PAGE_TOKEN', // Optional: The next page of results. Use the next token provided by the previous results (string).
- senderAddress: 'ALGORAND_SENDER_ADDRESS', // Optional: Only include transactions with this sender address (string).
- txId: 'TRANSACTION_ID' // Optional: Lookup the specific transaction by ID (string).
-};
-
-// Lookup application logs for the Algorand application
-const applicationLogs = await tatum.rpc.getApplicationLogs(params);
-
-// Log the application logs
-console.log('Algorand Application Logs:', applicationLogs);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getApplicationLogs` method allows you to lookup logs for an Algorand application.
-
-### Example Use Cases
-
-1. **Application Logs**: Developers can use this method to retrieve logs associated with a specific Algorand application.
-
-### Request Parameters
-
-The `getApplicationLogs` method requires the following parameters:
-
-- `applicationId` (number, required): Specify the application ID for which you want to lookup logs.
-- `limit` (number, optional): Maximum number of results to return.
-- `maxRound` (number, optional): Include results at or before the specified max-round.
-- `minRound` (number, optional): Include results at or after the specified min-round.
-- `next` (string, optional): The next page of results. Use the next token provided by the previous results.
-- `senderAddress` (string, optional): Only include transactions with this sender address.
-- `txId` (string, optional): Lookup the specific transaction by ID.
-
-### Return Object
-
-The method returns an array of application logs for the specified Algorand application.
-
-Please note that the structure of the returned object may change in different Algorand RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getapplications.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getapplications.md
deleted file mode 100644
index eeac9768..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getapplications.md
+++ /dev/null
@@ -1,77 +0,0 @@
----
-title: "getApplications"
-slug: "rpc-algorand-getapplications"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:41 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandIndexer, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_INDEXER });
-
-// Define the input parameters as a dictionary object
-const params = {
- applicationId: 123, // Application ID (integer).
- creator: 'ALGORAND_ADDRESS', // Filter just applications with the given creator address (string).
- includeAll: true, // Include all items including closed accounts, deleted applications, destroyed assets, opted-out asset holdings, and closed-out application localstates (boolean).
- limit: 10, // Maximum number of results to return (integer).
- next: 'NEXT_TOKEN', // The next page of results. Use the next token provided by the previous results (string).
-};
-
-// Search for applications
-const applications = await tatum.indexer.getApplications(params);
-
-// Log the applications
-console.log('Applications:', applications);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getApplications` method allows you to search for applications on the Algorand network using various filtering criteria. You can filter applications by their Application ID, creator address, and more.
-
-### Request Parameters
-
-The `getApplications` method requires the following parameters:
-
-- `applicationId` (integer, optional): Application ID used to filter applications.
-
-- `creator` (string, optional): Filter applications by the creator's address.
-
-- `includeAll` (boolean, optional): Whether to include all items, including closed accounts, deleted applications, destroyed assets, opted-out asset holdings, and closed-out application localstates.
-
-- `limit` (integer, optional): Maximum number of results to return. Additional pages may be available even if the limit is not reached.
-
-- `next` (string, optional): The next page token to use for pagination. Provide this token when making another request to retrieve the next set of results.
-
-### Return Object
-
-The method returns a response object containing information about the applications:
-
-- `applications` (array of objects): An array of application objects that match the search criteria.
-
-- `current-round` (integer): The round at which the results were computed.
-
-- `next-token` (string): Used for pagination. When making another request, provide this token with the `next` parameter to retrieve the next set of results.
-
-Please note that the structure of the returned object may change in different Algorand Indexer API versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getasset.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getasset.md
deleted file mode 100644
index e5790c0c..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getasset.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: "getAsset"
-slug: "rpc-algorand-getasset"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:06 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandIndexer, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_INDEXER });
-
-// Define the input parameters as a dictionary object
-const params = {
- assetId: 123, // Specify the asset ID (number) for which you want to lookup asset information.
- includeAll: true // Optional: Include all items, including closed accounts, deleted applications, destroyed assets, opted-out asset holdings, and closed-out application localstates (boolean).
-};
-
-// Lookup asset information
-const assetInfo = await tatum.rpc.getAsset(params);
-
-// Log the asset information
-console.log('Asset Information:', assetInfo);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getAsset` method allows you to lookup information for a specific asset.
-
-### Example Use Cases
-
-1. **Asset Lookup**: Developers can use this method to retrieve detailed information about a specific asset.
-
-### Request Parameters
-
-The `getAsset` method requires the following parameters, all included in the `params` dictionary object:
-
-- `assetId` (number, required): Specify the asset ID for which you want to lookup asset information.
-- `includeAll` (boolean, optional): Include all items, including closed accounts, deleted applications, destroyed assets, opted-out asset holdings, and closed-out application localstates (boolean).
-
-### Return Object
-
-The method returns an object representing the detailed information of the specified asset, including its properties.
-
-Please note that the structure of the returned object may change in different RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getassetbalances.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getassetbalances.md
deleted file mode 100644
index 388eea65..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getassetbalances.md
+++ /dev/null
@@ -1,73 +0,0 @@
----
-title: "getAssetBalances"
-slug: "rpc-algorand-getassetbalances"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:42 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandIndexer, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_INDEXER });
-
-// Define the input parameters as a dictionary object
-const params = {
- assetId: 123, // Specify the asset ID (number) for which you want to lookup balances.
- currencyGreaterThan: 100, // Optional: Results should have an amount greater than this value (number).
- currencyLessThan: 500, // Optional: Results should have an amount less than this value (number).
- includeAll: true, // Optional: Include all items, including closed accounts, deleted applications, destroyed assets, opted-out asset holdings, and closed-out application localstates (boolean).
- limit: 100, // Optional: Maximum number of results to return (number).
- next: 'NEXT_PAGE_TOKEN' // Optional: The next page of results. Use the next token provided by the previous results (string).
-};
-
-// Lookup the list of accounts holding the specified asset
-const assetBalances = await tatum.rpc.getAssetBalances(params);
-
-// Log the list of accounts and their asset balances
-console.log('Asset Balances:', assetBalances);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getAssetBalances` method allows you to lookup the list of accounts that hold a specific asset.
-
-### Example Use Cases
-
-1. **Asset Balances**: Developers can use this method to retrieve a list of accounts holding a particular asset, with optional filters for currency amounts.
-
-### Request Parameters
-
-The `getAssetBalances` method requires the following parameters:
-
-- `assetId` (number, required): Specify the asset ID for which you want to lookup balances.
-- `currencyGreaterThan` (number, optional): Results should have an amount greater than this value (number).
-- `currencyLessThan` (number, optional): Results should have an amount less than this value (number).
-- `includeAll` (boolean, optional): Include all items, including closed accounts, deleted applications, destroyed assets, opted-out asset holdings, and closed-out application localstates (boolean).
-- `limit` (number, optional): Maximum number of results to return (number).
-- `next` (string, optional): The next page of results. Use the next token provided by the previous results (string).
-
-### Return Object
-
-The method returns a list of accounts holding the specified asset, along with their asset balances.
-
-Please note that the structure of the returned object may change in different RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getassetinformation.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getassetinformation.md
deleted file mode 100644
index e154e034..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getassetinformation.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: "getAssetInformation"
-slug: "rpc-algorand-getassetinformation"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:03 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandAlgod, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_ALGOD });
-
-// Define the input parameters in a single object
-const params = {
- assetId: 123, // Specify the asset ID for which you want to retrieve information.
-};
-
-// Retrieve the asset information for the specified asset ID
-const assetInfo = await tatum.rpc.getAssetInformation(params);
-
-// Log the asset information
-console.log('Asset Information:', assetInfo);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getAssetInformation` method allows you to retrieve asset information, including creator, name, total supply, and special addresses, for a specific asset ID.
-
-### Example Use Cases
-
-1. **Asset Details**: Developers can use this method to retrieve detailed information about a specific asset, including the address of the asset's creator, the name of the asset, the total supply of the asset, and any special addresses associated with the asset.
-
-### Request Parameters
-
-The `getAssetInformation` method requires the following parameter:
-
-- `assetId` (integer, required): An asset identifier representing the asset for which you want to retrieve information.
-
-### Return Object
-
-The method returns an object representing the asset information for the specified asset ID. The returned object includes details such as the asset's creator, name, total supply, and special addresses.
-
-Please note that the structure of the returned object may change in different Algorand RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getassets.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getassets.md
deleted file mode 100644
index e1cdaeec..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getassets.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: "getAssets"
-slug: "rpc-algorand-getassets"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:01 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandIndexer, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_INDEXER });
-
-// Define the input parameters in a single object
-const params = {
- assetId: 123, // Optional: Asset ID (number).
- creator: 'CREATOR_ADDRESS', // Optional: Filter assets with the given creator address (string).
- includeAll: true, // Optional: Include all items, including closed accounts, deleted applications, destroyed assets, opted-out asset holdings, and closed-out application localstates (boolean).
- limit: 100, // Optional: Maximum number of results to return (number).
- name: 'ASSET_NAME', // Optional: Filter assets with the given name (string).
- next: 'NEXT_PAGE_TOKEN', // Optional: The next page of results. Use the next token provided by the previous results (string).
- unit: 'ASSET_UNIT' // Optional: Filter assets with the given unit (string).
-};
-
-// Search for assets using the Algorand Indexer
-const assets = await tatum.rpc.getAssets(params);
-
-// Log the asset information
-console.log('Algorand Assets:', assets);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getAssets` method allows you to search for assets in the Algorand blockchain.
-
-### Example Use Cases
-
-1. **Asset Search**: Developers can use this method to search for assets with specific criteria, such as asset ID, creator address, name, or unit.
-
-### Request Parameters
-
-The `getAssets` method requires the following parameters:
-
-- `assetId` (number, optional): Asset ID to filter assets by (number).
-- `creator` (string, optional): Filter assets with the given creator address (string).
-- `includeAll` (boolean, optional): Include all items, including closed accounts, deleted applications, destroyed assets, opted-out asset holdings, and closed-out application localstates (boolean).
-- `limit` (number, optional): Maximum number of results to return (number).
-- `name` (string, optional): Filter assets with the given name (string).
-- `next` (string, optional): The next page of results. Use the next token provided by the previous results (string).
-- `unit` (string, optional): Filter assets with the given unit (string).
-
-### Return Object
-
-The method returns an array of asset information that matches the specified criteria.
-
-Please note that the structure of the returned object may change in different Algorand RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getassettransactions.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getassettransactions.md
deleted file mode 100644
index 38d3d07d..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getassettransactions.md
+++ /dev/null
@@ -1,91 +0,0 @@
----
-title: "getAssetTransactions"
-slug: "rpc-algorand-getassettransactions"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:05 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandIndexer, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_INDEXER });
-
-// Define the input parameters as a dictionary object
-const params = {
- assetId: 123, // Specify the asset ID (number) for which you want to lookup transactions.
- address: 'ALGORAND_ADDRESS', // Optional: Include transactions with this address in one of the transaction fields (string).
- addressRole: 'sender', // Optional: Define what type of address to search for (enum: sender, receiver, freeze-target).
- afterTime: '2023-11-06T00:00:00Z', // Optional: Include results after the given time (RFC 3339 formatted string).
- beforeTime: '2023-11-07T00:00:00Z', // Optional: Include results before the given time (RFC 3339 formatted string).
- currencyGreaterThan: 100, // Optional: Results should have an amount greater than this value (number).
- currencyLessThan: 500, // Optional: Results should have an amount less than this value (number).
- excludeCloseTo: true, // Optional: Exclude close-to addresses when searching for a specific address (boolean).
- limit: 100, // Optional: Maximum number of results to return (number).
- maxRound: 1000, // Optional: Include results at or before the specified max-round (number).
- minRound: 900, // Optional: Include results at or after the specified min-round (number).
- next: 'NEXT_PAGE_TOKEN', // Optional: The next page of results. Use the next token provided by the previous results (string).
- notePrefix: 'PREFIX_TEXT', // Optional: Specify a prefix that must be contained in the note field (string).
- rekeyTo: true, // Optional: Include results which include the rekey-to field (boolean).
- round: 1000, // Optional: Include results for the specified round (number).
- sigType: 'sig', // Optional: Filter results using the specified type of signature (enum: sig, msig, lsig).
- txType: 'pay', // Optional: Filter results by transaction type (enum: pay, keyreg, acfg, axfer, afrz, appl, stpf).
- txId: 'TRANSACTION_ID' // Optional: Lookup the specific transaction by ID (string).
-};
-
-// Lookup transactions for the specified asset
-const assetTransactions = await tatum.rpc.getAssetTransactions(params);
-
-// Log the list of transactions related to the asset
-console.log('Asset Transactions:', assetTransactions);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getAssetTransactions` method allows you to lookup transactions for a specific asset. Transactions are returned in chronological order, from oldest to newest.
-
-### Request Parameters
-
-The method requires the following parameters:
-
-- `assetId` (number, required): Specify the asset ID for which you want to lookup transactions.
-- `address` (string, optional): Include transactions with this address in one of the transaction fields.
-- `addressRole` (enum, optional): Define what type of address to search for (sender, receiver, freeze-target).
-- `afterTime` (string, optional): Include results after the given time (RFC 3339 formatted string).
-- `beforeTime` (string, optional): Include results before the given time (RFC 3339 formatted string).
-- `currencyGreaterThan` (number, optional): Results should have an amount greater than this value.
-- `currencyLessThan` (number, optional): Results should have an amount less than this value.
-- `excludeCloseTo` (boolean, optional): Exclude close-to addresses when searching for a specific address.
-- `limit` (number, optional): Maximum number of results to return.
-- `maxRound` (number, optional): Include results at or before the specified max-round.
-- `minRound` (number, optional): Include results at or after the specified min-round.
-- `next` (string, optional): The next page of results. Use the next token provided by the previous results.
-- `notePrefix` (string, optional): Specify a prefix that must be contained in the note field.
-- `rekeyTo` (boolean, optional): Include results which include the rekey-to field.
-- `round` (number, optional): Include results for the specified round.
-- `sigType` (enum, optional): Filter results using the specified type of signature (
-
-### Return Object
-
-The method returns a list of transactions related to the specified asset. Transactions are returned in chronological order, from oldest to newest. Each transaction in the list includes details such as transaction ID, sender address, receiver address, transaction type, and more.
-
-Please note that the structure of the returned object may change in different RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getblock.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getblock.md
deleted file mode 100644
index ce6f8965..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getblock.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: "getBlock"
-slug: "rpc-algorand-getblock"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:04 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandIndexer, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_INDEXER });
-
-// Define the input parameters as a dictionary object
-const params = {
- roundNumber: 1000, // Specify the round number (integer) for which you want to lookup the block.
- headerOnly: true // Optional: Set to true to retrieve only the block header without transactions (boolean).
-};
-
-// Lookup the block for the specified round number
-const blockInfo = await tatum.rpc.getBlock(params);
-
-// Log the block information
-console.log('Block Information:', blockInfo);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getBlock` method allows you to lookup a block by specifying its round number. You can retrieve both the block header and transactions, or only the block header using the `headerOnly` flag.
-
-### Request Parameters
-
-The method requires the following parameters:
-
-- `roundNumber` (number, required): Specify the round number for which you want to lookup the block.
-- `headerOnly` (boolean, optional): Set to true to retrieve only the block header without transactions (boolean).
-
-### Return Object
-
-The method returns information about the specified block, which includes details such as the block's round number, timestamp, previous block ID, seed, transactions, and more. If the `headerOnly` flag is set to true, the returned object will contain only the block header information.
-
-Please note that the structure of the returned object may change in different RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getblockhash.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getblockhash.md
deleted file mode 100644
index 1994ea68..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getblockhash.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: "getBlockHash"
-slug: "rpc-algorand-getblockhash"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:01 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandAlgod, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_ALGOD });
-
-// Define the input parameters in a single object
-const params = {
- round: 12345, // Specify the round from which you want to fetch block hash information (integer).
-};
-
-// Get the block hash for the specified round
-const blockHash = await tatum.rpc.getBlockHash(params);
-
-// Log the block hash
-console.log('Block Hash:', blockHash);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getBlockHash` method allows you to fetch the block hash information for a specific block on the Algorand blockchain.
-
-### Example Use Cases
-
-1. **Retrieve Block Hash**: Developers can use this method to fetch the block hash for a specific block on the Algorand blockchain.
-
-### Request Parameters
-
-The `getBlockHash` method requires the following parameter:
-
-- `round` (integer, required): Specify the round from which you want to fetch block hash information.
-
-### Return Object
-
-The method returns an object representing the block hash of the specified round on the Algorand blockchain.
-
-Please note that the structure of the returned object may change in different Algorand RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getgenesis.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getgenesis.md
deleted file mode 100644
index 630ca065..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getgenesis.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: "getGenesis"
-slug: "rpc-algorand-getgenesis"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:43 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandAlgod, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_ALGOD });
-
-// Retrieve the genesis information
-const genesisInfo = await tatum.rpc.getGenesis();
-
-// Log the genesis information
-console.log('Algorand Genesis:', genesisInfo);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getGenesis` method allows you to retrieve the entire genesis file in JSON format.
-
-### Example Use Cases
-
-1. **Genesis Information**: Developers can use this method to retrieve the genesis information of the Algorand network, including details about the network configuration.
-
-### Request Parameters
-
-The `getGenesis` method does not require any parameters.
-
-### Return Object
-
-The method returns a string representing the entire genesis file in JSON format.
-
-Please note that the structure of the returned object may change in different Algorand RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-gethealth.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-gethealth.md
deleted file mode 100644
index 55b1736a..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-gethealth.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: "getHealth"
-slug: "rpc-algorand-gethealth"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:42 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandIndexer, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_INDEXER });
-
-// Check the health status of the Algorand node
-const healthStatus = await tatum.rpc.health();
-
-// Log the health status
-console.log('Algorand Node Health Status:', healthStatus);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getHealth` method allows you to check the health status of the Algorand node connected to the Tatum SDK. It provides information about the node's availability and operational status.
-
-### Example Use Cases:
-
-1. **Node Monitoring:** Developers and operators can use this method to monitor the health of the Algorand node connected to their application and ensure it is operational.
-
-2. **Application Resilience:** It can be used to build resilience into your application by checking the health status of the node before making requests to it.
-
-### Return Object
-
-The method returns an object representing the health status of the Algorand Indexer node.
-
-Please note that the structure of the returned object may change in different Algorand RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getledgerstatedelta.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getledgerstatedelta.md
deleted file mode 100644
index faffce5f..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getledgerstatedelta.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: "getLedgerStateDelta"
-slug: "rpc-algorand-getledgerstatedelta"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:03 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandAlgod, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_ALGOD });
-
-// Define the input parameters in a single object
-const params = {
- round: 12345, // Specify the round for which the deltas are desired (number).
- format: 'json' // Optional: Configures whether the response object is JSON or MessagePack encoded. If not provided, defaults to JSON (enum: json, msgpack).
-};
-
-// Retrieve ledger deltas for the specified round
-const ledgerStateDelta = await tatum.rpc.getLedgerStateDelta(params);
-
-// Log the ledger deltas
-console.log('Ledger State Delta:', ledgerStateDelta);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getLedgerStateDelta` method allows you to retrieve the ledger deltas for a specific round in the Algorand network.
-
-### Example Use Cases
-
-1. **Ledger Analysis**: Developers can use this method to retrieve the ledger deltas for a specific round and analyze the changes in the Algorand ledger.
-
-### Request Parameters
-
-The `getLedgerStateDelta` method requires the following parameters:
-
-- `round` (number, required): Specify the round for which the deltas are desired.
-- `format` (enum: json, msgpack, optional): Configures whether the response object is JSON or MessagePack encoded. If not provided, it defaults to JSON.
-
-### Return Object
-
-The method returns an object representing the ledger deltas for the specified round in the Algorand network.
-
-Please note that the structure and contents of the returned object may vary depending on the Algorand network and RPC version.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getledgersupply.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getledgersupply.md
deleted file mode 100644
index df469cd5..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getledgersupply.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: "getLedgerSupply"
-slug: "rpc-algorand-getledgersupply"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:02 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandAlgod, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_ALGOD });
-
-// Retrieve the current supply of MicroAlgos reported by the ledger
-const supply = await tatum.rpc.getLedgerSupply();
-
-// Log the current supply
-console.log('Algorand Current Supply:', supply);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getLedgerSupply` method allows you to retrieve the current supply of MicroAlgos reported by the ledger.
-
-### Example Use Cases
-
-1. **Supply Information**: Developers can use this method to retrieve the current supply of MicroAlgos in the Algorand system.
-
-### Request Parameters
-
-The `getLedgerSupply` method does not require any parameters.
-
-### Return Object
-
-The method returns an object representing the current supply of MicroAlgos in the Algorand system.
-
-Please note that the structure of the returned object may change in different Algorand RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getnodestatus.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getnodestatus.md
deleted file mode 100644
index 5715d4da..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getnodestatus.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: "getNodeStatus"
-slug: "rpc-algorand-getnodestatus"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:02 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandAlgod, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_ALGOD });
-
-// Retrieve the current node status
-const nodeStatus = await tatum.rpc.getNodeStatus();
-
-// Log the node status
-console.log('Algorand Node Status:', nodeStatus);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getNodeStatus` method allows you to retrieve the current status of an Algorand node.
-
-### Example Use Cases
-
-1. **Check Node Status**: Developers can use this method to check the status of an Algorand node and get information about the node's catchup progress, last round seen, consensus version details, and more.
-
-### Request Parameters
-
-The `getNodeStatus` method does not require any parameters.
-
-### Return Object
-
-The method returns an object representing the current status of the Algorand node. The object contains information about the node's catchup progress, last round seen, consensus version details, and more.
-
-Please note that the structure of the returned object may change in different Algorand RPC versions.
-
-```
-
-
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getnodestatusafterround.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getnodestatusafterround.md
deleted file mode 100644
index 86d400de..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getnodestatusafterround.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: "getNodeStatusAfterRound"
-slug: "rpc-algorand-getnodestatusafterround"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:07 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandAlgod, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_ALGOD });
-
-// Define the input parameters in a single object
-const params = {
- round: 10000 // Specify the round to wait until returning status.
-};
-
-// Wait for a block to appear after the specified round and return the node's status at the time
-const nodeStatus = await tatum.rpc.getNodeStatusAfterRound(params);
-
-// Log the node status
-console.log('Algorand Node Status:', nodeStatus);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getNodeStatusAfterRound` method allows you to wait for a block to appear after a specified round and returns the node's status at that time.
-
-### Example Use Cases
-
-1. **Wait for Block**: Developers can use this method to wait for a specific round and retrieve the node's status when a block appears after that round.
-
-### Request Parameters
-
-The `getNodeStatusAfterRound` method requires the following parameter:
-
-- `round` (integer, required): The round to wait until returning status.
-
-### Return Object
-
-The method returns an object representing the node's status at the time a block appears after the specified round. The object includes various properties that provide information about the node's status, such as catchpoints, catchup progress, last round seen, consensus version, and voting information.
-
-Please note that the structure of the returned object may change in different Algorand RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getpendingtransactions.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getpendingtransactions.md
deleted file mode 100644
index 6d921172..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-getpendingtransactions.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: "getPendingTransactions"
-slug: "rpc-algorand-getpendingtransactions"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:06 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandAlgod, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_ALGOD });
-
-// Define the input parameters in a single object
-const params = {
- max: 10, // Optional: Truncated number of transactions to display. If max=0, returns all pending txns (number).
- format: 'json', // Optional: Configures whether the response object is JSON or MessagePack encoded (enum: json, msgpack).
-};
-
-// Retrieve the list of pending transactions
-const pendingTransactions = await tatum.rpc.getPendingTransactions(params);
-
-// Log the pending transactions
-console.log('Pending Transactions:', pendingTransactions);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getPendingTransactions` method allows you to retrieve the list of unconfirmed transactions currently in the transaction pool.
-
-### Example Use Cases
-
-1. **Monitor Pending Transactions**: Developers can use this method to monitor and retrieve information about pending transactions in the transaction pool.
-
-### Request Parameters
-
-The `getPendingTransactions` method requires the following parameters:
-
-- `max` (number, optional): Truncated number of transactions to display. If max = 0, returns all pending transactions.
-- `format` (enum: json, msgpack, optional): Configures whether the response object is JSON or MessagePack encoded. If not provided, defaults to JSON.
-
-### Return Object
-
-The method returns a potentially truncated list of transactions currently in the node's transaction pool. This includes an array of signed transaction objects as they were submitted, along with the total number of transactions in the pool.
-
-You can compute whether or not the list is truncated if the number of elements in the `top-transactions` array is fewer than `total-transactions`.
-
-Please note that the structure of the returned object may vary depending on the Algorand RPC version.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-gettransaction.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-gettransaction.md
deleted file mode 100644
index 097d32d9..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-gettransaction.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: "getTransaction"
-slug: "rpc-algorand-gettransaction"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:03 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandIndexer, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_INDEXER });
-
-// Define the input parameters as a dictionary object
-const txId = { txId : 'TRANSACTION_ID'}; // Specify the transaction ID you want to lookup (string).
-
-// Lookup a single transaction by its ID
-const transaction = await tatum.rpc.getTransactionById(txId);
-
-// Log the transaction information
-console.log('Transaction Information:', transaction);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getTransactionById` method allows you to lookup a single transaction by its unique transaction ID.
-
-### Request Parameters
-
-The method requires the following parameter:
-
-- `txId` (string, required): Specify the transaction ID you want to lookup.
-
-### Return Object
-
-The method returns information about the specified transaction, including details such as the transaction's ID, sender address, receiver address, transaction type, amount, and more.
-
-Please note that the structure of the returned object may change in different RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-gettransactionparams.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-gettransactionparams.md
deleted file mode 100644
index de4999d8..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-gettransactionparams.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: "getTransactionParams"
-slug: "rpc-algorand-gettransactionparams"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:43 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandAlgod, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_ALGOD });
-
-// Retrieve transaction parameters for constructing a new transaction
-const transactionParams = await tatum.rpc.getTransactionParams();
-
-// Log the transaction parameters
-console.log('Transaction Parameters:', transactionParams);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getTransactionParams` method allows you to retrieve the parameters that help a client construct a new transaction in Algorand.
-
-### Example Use Cases
-
-1. **Transaction Construction**: Developers can use this method to get the necessary parameters required for constructing a new transaction in Algorand.
-
-### Request Parameters
-
-The `getTransactionParams` method does not require any parameters.
-
-### Return Object
-
-The method returns an object representing the parameters that help a client construct a new transaction in Algorand. The returned object includes the following properties:
-
-- `consensus-version` (string): Indicates the consensus protocol version as of LastRound.
-- `fee` (integer): The suggested transaction fee. The fee is in units of micro-Algos per byte. The fee may fall to zero but transactions must still have a fee of at least MinTxnFee for the current network protocol.
-- `genesis-hash` (string): The hash of the genesis block.
-- `genesis-id` (string): An ID listed in the genesis block.
-- `last-round` (integer): Indicates the last round seen.
-- `min-fee` (integer): The minimum transaction fee (not per byte) required for the transaction to validate for the current network protocol.
-
-Please note that the structure of the returned object may change in different Algorand RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-gettransactionproof.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-gettransactionproof.md
deleted file mode 100644
index 1ff4bb60..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-gettransactionproof.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: "getTransactionProof"
-slug: "rpc-algorand-gettransactionproof"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:06 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandAlgod, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_ALGOD });
-
-// Define the input parameters in a single object
-const params = {
- round: ROUND_NUMBER, // Specify the round in which the transaction appears.
- txid: 'TRANSACTION_ID', // Specify the transaction ID for which to generate a proof.
- format: 'json', // Optional: Configures whether the response object is JSON or MessagePack encoded. If not provided, defaults to JSON.
- hashtype: 'sha512_256' // Optional: The type of hash function used to create the proof, must be one of: sha512_256 or sha256.
-};
-
-// Generate a proof for a transaction in a block
-const transactionProof = await tatum.rpc.getTransactionProof(params);
-
-// Log the transaction proof
-console.log('Transaction Proof:', transactionProof);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getTransactionProof` method allows you to get a proof for a transaction in a block.
-
-### Example Use Cases
-
-1. **Transaction Verification**: Developers can use this method to get a proof for a transaction in a block in order to verify the authenticity and integrity of the transaction.
-
-### Request Parameters
-
-The `getTransactionProof` method requires the following parameters:
-
-- `round` (integer, required): Specify the round in which the transaction appears.
-- `txid` (string, required): Specify the transaction ID for which to generate a proof.
-- `hashtype` (enum: sha512_256, sha256, optional): The type of hash function used to create the proof, must be one of: sha512_256 or sha256.
-- `format` (enum: json, msgpack, optional): Configures whether the response object is JSON or MessagePack encoded. If not provided, defaults to JSON.
-
-### Return Object
-
-The method returns an object representing the proof of the specified transaction in a block. The object includes the following properties:
-
-- `hashtype` (string): The type of hash function used to create the proof, must be one of: sha512_256 or sha256.
-- `idx` (integer): Index of the transaction in the block's payset.
-- `proof` (string): Proof of transaction membership.
-- `stibhash` (string): Hash of SignedTxnInBlock for verifying the proof.
-- `treedepth` (integer): Represents the depth of the tree that is being proven, i.e. the number of edges from a leaf to the root.
-
-Please note that the structure of the returned object may change in different Algorand RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-gettransactions.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-gettransactions.md
deleted file mode 100644
index d4740f25..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-gettransactions.md
+++ /dev/null
@@ -1,95 +0,0 @@
----
-title: "getTransactions"
-slug: "rpc-algorand-gettransactions"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:04 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandIndexer, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_INDEXER });
-
-// Define the input parameters as a dictionary object
-const params = {
- address: 'ALGORAND_ADDRESS', // Optional: Only include transactions with this address in one of the transaction fields (string).
- addressRole: 'sender', // Optional: Combine with the address parameter to define what type of address to search for (enum: sender, receiver, freeze-target).
- afterTime: '2023-11-06T00:00:00Z', // Optional: Include results after the given time (RFC 3339 formatted string).
- applicationId: 123, // Optional: Application ID (integer).
- assetId: 456, // Optional: Asset ID (integer).
- beforeTime: '2023-11-07T00:00:00Z', // Optional: Include results before the given time (RFC 3339 formatted string).
- currencyGreaterThan: 100, // Optional: Results should have an amount greater than this value (number).
- currencyLessThan: 500, // Optional: Results should have an amount less than this value (number).
- excludeCloseTo: true, // Optional: Combine with address and address-role parameters to define what type of address to search for (boolean).
- limit: 100, // Optional: Maximum number of results to return (number).
- maxRound: 1000, // Optional: Include results at or before the specified max-round (number).
- minRound: 900, // Optional: Include results at or after the specified min-round (number).
- next: 'NEXT_PAGE_TOKEN', // Optional: The next page of results. Use the next token provided by the previous results (string).
- notePrefix: 'PREFIX_TEXT', // Optional: Specify a prefix that must be contained in the note field (string).
- rekeyTo: true, // Optional: Include results which include the rekey-to field (boolean).
- round: 1000, // Optional: Include results for the specified round (number).
- sigType: 'sig', // Optional: Filter results using the specified type of signature (enum: sig, msig, lsig).
- txType: 'pay', // Optional: Filter results by transaction type (enum: pay, keyreg, acfg, axfer, afrz, appl, stpf).
- txId: 'TRANSACTION_ID' // Optional: Lookup the specific transaction by ID (string).
-};
-
-// Search for transactions based on the specified parameters
-const transactions = await tatum.rpc.getTransactions(params);
-
-// Log the list of transactions that match the criteria
-console.log('Transactions:', transactions);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getTransactions` method allows you to search for transactions based on various criteria. Transactions can be filtered by address, address role, time, application ID, asset ID, currency amount, and more. By default, transactions are returned in chronological order from oldest to newest, but you can reverse the order using the `address` parameter.
-
-### Request Parameters
-
-The method requires the following parameters:
-
-- `address` (string, optional): Only include transactions with this address in one of the transaction fields.
-- `addressRole` (enum, optional): Combine with the address parameter to define what type of address to search for (sender, receiver, freeze-target).
-- `afterTime` (string, optional): Include results after the given time (RFC 3339 formatted string).
-- `applicationId` (integer, optional): Application ID for filtering transactions.
-- `assetId` (integer, optional): Asset ID for filtering transactions.
-- `beforeTime` (string, optional): Include results before the given time (RFC 3339 formatted string).
-- `currencyGreaterThan` (number, optional): Results should have an amount greater than this value.
-- `currencyLessThan` (number, optional): Results should have an amount less than this value.
-- `excludeCloseTo` (boolean, optional): Combine with address and address-role parameters to define what type of address to search for.
-- `limit` (number, optional): Maximum number of results to return.
-- `maxRound` (number, optional): Include results at or before the specified max-round.
-- `minRound` (number, optional): Include results at or after the specified min-round.
-- `next` (string, optional): The next page of results. Use the next token provided by the previous results.
-- `notePrefix` (string, optional): Specifies a prefix that must be contained in the note field.
-- `rekeyTo` (boolean, optional): Include results which include the rekey-to field.
-- `round` (number, optional): Include results for the specified round.
-- `sigType` (enum, optional): Filter results using the specified type of signature (sig, msig, lsig).
-- `txType` (enum, optional): Filter results by transaction type (pay, keyreg, acfg, axfer, afrz, appl, stpf).
-- `txId` (string, optional): Lookup the specific transaction by ID.
-
-### Return Object
-
-The method returns a list of transactions that match the specified criteria. Transactions include details such as transaction ID, sender address, receiver address, transaction type, and more. The order of results can be reversed based on the `address` parameter.
-
-Please note that the structure of the returned object may change in different RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-ishealthy.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-ishealthy.md
deleted file mode 100644
index 9bdfbfbf..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-ishealthy.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: "isHealthy"
-slug: "rpc-algorand-ishealthy"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:01 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandAlgod, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_ALGOD });
-
-// Retrieve health check status for the Algorand node
-const isHealthy = await tatum.rpc.isHealthy();
-
-// Log the health check status
-console.log('Algorand Health Check:', isHealthy);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `isHealthy` method allows you to check the health of the Algorand node.
-
-### Example Use Cases
-
-1. **Health Monitoring**: Developers can use this method to regularly monitor the health status of the Algorand node and ensure that it is functioning properly.
-
-### Request Parameters
-
-The `isHealthy` method does not require any parameters.
-
-### Return Object
-
-The method returns an empty object with a response code indicating the health status of the Algorand node.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-isready.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-isready.md
deleted file mode 100644
index 20e0a808..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-isready.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: "isReady"
-slug: "rpc-algorand-isready"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:03 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandAlgod, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_ALGOD });
-
-// Retrieve the health status of the Algorand node
-const readyStatus = await tatum.rpc.isReady();
-
-// Log the health status
-console.log('Algorand Node Ready:', readyStatus);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `isReady` method allows you to check the health status of the Algorand node and confirm if it is fully caught up.
-
-### Example Use Cases
-
-1. **Node Health Check**: Developers can use this method to check if the Algorand node is healthy and fully caught up, ensuring that it is ready to process requests.
-
-### Request Parameters
-
-The `isReady` method does not require any parameters.
-
-### Return Object
-
-The method returns a response indicating the health status of the Algorand node.
-
-Please note that the structure of the returned object may change in different Algorand RPC versions.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-simulatetransaction.md b/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-simulatetransaction.md
deleted file mode 100644
index 20e6b1bc..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-algorand/rpc-algorand-simulatetransaction.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-title: "simulateTransaction"
-slug: "rpc-algorand-simulatetransaction"
-excerpt: "Algorand RPC"
-hidden: false
-metadata:
- description: "Algorand RPC"
- image: []
- keywords: "algorand, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:40 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, AlgorandAlgod, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Algorand
-const tatum = await TatumSDK.init({ network: Network.ALGORAND_ALGOD });
-
-// Define the input parameters in a single object
-const params = {
- format: 'json', // Optional: Configures whether the response object is JSON or MessagePack encoded. If not provided, defaults to JSON.
-};
-
-// Define the request body object
-const requestBody = {
- // Specify the transactions to simulate, along with any other inputs.
- // Please refer to the Tatum SDK documentation for detailed information about the request body schema.
-};
-
-// Simulate the transaction or transaction group on the Algorand network
-const simulationResult = await tatum.rpc.simulateTransaction(params, requestBody);
-
-// Log the simulation result
-console.log('Algorand Transaction Simulation Result:', simulationResult);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `simulateTransaction` method allows you to simulate a raw transaction or transaction group as it would be evaluated on the Algorand network. The simulation will use blockchain state from the latest committed round.
-
-### Example Use Cases
-
-1. **Transaction Simulation**: Developers can use this method to test the validity and outcome of a transaction or transaction group before actually submitting it to the Algorand network. This can help avoid failed transactions and wasted resources.
-
-### Request Parameters
-
-The `simulateTransaction` method requires the following parameters:
-
-- `format` (enum: json, msgpack, optional): Configures whether the response object is JSON or MessagePack encoded. If not provided, defaults to JSON.
-
-### Request Body
-
-The `simulateTransaction` method requires a request body object. Please refer to the Tatum SDK documentation for detailed information about the request body schema.
-
-### Return Object
-
-The method returns an object representing the result of the simulated transaction or transaction group. Please note that the structure of the returned object may vary depending on the format specified in the request parameters and the Algorand RPC version.
-
-### Error Responses
-
-- `400`: Bad Request. The request was invalid or missing required parameters.
-- `401`: Invalid API Token. The API token used for authentication is invalid.
-- `500`: Internal Error. An unexpected error occurred on the server.
-- `503`: Service Temporarily Unavailable. The server is temporarily unable to handle the request.
-
-Please refer to the Tatum SDK documentation for more information about error responses.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon.md b/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon.md
deleted file mode 100644
index fade8f8d..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Bnb Beacon"
-slug: "rpc-bnb-beacon"
-excerpt: ""
-hidden: false
-createdAt: "Wed Mar 06 2024 10:35:18 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:39 GMT+0000 (Coordinated Universal Time)"
----
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-abcinfo.md b/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-abcinfo.md
deleted file mode 100644
index 688c31d2..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-abcinfo.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: "abcInfo"
-slug: "rpc-bnb-beacon-abcinfo"
-excerpt: "Bnb Beacon RPC"
-hidden: false
-metadata:
- description: "Bnb Beacon RPC"
- image: []
- keywords: "bnb-beacon, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:43 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Importing Tatum SDK for Beacon Chain
-import { TatumSDK, Network, Bnb } from '@tatumio/tatum';
-
-// Initializing SDK for Beacon Chain network
-const tatum = await TatumSDK.init({ network: Network.BNB });
-
-// Using the 'abciInfo' method to get information about the ABCI (Application Blockchain Interface) application
-const abciInfoData = await tatum.rpc.abciInfo();
-
-console.log(abciInfoData);
-
-// Destroying the Tatum SDK instance. This is necessary to stop any background jobs that the SDK may have started.
-await tatum.destroy();
-```
-
-### Overview
-
-The `abciInfo` method is utilized to retrieve information about the BNB Beacon Chain application.
-
-### Return Object
-
-The `abciInfo` method typically returns an object containing the details about the application. While the exact structure might vary, the return object may include the following fields:
-
-- `version` (string): The version of the application.
-- `lastBlockHeight` (string number): The height of the last block processed.
-- `lastBlockAppHash` (string number): The hash of the last block processed.
-
-(Note: The exact fields in the return object might vary based on the BNB Beacon Chain's implementation and version.)
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-abciquerry.md b/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-abciquerry.md
deleted file mode 100644
index aa6bc286..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-abciquerry.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: "abciQuerry"
-slug: "rpc-bnb-beacon-abciquerry"
-excerpt: "Bnb Beacon RPC"
-hidden: false
-metadata:
- description: "Bnb Beacon RPC"
- image: []
- keywords: "bnb-beacon, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:02 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-/// Importing Tatum SDK for Beacon Chain
-import { TatumSDK, Network, Bnb } from '@tatumio/tatum';
-
-// Initializing SDK for Beacon Chain network
-const tatum = await TatumSDK.init({ network: Network.BNB });
-
-// Defining query parameters for the 'abciQuery' method
-const queryParams = {
- path: 'YOUR_PATH_HERE',
- data: 'YOUR_DATA_HERE',
- height: 'YOUR_HEIGHT_VALUE',
- prove: YOUR_PROVE_BOOLEAN
-};
-
-// Using the 'abciQuery' method to query data from the ABCI application
-const abciQueryData = await tatum.rpc.abciQuery(queryParams);
-
-console.log(abciQueryData);
-
-// Destroying the Tatum SDK instance. This is necessary to stop any background jobs that the SDK may have started.
-await tatum.destroy();
-```
-
-### Overview
-
-The `abciQuery` method is used to query the BNB Beacon Chain application directly via ABCI. This provides a direct interface to the application layer, enabling specific data retrieval from the chain.
-
-### Parameters
-
-- `path` (string, required): The query path which corresponds to the type of data or information you want to retrieve. This is a required parameter and should follow a format like `"/a/b/c"`.
-- `data` (string, required): The data associated with the query. This is also a required parameter and is used to provide additional context or filters for the query.
-- `height` (string number, optional): The height at which to perform the query. If set to 0, it queries the latest data. This is an optional parameter.
-- `prove` (boolean, optional): If set to `true`, the response will include proofs of the transactions' inclusion in the block. This is also an optional parameter.
-
-### Return Object
-
-The `abciQuery` method returns an object with details about the queried data from the application layer. The exact structure and content depend on the query path and data, but the return object might typically include:
-
-- `response` (object): The response data from the ABCI query. It may contain fields like `key`, `value`, `height`, and `index`.
-
-(Note: The exact fields in the return object might vary based on the BNB Beacon Chain's implementation and version.)
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-block.md b/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-block.md
deleted file mode 100644
index 0cd579be..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-block.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: "block"
-slug: "rpc-bnb-beacon-block"
-excerpt: "Bnb Beacon RPC"
-hidden: false
-metadata:
- description: "Bnb Beacon RPC"
- image: []
- keywords: "bnb-beacon, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:44 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Importing Tatum SDK for Beacon Chain
-import { TatumSDK, Network, Bnb } from '@tatumio/tatum';
-
-// Initializing SDK for Beacon Chain network
-const tatum = await TatumSDK.init({ network: Network.BNB });
-
-// Defining the parameters for fetching a specific block from the blockchain
-const blockParams = {
- height: YOUR_HEIGHT_VALUE
-};
-
-// Fetching the block data using the 'block' method and the defined parameters
-const blockData = await tatum.rpc.block(blockParams);
-
-console.log(blockData);
-
-// Destroying the Tatum SDK instance to stop any background jobs and free up resources
-await tatum.destroy();
-
-```
-
-### Overview
-
-The `block` method is utilized to fetch block details for a specific height from the BNB Beacon Chain. Without specific block `height`, method returns last known block.
-
-### Parameters
-
-- `height` (string number, optional): The height of the block to be fetched. This is a optional parameter.
-
-### Return Object
-
-The `block` method returns an object containing the details of the block at the specified height. While the exact structure might vary, the return object may include fields like:
-
-- `header` (object): Information about the block header.
-- `transactions` (array): List of transactions within the block.
-- `blockHash` (string): Hash of the block.
-- ... and other details depending on the BNB Beacon Chain's implementation and version.
-
-(Note: The exact fields in the return object might vary based on the BNB Beacon Chain's implementation and version.)
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-blockchain.md b/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-blockchain.md
deleted file mode 100644
index 0ac78d60..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-blockchain.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: "blockchain"
-slug: "rpc-bnb-beacon-blockchain"
-excerpt: "Bnb Beacon RPC"
-hidden: false
-metadata:
- description: "Bnb Beacon RPC"
- image: []
- keywords: "bnb-beacon, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:03 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Importing Tatum SDK for Beacon Chain
-import { TatumSDK, Network, Bnb } from '@tatumio/tatum';
-
-// Initializing SDK for Beacon Chain network
-const tatum = await TatumSDK.init({ network: Network.BNB });
-
-// Defining the block height range parameters for the query (optional)
-const blockchainParams = {
- minHeight: 'YOUR_MIN_HEIGHT_VALUE', // Optional: e.g., "12345"
- maxHeight: 'YOUR_MAX_HEIGHT_VALUE' // Optional: e.g., "67890"
-};
-
-// Fetching blockchain data within the specified block height range
-const blockchainData = await tatum.rpc.blockchain(blockchainParams);
-console.log(blockchainData);
-
-// Destroy Tatum SDK - needed for stopping background jobs
-await tatum.destroy();
-```
-
-### Overview
-
-The `blockchain` method is utilized to fetch blockchain data from the BNB Beacon Chain. Users can optionally specify a block height range to filter the results.
-
-### Parameters
-
-- `minHeight` (string, optional): The minimum block height from which to fetch the data. If not provided, there is no lower limit.
-- `maxHeight` (string, optional): The maximum block height up to which to fetch the data. If not provided, there is no upper limit.
-
-### Return Object
-
-The `blockchain` method returns an object that provides a snapshot of the blockchain data within the specified block height range. The exact structure of the return object can vary, but it generally includes information related to blocks, transactions, and possibly other blockchain-specific details.
-
-(Note: The exact fields in the return object can differ based on the BNB Beacon Chain's implementation and version.)
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-blockresults.md b/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-blockresults.md
deleted file mode 100644
index 7959b84a..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-blockresults.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: "blockResults"
-slug: "rpc-bnb-beacon-blockresults"
-excerpt: "Bnb Beacon RPC"
-hidden: false
-metadata:
- description: "Bnb Beacon RPC"
- image: []
- keywords: "bnb-beacon, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:05 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Importing Tatum SDK for Beacon Chain
-import { TatumSDK, Network, Bnb } from '@tatumio/tatum';
-
-// Initializing SDK for Beacon Chain network
-const tatum = await TatumSDK.init({ network: Network.BNB });
-
-// Defining the block height parameter for the query
-const blockParams = {
- height: YOUR_HEIGHT_VALUE
-};
-
-// Fetching and logging the block result data from the BNB Beacon Chain
-const blockResultData = await tatum.rpc.blockResult(blockParams);
-console.log(blockResultData);
-
-// Cleaning up resources used by Tatum SDK
-await tatum.destroy();
-```
-
-### Overview
-
-The `blockResult` method is used to fetch the results of transactions in a specified block on the BNB Beacon Chain.
-
-### Parameters
-
-- `height`: (string number, optional) The height of the block you are interested in. If not specified, it will default to the latest block.
-
-### Return Object
-
-The method returns an object containing detailed information about the transactions in the specified block. The exact structure of the returned object can depend on the BNB Beacon Chain's implementation and version. Some of the fields you might see include:
-
-- `block_meta` (object): Metadata about the block.
-- `block` (object): Detailed information about the block itself.
-- `results` (object): Results of transactions included in the block.
-- `validator_updates` (array): Information about any validator updates.
-- `consensus_param_updates` (object): Information about any updates to consensus parameters.
-
-(Note: The exact fields in the return object can differ based on the BNB Beacon Chain's implementation and version.)
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-broadcasttxasync.md b/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-broadcasttxasync.md
deleted file mode 100644
index 48472d56..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-broadcasttxasync.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: "broadcastTxAsync"
-slug: "rpc-bnb-beacon-broadcasttxasync"
-excerpt: "Bnb Beacon RPC"
-hidden: false
-metadata:
- description: "Bnb Beacon RPC"
- image: []
- keywords: "bnb-beacon, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:42 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Importing Tatum SDK for Beacon Chain
-import { TatumSDK, Network, Bnb } from '@tatumio/tatum';
-
-// Initializing SDK for Beacon Chain network
-const tatum = await TatumSDK.init({ network: Network.BNB });
-
-// Defining the transaction to broadcast
-const signedTx = 'SIGNED_TRANSACTION_STRING'; // Replace with your signed transaction string
-
-// Broadcasting the transaction asynchronously
-const txResponse = await tatum.rpc.broadcastTxAsync({ tx: signedTx });
-console.log(txResponse);
-
-// Destroy Tatum SDK - needed for stopping background jobs
-await tatum.destroy();
-```
-
-### Overview
-
-The `broadcastTxAsync` method is used to broadcast a signed transaction to the BNB Beacon Chain asynchronously.
-
-### Parameters
-
-- `tx` (string, required): The signed transaction string that you want to broadcast.
-
-### Return Object
-
-The method returns a promise that resolves to a JSON-RPC response containing information about the broadcasted transaction. The response includes the following fields:
-
-- `code` (string): The status code of the transaction.
- - Example: `0`
-
-- `data` (string): Additional data related to the transaction.
- - Example: `7B226F726465725F6964223A22383133453439333946313536374232313937303446464332414434444635384244453031303837392D3438227D`
-
-- `hash` (string): The hash of the broadcasted transaction.
- - Example: `008EA3C57B15E34B045F69DCEB2A5589B979B2B58BA282C15DF2AEA8B441AB6B`
-
-- `log` (string): Transaction log information.
- - Example: `Msg 0:`
-
-(Note: The exact response structure may vary depending on the BNB Beacon Chain's implementation and version.)
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-broadcasttxcommit.md b/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-broadcasttxcommit.md
deleted file mode 100644
index d5fc7706..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-broadcasttxcommit.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: "broadcastTxCommit"
-slug: "rpc-bnb-beacon-broadcasttxcommit"
-excerpt: "Bnb Beacon RPC"
-hidden: false
-metadata:
- description: "Bnb Beacon RPC"
- image: []
- keywords: "bnb-beacon, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:40 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Importing Tatum SDK for Beacon Chain
-import { TatumSDK, Network, Bnb } from '@tatumio/tatum';
-
-// Initializing SDK for Beacon Chain network
-const tatum = await TatumSDK.init({ network: Network.BNB });
-
-// Defining the signed transaction string to broadcast
-const signedTx = 'SIGNED_TRANSACTION_STRING'; // Replace with your signed transaction string
-
-// Broadcasting the transaction and waiting for commit
-const commitResponse = await tatum.rpc.broadcastTxCommit({ tx: signedTx });
-console.log(commitResponse);
-
-// Destroy Tatum SDK - needed for stopping background jobs
-await tatum.destroy();
-```
-
-### Overview
-
-The `broadcastTxCommit` method is used to broadcast a signed transaction to the BNB beacon chain and wait for it to be included in a block (commit). This method provides information about the committed transaction, including its status, block height, and other relevant data.
-
-### Parameters
-
-- `tx` (string, required): The signed transaction string that you want to broadcast.
-
-### Return Object
-
-The method returns a response containing information about the committed transaction. The response includes the following fields:
-
-- `height` (string): The block height at which the transaction was included.
- - Example: `7734637`
-
-- `hash` (string): The hash of the committed transaction.
- - Example: `008EA3C57B15E34B045F69DCEB2A5589B979B2B58BA282C15DF2AEA8B441AB6B`
-
-- `check_tx` (object): Additional information related to the check transaction phase.
- - Example: `{ }`
-
-- `deliver_tx` (object): Additional information related to the deliver transaction phase.
-
-(Note: The exact structure of the response may vary based on the BNB beacon chain's implementation and version.)
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-broadcasttxsync.md b/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-broadcasttxsync.md
deleted file mode 100644
index 3440afb8..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-broadcasttxsync.md
+++ /dev/null
@@ -1,60 +0,0 @@
----
-title: "broadcastTxSync"
-slug: "rpc-bnb-beacon-broadcasttxsync"
-excerpt: "Bnb Beacon RPC"
-hidden: false
-metadata:
- description: "Bnb Beacon RPC"
- image: []
- keywords: "bnb-beacon, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:05 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Importing Tatum SDK for Beacon Chain
-import { TatumSDK, Network, Bnb } from '@tatumio/tatum';
-
-// Initializing SDK for Beacon Chain network
-const tatum = await TatumSDK.init({ network: Network.BNB });
-
-// Defining the signed transaction string to broadcast
-const signedTx = 'SIGNED_TRANSACTION_STRING'; // Replace with your signed transaction string
-
-// Broadcasting the transaction synchronously
-const syncResponse = await tatum.rpc.broadcastTxSync({ tx: signedTx });
-console.log(syncResponse);
-
-// Destroy Tatum SDK - needed for stopping background jobs
-await tatum.destroy();
-```
-
-### Overview
-
-The `broadcastTxSync` method is used to broadcast a signed transaction to the BNB beacon chain synchronously.
-
-### Parameters
-
-- `tx` (string, required): The signed transaction string that you want to broadcast.
-
-(Note: The `tx` parameter should contain the signed transaction in the appropriate format for the BNB beacon chain.)
-
-### Return Object
-
-This method returns a JSON-RPC response containing information about the broadcasted transaction. The response includes the following fields:
-
-- `code` (string): The status code of the transaction.
-- `data` (string): Additional data related to the transaction.
-- `hash` (string): The hash of the broadcasted transaction.
-- `log` (string): Transaction log information.
-
-(Note: The exact structure of the response may vary based on the BNB beacon chain's implementation and version.)
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-commit.md b/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-commit.md
deleted file mode 100644
index 1c625886..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-commit.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: "commit"
-slug: "rpc-bnb-beacon-commit"
-excerpt: "Bnb Beacon RPC"
-hidden: false
-metadata:
- description: "Bnb Beacon RPC"
- image: []
- keywords: "bnb-beacon, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:06 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Importing Tatum SDK for Beacon Chain
-import { TatumSDK, Network, Bnb } from '@tatumio/tatum';
-
-// Initializing SDK for Beacon Chain network
-const tatum = await TatumSDK.init({ network: Network.BNB });
-
-// Defining the block height parameter for the query
-const commitParams = {
- height: 'YOUR_HEIGHT_VALUE', // e.g., "12345"
-};
-
-// Fetching commit information for the specified block height
-const commitData = await tatum.rpc.commit(commitParams);
-console.log(commitData);
-
-// Destroy Tatum SDK - needed for stopping background jobs
-await tatum.destroy();
-```
-
-### Overview
-
-The `commit` method is used to retrieve the commit information of a specific block in the BNB Beacon Chain by providing the block height. If no height is provided, it will fetch commit information regarding the latest block.
-
-### Parameters
-
-- `height` (string, optional): The height of the block for which you want to retrieve commit information.
-
-### Return Object
-
-This method returns an object containing commit information for the specified block, including details like commit hash, precommit validators, and more.
-
-(Note: The exact fields in the return object might vary based on the BNB Beacon Chain's implementation and version.)
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-genesis.md b/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-genesis.md
deleted file mode 100644
index 54fcf872..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-genesis.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: "genesis"
-slug: "rpc-bnb-beacon-genesis"
-excerpt: "Bnb Beacon RPC"
-hidden: false
-metadata:
- description: "Bnb Beacon RPC"
- image: []
- keywords: "bnb-beacon, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:04 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-```typescript
-// Importing Tatum SDK for Beacon Chain
-import { TatumSDK, Network, Bnb } from '@tatumio/tatum';
-
-// Initializing SDK for Beacon Chain network
-const tatum = await TatumSDK.init({ network: Network.BNB });
-
-// Retrieve the genesis information
-const genesisInfo = await tatum.rpc.genesis();
-console.log(genesisInfo);
-
-// Destroy Tatum SDK - needed for stopping background jobs
-await tatum.destroy();
-```
-
-### Overview
-
-The `genesis` method is used to retrieve the genesis information of the Beacon Chain.
-
-### Parameters
-
-This method does not require any parameters.
-
-### Return Object (Required)
-
-The method returns a Promise that resolves to a JSON-RPC response containing the following field:
-
-- `genesis` (object): General information about the Beacon Chain genesis.
-
-(Note: The exact fields in the return object might vary based on the BNB Beacon Chain's implementation and version.)
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-health.md b/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-health.md
deleted file mode 100644
index 0debfa37..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-health.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: "health"
-slug: "rpc-bnb-beacon-health"
-excerpt: "Bnb Beacon RPC"
-hidden: false
-metadata:
- description: "Bnb Beacon RPC"
- image: []
- keywords: "bnb-beacon, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:03 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-```typescript
-// Importing Tatum SDK for Beacon Chain
-import { TatumSDK, Network, Bnb } from '@tatumio/tatum';
-
-// Initializing SDK for Beacon Chain network
-const tatum = await TatumSDK.init({ network: Network.BNB });
-
-// Check the health status
-const healthStatus = await tatum.rpc.health();
-console.log(healthStatus);
-
-// Destroy Tatum SDK - needed for stopping background jobs
-await tatum.destroy();
-```
-
-### Overview
-
-The `health` method is used to check the health status of the Beacon Chain.
-
-### Parameters
-
-This method does not require any parameters.
-
-### Return Object (Required)
-
-The method returns a Promise that resolves to a JSON-RPC response containing information about the health status of the Beacon Chain.
-
-(Note: The exact structure of the transaction objects and response may vary based on the BNB beacon chain's implementation and version.)
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-netinfo.md b/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-netinfo.md
deleted file mode 100644
index 48e12ffe..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-netinfo.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: "netInfo"
-slug: "rpc-bnb-beacon-netinfo"
-excerpt: "Bnb Beacon RPC"
-hidden: false
-metadata:
- description: "Bnb Beacon RPC"
- image: []
- keywords: "bnb-beacon, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:05 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-```typescript
-// Importing Tatum SDK for Beacon Chain
-import { TatumSDK, Network, Bnb } from '@tatumio/tatum';
-
-// Initializing SDK for Beacon Chain network
-const tatum = await TatumSDK.init({ network: Network.BEACON_CHAIN });
-
-// Retrieve network information
-const networkInfo = await tatum.rpc.netInfo();
-console.log(networkInfo);
-
-// Destroy Tatum SDK - needed for stopping background jobs
-await tatum.destroy();
-```
-
-### Overview
-
-The `netInfo` method is used to retrieve network information from the Beacon Chain.
-
-### Parameters
-
-This method does not require any parameters.
-
-### Return Object
-
-The method returns a Promise that resolves to a JSON-RPC response containing the following fields:
-
-- `listening` (boolean): Indicates whether the BNB Beacon Chain node is currently listening for incoming connections. If it is listening, the value will be `true`, otherwise, it will be `false`.
-
-- `listeners` (array): An array of listener objects. Listener objects typically represent information about nodes or entities that are actively connected to the BNB Beacon Chain node, such as peers or clients.
-
-- `n_peers` (number): Represents the number of peers that the BNB Beacon Chain node is currently connected to. It provides a count of how many other nodes or entities the node is actively communicating with.
-
-- `peers` (array): An array of peer objects. Peer objects typically represent information about the peers or other nodes that the BNB Beacon Chain node is connected to. It may include details about these peers, such as their addresses, identities, or status.
-
-(Note: The exact fields in the return object might vary based on the BNB Beacon Chain's implementation and version.)
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-numunconfirmedtxs.md b/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-numunconfirmedtxs.md
deleted file mode 100644
index 9285b92d..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-numunconfirmedtxs.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: "numUnconfirmedTxs"
-slug: "rpc-bnb-beacon-numunconfirmedtxs"
-excerpt: "Bnb Beacon RPC"
-hidden: false
-metadata:
- description: "Bnb Beacon RPC"
- image: []
- keywords: "bnb-beacon, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:02 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-```typescript
-// Importing Tatum SDK for BNB Beacon Chain
-import { TatumSDK, Network, Bnb } from '@tatumio/tatum';
-
-// Initializing SDK for BNB Beacon Chain network
-const tatum = await TatumSDK.init({ network: Network.BNB });
-
-// Retrieve the number of unconfirmed transactions
-const numUnconfirmedTxs = await tatum.rpc.numUnconfirmedTxs();
-console.log(numUnconfirmedTxs);
-
-// Destroy Tatum SDK - needed for stopping background jobs
-await tatum.destroy();
-```
-
-### Overview
-
-The `numUnconfirmedTxs` method is used to retrieve the number of unconfirmed transactions in the BNB Beacon Chain.
-
-### Parameters
-
-This method does not require any parameters.
-
-### Return Object
-
-The method returns a Promise that resolves to a JSON-RPC response containing the following fields:
-
-- `n_txs` (string): The number of unconfirmed transactions. Example: `0`
-- `total` (string): The total value associated with unconfirmed transactions. Example: `0`
-- `total_bytes` (string): The total size in bytes of unconfirmed transactions. Example: `0`
-
-(Note: The exact fields in the return object might vary based on the BNB Beacon Chain's implementation and version.)
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-status.md b/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-status.md
deleted file mode 100644
index 03c49f62..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-status.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: "status"
-slug: "rpc-bnb-beacon-status"
-excerpt: "Bnb Beacon RPC"
-hidden: false
-metadata:
- description: "Bnb Beacon RPC"
- image: []
- keywords: "bnb-beacon, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:06 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Importing Tatum SDK for Beacon Chain
-import { TatumSDK, Network, Bnb } from '@tatumio/tatum';
-
-// Initializing SDK for Beacon Chain network
-const tatum = await TatumSDK.init({ network: Network.BNB });
-
-// Fetching and logging the status of the Beacon Chain
-const statusData = await tatum.rpc.status();
-console.log(statusData);
-
-// Cleaning up resources used by Tatum SDK
-await tatum.destroy();
-```
-
-### Overview
-
-The `status` method is used to obtain information about the current status of the BNB Beacon Chain.
-
-### Return Object
-
-The `status` method provides an object that contains details about the current state of the chain. The returned structure might differ, but commonly includes these fields:
-
-- `nodeInfo` (object): Details about the node, like its ID, listen address, and version.
-- `syncInfo` (object): Information about the node's synchronization status, like the latest block hash, height, and timestamp.
-- `validator_info` (object): Information about the node as a validator, such as its address and voting power.
-
-(Note: The exact fields in the return object can differ based on the BNB Beacon Chain's implementation and version.)
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-tx.md b/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-tx.md
deleted file mode 100644
index de0d4cf7..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-tx.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: "tx"
-slug: "rpc-bnb-beacon-tx"
-excerpt: "Bnb Beacon RPC"
-hidden: false
-metadata:
- description: "Bnb Beacon RPC"
- image: []
- keywords: "bnb-beacon, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:37 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Importing Tatum SDK for Beacon Chain
-import { TatumSDK, Network, Bnb } from '@tatumio/tatum';
-
-// Initializing SDK for Beacon Chain network
-const tatum = await TatumSDK.init({ network: Network.BNB });
-
-// Defining the transaction hash parameter for the query
-const txParams = {
- hash: 'YOUR_TRANSACTION_HASH', // e.g., "0x1234abcd..."
-};
-
-// Fetching transaction information by hash
-const txData = await tatum.rpc.tx(txParams);
-console.log(txData);
-
-// Destroy Tatum SDK - needed for stopping background jobs
-await tatum.destroy();
-```
-
-### Overview
-
-The `tx` method is used to retrieve detailed information about a specific transaction on the BNB Beacon Chain using the transaction's hash.
-
-### Parameters
-
-- `hash` (string, required): The hash of the transaction you want to retrieve information about.
-
-### Return Object
-
-This method returns an object containing detailed information about the specified transaction, including the transaction's hash, block height, and other relevant data.
-
-(Note: The exact fields in the return object might vary based on the BNB Beacon Chain's implementation and version.)
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-txsearch.md b/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-txsearch.md
deleted file mode 100644
index c0cbe548..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-txsearch.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: "txSearch"
-slug: "rpc-bnb-beacon-txsearch"
-excerpt: "Bnb Beacon RPC"
-hidden: false
-metadata:
- description: "Bnb Beacon RPC"
- image: []
- keywords: "bnb-beacon, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:06 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Importing Tatum SDK for Beacon Chain
-import { TatumSDK, Network, Bnb } from '@tatumio/tatum';
-
-// Initializing SDK for Beacon Chain network
-const tatum = await TatumSDK.init({ network: Network.BNB });
-
-// Defining the search parameters
-const searchParams = {
- query: 'QUERY_STRING', // Replace with your query string (Required)
- prove: true, // Include proofs of transaction inclusion in the block (true/false) (Required)
- page: '1', // Page number (1-based) (Optional)
- per_page: '10' // Number of entries per page (max: 100) (Optional)
-};
-
-// Searching for transactions
-const searchResults = await tatum.rpc.txSearch(searchParams);
-console.log(searchResults);
-
-// Destroy Tatum SDK - needed for stopping background jobs
-await tatum.destroy();
-```
-
-### Overview
-
-The `txSearch` method is used to search for transactions on the BNB beacon chain that match specific search criteria.
-
-### Parameters
-
-- `query` (string, Required): The query string used to search for transactions.
-- `prove` (boolean, Required): Include proofs of the transaction's inclusion in the block (true/false).
-- `page` (string number, Optional): Page number for paginating results (1-based).
-- `per_page` (string number, Optional): Number of entries per page (max: 100).
-
-### Return Object
-
-The method returns a JSON-RPC response containing information about the matching transactions. The response includes the following fields:
-
-- `total_count` (string, Required): The total count of matching transactions.
- - Example: `2`
-- `txs` (array, Required): An array of transaction objects.
- - Example: `[ ]`
-
-(Note: The exact structure of the transaction objects and response may vary based on the BNB beacon chain's implementation and version.)
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-unconfirmedtxs.md b/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-unconfirmedtxs.md
deleted file mode 100644
index 62524c99..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-unconfirmedtxs.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: "unconfirmedTxs"
-slug: "rpc-bnb-beacon-unconfirmedtxs"
-excerpt: "Bnb Beacon RPC"
-hidden: false
-metadata:
- description: "Bnb Beacon RPC"
- image: []
- keywords: "bnb-beacon, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:37 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-```typescript
-// Importing Tatum SDK for Beacon Chain
-import { TatumSDK, Network, Bnb } from '@tatumio/tatum';
-
-// Initializing SDK for Beacon Chain network
-const tatum = await TatumSDK.init({ network: Network.BNB });
-
-// Define the limit for unconfirmed transactions
-const limit = { limit : '10' };
-
-// Retrieve unconfirmed transactions
-const unconfirmedTxs = await tatum.rpc.unconfirmedTxs(limit);
-console.log(unconfirmedTxs);
-
-// Destroy Tatum SDK - needed for stopping background jobs
-await tatum.destroy();
-```
-
-### Overview
-
-The `unconfirmedTxs` method is used to retrieve unconfirmed transactions from the BNB Beacon Chain.
-
-### Parameters
-
-- `limit` (string, optional): The maximum number of unconfirmed transactions to retrieve.
-
-### Return Object (Required)
-
-- `n_txs` (number): The number of unconfirmed transactions.
-- `total` (number): The total value associated with unconfirmed transactions.
-- `total_bytes` (number): The total size in bytes of unconfirmed transactions.
-- `txs` (array): An array of unconfirmed transaction objects.
-
-(Note: The exact structure of the transaction objects and response may vary based on the BNB beacon chain's implementation and version.)
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-validators.md b/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-validators.md
deleted file mode 100644
index c650366a..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-bnb-beacon/rpc-bnb-beacon-validators.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: "validators"
-slug: "rpc-bnb-beacon-validators"
-excerpt: "Bnb Beacon RPC"
-hidden: false
-metadata:
- description: "Bnb Beacon RPC"
- image: []
- keywords: "bnb-beacon, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:03 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-```typescript
-// Importing Tatum SDK for Beacon Chain
-import { TatumSDK, Network, Bnb } from '@tatumio/tatum';
-
-// Initializing SDK for Beacon Chain network
-const tatum = await TatumSDK.init({ network: Network.BNB });
-
-// Optional parameters
-const params = {
- height : 'your-height',
- page : 'your-page',
- perPage : 'entries-per-page'
-};
-// Retrieve the current validator set
-const validatorSet = await tatum.rpc.validators(params);
-console.log(validatorSet);
-
-// Destroy Tatum SDK - needed for stopping background jobs
-await tatum.destroy();
-```
-
-### Overview
-
-The `validators` method is used to retrieve the current validator set on the BNB Beacon Chain.
-
-### Parameters
-
-- `height` (string, optional): Height to return. If no height is provided, it will fetch the validator set corresponding to the latest block.
-- `page` (string, optional): Page number (1-based).
-- `perPage` (string, optional): Number of entries per page (max: 100).
-
-### Return Object (Required)
-
-- `block_height` (string): Example: `55`
-- `validators` (array): An array of validator objects representing the validators in the set. Example: `[]`
-
-(Note: The exact structure of the validator objects and response may vary based on the BNB Beacon Chain's implementation and version.)
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-cardano.md b/v1.0/RPC Nodes/rpc-others/rpc-cardano.md
deleted file mode 100644
index 40c9eaee..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-cardano.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Cardano"
-slug: "rpc-cardano"
-excerpt: ""
-hidden: false
-createdAt: "Wed Mar 06 2024 10:35:18 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:40 GMT+0000 (Coordinated Universal Time)"
----
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-constructionmetadata.md b/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-constructionmetadata.md
deleted file mode 100644
index 3cf565be..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-constructionmetadata.md
+++ /dev/null
@@ -1,90 +0,0 @@
----
-title: "constructionMetadata"
-slug: "rpc-cardano-constructionmetadata"
-excerpt: "Cardano RPC"
-hidden: false
-metadata:
- description: "Cardano RPC"
- image: []
- keywords: "cardano, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:40 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, CardanoRosetta, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Cardano
-const tatum = await TatumSDK.init({ network: Network.CARDANO_ROSETTA });
-
-// Define the input parameters in a single object
-const params = {
- networkIdentifier: {
- blockchain: 'CARDANO', // string, required
- network: 'NETWORK_NAME', // string, required
- subNetworkIdentifier: {
- network: 'SUB_NETWORK_NAME', // string (optional)
- metadata: {
- [key: string]: any, // object (optional)
- },
- },
- },
- options: {
- // Optional object
- },
- publicKeys: [
- {
- hexBytes: 'PUBLIC_KEY_HEX_BYTES', // Required: Specifies the hexadecimal representation of the staking credential .
- curveType: 'SECP256K1', // Required: Specifies the curve type for the staking credential .]
- },
- ]
-};
-
-// Retrieve metadata for transaction construction on the Cardano network
-const metadata = await tatum.rpc.constructionMetadata(params);
-
-// Log the metadata
-console.log('Cardano Transaction Construction Metadata:', metadata);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `constructionMetadata` method allows you to retrieve metadata required to construct a transaction for a specific network.
-
-### Example Use Cases
-
-1. **Metadata Retrieval**: Developers can use this method along with the `constructionPreprocess` endpoint to retrieve metadata required for transaction construction in an offline environment.
-
-### Request Parameters
-
-The `constructionMetadata` method requires the following parameters:
-
-- `networkIdentifier` (object, required): An object containing information about the blockchain network.
- - `blockchain` (string, required): The blockchain identifier, which should be set to `CARDANO` for Cardano.
- - `network` (string, required): The network name for Cardano.
- - `subNetworkIdentifier` (object, optional): An optional sub-network identifier object.
- - `network` (string, required): The name of the sub-network within Cardano.
- - `metadata` (object, optional): Metadata associated with the sub-network.
-- `options` (object, optional): Some blockchains require different metadata for different types of transaction construction (ex: delegation versus a transfer). Instead of requiring a blockchain node to return all possible types of metadata for construction (which may require multiple node fetches), the client can populate an options object to limit the metadata returned to only the subset required.
-- `publicKey` (object, required): PublicKey contains a public key byte array for a particular CurveType encoded in hex. Note that there is no PrivateKey struct as this is NEVER the concern of an implementation.
- - `hexBytes` (string, required): The hexadecimal representation of the public key.
- - `curveType` (string, enum, required): The type of cryptographic curve associated with the public key (Choose from: secp256k1, secp256k1_bip340, secp256r1, edwards25519, tweedle, pallas).
-
-### Return Object
-
-The method returns an object representing the metadata required to construct a transaction for a specific network.
-
-Structure and behavior of this method may vary with different versions of the Cardano service. Always refer to the documentation specific to the version you are using for the most accurate information.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-constructionpayloads.md b/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-constructionpayloads.md
deleted file mode 100644
index 5fdada5a..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-constructionpayloads.md
+++ /dev/null
@@ -1,167 +0,0 @@
----
-title: "constructionPayloads"
-slug: "rpc-cardano-constructionpayloads"
-excerpt: "Cardano RPC"
-hidden: false
-metadata:
- description: "Cardano RPC"
- image: []
- keywords: "cardano, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:02 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, CardanoRosetta, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Cardano
-const tatum = await TatumSDK.init({ network: Network.CARDANO_ROSETTA });
-
-// Define the input parameters in a single object
-const params = {
- networkIdentifier: {
- blockchain: 'CARDANO', // Required: Specifies the blockchain .
- network: 'MAINNET', // Required: Specifies the network name .
- subNetworkIdentifier: {
- network: 'SUB_NETWORK_NAME', // Optional: Specifies the sub-network name .
- metadata: {
- KEY: 'VALUE', // Optional: Specify metadata .
- },
- },
- },
- operations: [
- {
- operation_identifier: {
- index: 1, // Required: Specifies the operation index (number).
- network_index: 0, // Optional: Specifies the network index (number).
- },
- related_operations: [
- {
- index: 2, // Optional: Specifies the related operation index (number).
- network_index: 1, // Optional: Specifies the related network index (number).
- },
- ],
- type: 'OPERATION_TYPE', // Required: Specifies the operation type.
- status: 'OPERATION_STATUS', // Optional: Specifies the operation status .
- account: {
- address: 'ACCOUNT_ADDRESS', // Required: Specifies the account address .
- sub_account: {
- address: 'SUB_ACCOUNT_ADDRESS', // Optional: Specifies the sub-account address .
- metadata: {
- // Optional metadata object for the sub-account
- },
- },
- metadata: {
- // Optional metadata object for the account
- },
- },
- amount: {
- value: 'AMOUNT_VALUE', // Required: Specifies the amount value (string).
- currency: {
- symbol: 'CURRENCY_SYMBOL', // Required: Specifies the currency symbol .
- decimals: 6, // Required: Specifies the currency decimals (number).
- metadata: {
- // Optional metadata for amount object
- },
- },
- metadata: {
- // Optional: Specify metadata here only if applicable.
- },
- },
- coin_change: {
- coin_identifier: {
- identifier: 'COIN_IDENTIFIER', // Required: uniquely identifies a Coin.
- },
- coin_action: 'coin_created', // Required
- },
- metadata: {
- // Optional: Specify operations metadata only if applicable.
- }
- },
- ],
- metadata: {
- // Optional metadata for constructionPayloads
- },
- publicKeys: [
- {
- hexBytes: 'PUBLIC_KEY_HEX_BYTES', // Required: Specifies the hexadecimal representation of the staking credential .
- curveType: 'SECP256K1', // Required: Specifies the curve type for the staking credential .]
- },
- ]
-};
-
-// Generate an unsigned transaction and signing payloads
-const constructionPayloads = await tatum.constructionPayloads(params);
-
-// Log the construction payloads
-console.log('Construction Payloads:', constructionPayloads);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `constructionPayloads` contains the network, a slice of operations, and arbitrary metadata that was returned by the call to `constructionMetadata`. Optionally, the request can also include an array of publicKeys associated with the AccountIdentifiers returned in `constructionPreprocess` response.
-
-### Example Use Cases
-
-1. **Transaction Construction**: Developers can use this method to construct an unsigned transaction that specifies the intent of the transaction but not all possible effects. The generated payloads can be signed by the specified account identifiers to complete the transaction.
-
-### Request Parameters
-
-The `constructionPayloads` method requires the following parameters:
-
-- `networkIdentifier` (object, required): An object containing information about the blockchain network.
- - `blockchain` (string, required): The blockchain identifier, which should be set to `CARDANO` for Cardano.
- - `network` (string, required): The network name for Cardano.
- - `subNetworkIdentifier` (object, optional): An optional sub-network identifier object.
- - `network` (string, required): The name of the sub-network within Cardano.
- - `metadata` (object, optional): Metadata associated with the sub-network.
-- `operations` (array of objects, required): An array of operation objects, where each object represents a transaction to be included in the Cardano transaction.
- - `operation_identifier` (object, required): An object containing an index that uniquely identifies the operation.
- - `index` (number, required): The index of the operation.
- - `network_index` (number, optional): The network-specific index of the operation.
- - `related_operations` (array of objects, optional): An array of related operation identifiers if applicable.
- - `index` (number, optional): The index of the related operation.
- - `network_index` (number, optional): The network-specific index of the related operation.
- - `type` (string, required): The type of the operation (e.g., "TRANSFER").
- - `status` (string, optional): The status of the operation (e.g., "SUCCESS").
- - `account` (object, required): An object containing information about the account.
- - `address` (string, required): The Cardano account address associated with the operation.
- - `sub_account` (object, optional): An optional sub-account object.
- - `address` (string, optional): The sub-account address.
- - `metadata` (object, optional): An optional metadata object for the sub-account. If the SubAccount address is not sufficient to uniquely specify a SubAccount, any other identifying information can be stored here. It is important to note that two SubAccounts with identical addresses but differing metadata will not be considered equal by clients.
- - `metadata` (object, optional): An optional metadata object for the account. Blockchains that utilize a username model (where the address is not a derivative of a cryptographic public key) should specify the public key(s) owned by the address in metadata.
- - `amount` (object, required): An object containing information about the transaction amount.
- - `value` (string, required): The value of the transaction amount.
- - `currency` (object, required): An object specifying the currency details.
- - `symbol` (string, required): The symbol or code of the currency.
- - `decimals` (number, required): The number of decimal places for the currency.
- - `metadata` (object, optional): Any additional information related to the currency itself. For example, it would be useful to populate this object with the contract address of an ERC-20 token.
- - `metadata` (object, optional): metadata object for the amount.
- - `coin_change` (object, required): An object containing information about coin changes in the operation.
- - `coin_identifier` (object, required): An object containing a coin identifier.
- - `identifier` (string, required): Identifier should be populated with a globally unique identifier of a Coin. In Bitcoin, this identifier would be transaction_hash:index..
- - `coin_action` (string, required): CoinActions are different state changes that a Coin can undergo. When a Coin is created, it is coin_created. When a Coin is spent, it is coin_spent. It is assumed that a single Coin cannot be created or spent more than once. (e.g., 'coin_created' | 'coin_spent').
- - `metadata` (object, optional): An optional metadata object for the operation, including withdrawal, deposit, refund, staking credential, pool key hash, epoch, token bundle, pool registration certificate, pool registration parameters, and vote registration metadata details.
-- `metadata` (object, optional): Specify the metadata for transaction construction.
-- `publicKey` (object, required): PublicKey contains a public key byte array for a particular CurveType encoded in hex. Note that there is no PrivateKey struct as this is NEVER the concern of an implementation.
- - `hexBytes` (string, required): The hexadecimal representation of the public key.
- - `curveType` (string, enum, required): The type of cryptographic curve associated with the public key (Choose from: secp256k1, secp256k1_bip340, secp256r1, edwards25519, tweedle, pallas).
-
-### Return Object
-
-The `constructionPayloads` method returns an object representing the unsigned transaction blob and a collection of payloads that must be signed by particular AccountIdentifiers using a certain SignatureType.
-
-Structure and behavior of this method may vary with different versions of the Cardano service. Always refer to the documentation specific to the version you are using for the most accurate information.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-constructionpreprocess.md b/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-constructionpreprocess.md
deleted file mode 100644
index 56533735..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-constructionpreprocess.md
+++ /dev/null
@@ -1,159 +0,0 @@
----
-title: "constructionPreprocess"
-slug: "rpc-cardano-constructionpreprocess"
-excerpt: "Cardano RPC"
-hidden: false
-metadata:
- description: "Cardano RPC"
- image: []
- keywords: "cardano, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:03 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, CardanoRosetta, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Cardano
-const tatum = await TatumSDK.init({ network: Network.CARDANO_ROSETTA });
-
-// Define the input parameters in a single object
-const params = {
- networkIdentifier: {
- blockchain: 'CARDANO', // Required: Specifies the blockchain .
- network: 'MAINNET', // Required: Specifies the network name .
- subNetworkIdentifier: {
- network: 'SUB_NETWORK_NAME', // Optional: Specifies the sub-network name .
- metadata: {
- KEY: 'VALUE', // Optional: Specify metadata .
- },
- },
- },
- operations: [
- {
- operation_identifier: {
- index: 1, // Required: Specifies the operation index (number).
- network_index: 0, // Optional: Specifies the network index (number).
- },
- related_operations: [
- {
- index: 2, // Optional: Specifies the related operation index (number).
- network_index: 1, // Optional: Specifies the related network index (number).
- },
- ],
- type: 'OPERATION_TYPE', // Required: Specifies the operation type.
- status: 'OPERATION_STATUS', // Optional: Specifies the operation status .
- account: {
- address: 'ACCOUNT_ADDRESS', // Required: Specifies the account address .
- sub_account: {
- address: 'SUB_ACCOUNT_ADDRESS', // Optional: Specifies the sub-account address .
- metadata: {
- // Optional metadata object for the sub-account
- },
- },
- metadata: {
- // Optional metadata object for the account
- },
- },
- amount: {
- value: 'AMOUNT_VALUE', // Required: Specifies the amount value (string).
- currency: {
- symbol: 'CURRENCY_SYMBOL', // Required: Specifies the currency symbol .
- decimals: 6, // Required: Specifies the currency decimals (number).
- metadata: {
- // Optional metadata for amount object
- },
- },
- metadata: {
- // Optional: Specify metadata here only if applicable.
- },
- },
- coin_change: {
- coin_identifier: {
- identifier: 'COIN_IDENTIFIER', // Required: uniquely identifies a Coin.
- },
- coin_action: 'coin_created', // Required
- },
- metadata: {
- // Optional: Specify operations metadata only if applicable.
- }
- },
- ],
- metadata: {
- //Optional: Specify constructionPreprocess metadata only if applicable.
- }
-};
-
-// Create a request to fetch metadata for transaction construction
-const preprocessRequest = await tatum.rpc.constructionPreprocess(params);
-
-// Log the preprocess request
-console.log('Construction Preprocess Request:', preprocessRequest);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `constructionPreprocess` method is called prior to `constructionPayloads` to construct a request for any metadata that is needed for transaction construction. This method is used to fetch information such as account nonce. The `options` object returned from this method will be sent to the `constructionMetadata` endpoint **UNMODIFIED** by the caller in an offline execution environment. If your Construction API implementation has configuration options, they MUST be specified in the `constructionPreprocess` request in the `metadata` field.
-
-### Example Use Cases
-
-1. **Transaction Construction**: Developers can use this method to fetch metadata required for transaction construction, such as the account nonce.
-2. **Validation**: Validators can use this method to validate transaction data before the actual transaction construction.
-
-### Request Parameters
-
-The `constructionPreprocess` method requires the following parameters:
-
-- `networkIdentifier` (object, required): An object containing information about the blockchain network.
- - `blockchain` (string, required): The blockchain identifier, which should be set to `CARDANO` for Cardano.
- - `network` (string, required): The network name for Cardano.
- - `subNetworkIdentifier` (object, optional): An optional sub-network identifier object.
- - `network` (string, required): The name of the sub-network within Cardano.
- - `metadata` (object, optional): Metadata associated with the sub-network.
-- `operations` (array of objects, required): An array of operation objects, where each object represents a transaction to be included in the Cardano transaction.
- - `operation_identifier` (object, required): An object containing an index that uniquely identifies the operation.
- - `index` (number, required): The index of the operation.
- - `network_index` (number, optional): The network-specific index of the operation.
- - `related_operations` (array of objects, optional): An array of related operation identifiers if applicable.
- - `index` (number, optional): The index of the related operation.
- - `network_index` (number, optional): The network-specific index of the related operation.
- - `type` (string, required): The type of the operation (e.g., "TRANSFER").
- - `status` (string, optional): The status of the operation (e.g., "SUCCESS").
- - `account` (object, required): An object containing information about the account.
- - `address` (string, required): The Cardano account address associated with the operation.
- - `sub_account` (object, optional): An optional sub-account object.
- - `address` (string, optional): The sub-account address.
- - `metadata` (object, optional): An optional metadata object for the sub-account. If the SubAccount address is not sufficient to uniquely specify a SubAccount, any other identifying information can be stored here. It is important to note that two SubAccounts with identical addresses but differing metadata will not be considered equal by clients.
- - `metadata` (object, optional): An optional metadata object for the account. Blockchains that utilize a username model (where the address is not a derivative of a cryptographic public key) should specify the public key(s) owned by the address in metadata.
- - `amount` (object, required): An object containing information about the transaction amount.
- - `value` (string, required): The value of the transaction amount.
- - `currency` (object, required): An object specifying the currency details.
- - `symbol` (string, required): The symbol or code of the currency.
- - `decimals` (number, required): The number of decimal places for the currency.
- - `metadata` (object, optional): Any additional information related to the currency itself. For example, it would be useful to populate this object with the contract address of an ERC-20 token.
- - `metadata` (object, optional): metadata object for the amount.
- - `coin_change` (object, required): An object containing information about coin changes in the operation.
- - `coin_identifier` (object, required): An object containing a coin identifier.
- - `identifier` (string, required): Identifier should be populated with a globally unique identifier of a Coin. In Bitcoin, this identifier would be transaction_hash:index..
- - `coin_action` (string, required): CoinActions are different state changes that a Coin can undergo. When a Coin is created, it is coin_created. When a Coin is spent, it is coin_spent. It is assumed that a single Coin cannot be created or spent more than once. (e.g., 'coin_created' | 'coin_spent').
- - `metadata` (object, optional): An optional metadata object for the operation, including withdrawal, deposit, refund, staking credential, pool key hash, epoch, token bundle, pool registration certificate, pool registration parameters, and vote registration metadata details.
-- `metadata` (object, optional): Metadata for `constructionPreprocess`
-
-### Return Object
-
-The method returns an object representing the preprocess request for transaction construction. This object includes the metadata required for constructing the transaction. The `options` object in this request will be sent to the `constructionMetadata` endpoint **UNMODIFIED** by the caller in an offline execution environment.
-
-Structure and behavior of this method may vary with different versions of the Cardano service. Always refer to the documentation specific to the version you are using for the most accurate information.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-createnetworktransaction.md b/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-createnetworktransaction.md
deleted file mode 100644
index f95b0455..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-createnetworktransaction.md
+++ /dev/null
@@ -1,124 +0,0 @@
----
-title: "createNetworkTransaction"
-slug: "rpc-cardano-createnetworktransaction"
-excerpt: "Cardano RPC"
-hidden: false
-metadata:
- description: "Cardano RPC"
- image: []
- keywords: "cardano, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:03 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, CardanoRosetta, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Cardano
-const tatum = await TatumSDK.init({ network: Network.CARDANO_ROSETTA });
-
-// Define the input parameters in a single object
-const params = {
- networkIdentifier: {
- blockchain: 'CARDANO', // Specify the blockchain identifier ('CARDANO' for Cardano).
- network: 'NETWORK_NAME', // Specify the network name.
- subNetworkIdentifier: {
- network: 'SUB_NETWORK_NAME', // Specify the sub-network name (optional).
- metadata: {
- // Optional metadata key-value pairs.
- },
- },
- },
- unsignedTransaction: 'UNSIGNED_TRANSACTION', // Specify the unsigned transaction blob.
- signatures: [
- {
- signing_payload: {
- address: 'ADDRESS', // [DEPRECATED] Network-specific address (optional).
- accountIdentifier: {
- address: 'ADDRESS', // Account address.
- subAccount: {
- address: 'ADDRESS', // Sub-account address (optional).
- metadata: {
- // Sub-account metadata (optional).
- },
- },
- metadata: {
- // Account metadata (optional).
- },
- },
- hexBytes: 'PAYLOAD_HEX', // Hex-encoded payload bytes.
- signatureType: 'ecdsa', // Signature type (ecdsa, ecdsa_recovery, ed25519, schnorr_1, schnorr_bip340, schnorr_poseidon).
- },
- publicKeys: [
- {
- hexBytes: 'PUBLIC_KEY_HEX', // Hexadecimal representation of the public key.
- curveType: 'secp256k1', // Curve type (secp256k1, secp256k1_bip340, secp256r1, edwards25519, tweedle, pallas).
- },
- ],
- signatureType: 'ecdsa', // Signature type (ecdsa, ecdsa_recovery, ed25519, schnorr_1, schnorr_bip340, schnorr_poseidon).
- hexBytes: 'SIGNATURE_HEX', // Hex-encoded signature.
- },
- ],
-};
-
-// Create network transaction from signatures
-const networkTransaction = await tatum.rpc.createNetworkTransaction(params);
-
-// Log the network transaction
-console.log('Network Transaction:', networkTransaction);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `createNetworkTransaction` method allows you to create a network-specific transaction from an unsigned transaction and an array of provided signatures. The signed transaction returned from this method will be sent to the `/construction/submit` endpoint by the caller.
-
-### Example Use Cases
-
-1. **Transaction Construction**: Developers can use this method to combine an unsigned Cardano transaction with the corresponding signatures, resulting in a fully signed network transaction ready to be submitted to the Cardano network.
-
-### Request Parameters
-
-The `createNetworkTransaction` method requires the following parameters in the request body:
-
-- `networkIdentifier` (object, required): An object containing information about the blockchain network.
- - `blockchain` (string, required): The blockchain identifier, which should be set to `CARDANO` for Cardano.
- - `network` (string, required): The network name for Cardano.
- - `subNetworkIdentifier` (object, optional): An optional sub-network identifier object.
- - `network` (string, required): The name of the sub-network within Cardano.
- - `metadata` (object, optional): Metadata associated with the sub-network.
-- `unsignedTransaction` (string, required): Contains the unsigned transaction blob returned by the `constructionPayloads` endpoint. The unsigned transaction represents the basic structure and details of the transaction before it is signed.
-- `signatures` (array of objects, required): This parameter is an array of signatures. Each signature is represented by a Signature object. Signatures are required to create a network transaction by combining them with the unsigned transaction.
- - `signing_payload` (object, required): The payload that was signed.
- - `address` (string, optional): [DEPRECATED] The network-specific address of the account that should sign the payload.
- - `accountIdentifier` (object, optional): An object containing information about the account.
- - `address` (string, required): The Cardano account address associated with the operation.
- - `sub_account` (object, optional): An optional sub-account object.
- - `address` (string, optional): The sub-account address.
- - `metadata` (object, optional): An optional metadata object for the sub-account. If the SubAccount address is not sufficient to uniquely specify a SubAccount, any other identifying information can be stored here. It is important to note that two SubAccounts with identical addresses but differing metadata will not be considered equal by clients.
- - `metadata` (object, optional): An optional metadata object for the account. Blockchains that utilize a username model (where the address is not a derivative of a cryptographic public key) should specify the public key(s) owned by the address in metadata.
- - `hex_bytes` (string, required): Hex-encoded string of the payload bytes.
- - `signatureType` (string, enum, optional): Signature type (Choose from: ecdsa, ecdsa_recovery, ed25519, schnorr_1, schnorr_bip340, schnorr_poseidon).
- - `publicKey` (object, required): PublicKey contains a public key byte array for a particular CurveType encoded in hex. Note that there is no PrivateKey struct as this is NEVER the concern of an implementation.
- - `hexBytes` (string, required): The hexadecimal representation of the public key.
- - `curveType` (string, enum, required): The type of cryptographic curve associated with the public key (Choose from: secp256k1, secp256k1_bip340, secp256r1, edwards25519, tweedle, pallas).
- - `signatureType` (string, enum, required): Signature type (Choose from: ecdsa, ecdsa_recovery, ed25519, schnorr_1, schnorr_bip340, schnorr_poseidon).
- - `hexBytes` (string, required): Hex-encoded string representing the signature.
-
-### Return Object
-
-The method returns an object representing the network transaction created from the unsigned transaction and provided signatures.
-
-Structure and behavior of this method may vary with different versions of the Cardano service. Always refer to the documentation specific to the version you are using for the most accurate information.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-deriveaccount.md b/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-deriveaccount.md
deleted file mode 100644
index 0a0c8048..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-deriveaccount.md
+++ /dev/null
@@ -1,88 +0,0 @@
----
-title: "deriveAccount"
-slug: "rpc-cardano-deriveaccount"
-excerpt: "Cardano RPC"
-hidden: false
-metadata:
- description: "Cardano RPC"
- image: []
- keywords: "cardano, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:03 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, CardanoRosetta, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Cardano
-const tatum = await TatumSDK.init({ network: Network.CARDANO_ROSETTA });
-
-// Define the input parameters in a single object
-const params = {
- networkIdentifier: {
- blockchain: 'CARDANO', // string, required
- network: 'NETWORK_NAME', // string, required
- subNetworkIdentifier: {
- network: 'SUB_NETWORK_NAME', // string (optional)
- metadata: {
- [key: string]: any, // object (optional)
- },
- },
- },
- publicKeys: {
- hexBytes: 'PUBLIC_KEY_HEX_BYTES', // string, required
- curveType: 'secp256k1', // CurveType, required (Choose from: secp256k1, secp256k1_bip340, secp256r1, edwards25519, tweedle, pallas)
- },
- metadata: {
- // metadata is optional object
- },
-};
-
-// Derive the account identifier from the public key
-const accountIdentifier = await tatum.rpc.deriveAccount(params);
-
-// Log the account identifier
-console.log('Account Identifier:', accountIdentifier);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `deriveAccount` method allows you to derive an account identifier (AccountIdentifier) from a public key.
-
-### Example Use Cases
-
-1. **Account Identification**: Developers can use this method to derive the account identifier associated with a public key.
-
-### Request Parameters
-
-The `deriveAccount` method requires the following parameter:
-
-- `networkIdentifier` (object, required): An object containing information about the blockchain network.
- - `blockchain` (string, required): The blockchain identifier, which should be set to `CARDANO` for Cardano.
- - `network` (string, required): The network name for Cardano.
- - `subNetworkIdentifier` (object, optional): An optional sub-network identifier object.
- - `network` (string, required): The name of the sub-network within Cardano.
- - `metadata` (object, optional): Metadata associated with the sub-network.
-- `publicKey` (object, required): PublicKey contains a public key byte array for a particular CurveType encoded in hex. Note that there is no PrivateKey struct as this is NEVER the concern of an implementation.
- - `hexBytes` (string, required): The hexadecimal representation of the public key.
- - `curveType` (string, enum, required): The type of cryptographic curve associated with the public key (Choose from: secp256k1, secp256k1_bip340, secp256r1, edwards25519, tweedle, pallas).
-- `metadata` (object, optional): An optional metadata object.
-
-### Return Object
-
-The method returns an object representing the derived account identifier (AccountIdentifier) associated with the specified public key.
-
-Structure and behavior of this method may vary with different versions of the Cardano service. Always refer to the documentation specific to the version you are using for the most accurate information.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-getaccountbalance.md b/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-getaccountbalance.md
deleted file mode 100644
index 3e8f5045..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-getaccountbalance.md
+++ /dev/null
@@ -1,101 +0,0 @@
----
-title: "getAccountBalance"
-slug: "rpc-cardano-getaccountbalance"
-excerpt: "Cardano RPC"
-hidden: false
-metadata:
- description: "Cardano RPC"
- image: []
- keywords: "cardano, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:41 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, CardanoRosetta, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Cardano
-const tatum = await TatumSDK.init({ network: Network.CARDANO_ROSETTA });
-
-// Define the input parameters in a single object
-const params = {
- networkIdentifier: {
- blockchain: 'CARDANO', // string, required
- network: 'NETWORK_NAME', // string, required
- },
- accountIdentifier: {
- address: 'ACCOUNT_ADDRESS', // string, required
- sub_account: {
- // Specify sub-account information if applicable
- },
- metadata: {
- chain_code: 'CHAIN_CODE', // Specify chain code only if applicable
- },
- },
- blockIdentifier: {
- index: 1123941, // number (int64), optional
- hash: '0x1f2cc6c5027d2f201a5453ad1119574d2aed23a392654742ac3c78783c071f85', // string, optional
- }, // `blockIdentifier` is optional object
- currency: {
- symbol: 'ADA', // string, required
- decimals: 6, // number, required
- metadata: {
- // Specify metadata if applicable
- },
- }, // `currency` is optional object
-};
-
-// Retrieve the account balance for the specified Cardano account
-const accountBalance = await tatum.rpc.getAccountBalance(params);
-
-// Log the account balance
-console.log('Cardano Account Balance:', accountBalance);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getAccountBalance` method allows you to get an account's balance for a specified Cardano account identifier and block identifier.
-
-### Example Use Cases
-
-1. **Balance Summary**: Developers can use this method to retrieve the balance summary of a Cardano account, including the total balance and balances of specific sub-accounts.
-
-### Request Parameters
-
-The `getAccountBalance` method requires the following parameters:
-
-- `networkIdentifier` (object, required): An object containing information about the blockchain network.
- - `blockchain` (string, required): The blockchain identifier, which should be set to `'CARDANO'` for Cardano.
- - `network` (string, required): The network name for Cardano.
-- `accountIdentifier` (object, optional): An object containing information about the account.
- - `address` (string, required): The Cardano account address associated with the operation.
- - `sub_account` (object, optional): An optional sub-account object.
- - `address` (string, optional): The sub-account address.
- - `metadata` (object, optional): An optional metadata object for the sub-account. If the SubAccount address is not sufficient to uniquely specify a SubAccount, any other identifying information can be stored here. It is important to note that two SubAccounts with identical addresses but differing metadata will not be considered equal by clients.
- - `metadata` (object, optional): An optional metadata object for the account. Blockchains that utilize a username model (where the address is not a derivative of a cryptographic public key) should specify the public key(s) owned by the address in metadata.
-- `blockIdentifier` (object, optional): An object containing information about the block.
- - `index` (number, optional): The index of the block (Type: number, Format: int64).
- - `hash` (string, optional): The hash of the block.
-- `currency` (object, required): An object specifying the currency details.
- - `symbol` (string, required): The symbol or code of the currency.
- - `decimals` (number, required): The number of decimal places for the currency.
- - `metadata` (object, optional): Any additional information related to the currency itself. For example, it would be useful to populate this object with the contract address of an ERC-20 token.
-
-### Return Object
-
-The method returns an object representing the account's balance for the specified Cardano account identifier and block identifier. It includes the total balance and balances of specific sub-accounts.
-
-Structure and behavior of this method may vary with different versions of the Cardano service. Always refer to the documentation specific to the version you are using for the most accurate information.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-getaccountcoins.md b/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-getaccountcoins.md
deleted file mode 100644
index 4b8ba30e..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-getaccountcoins.md
+++ /dev/null
@@ -1,96 +0,0 @@
----
-title: "getAccountCoins"
-slug: "rpc-cardano-getaccountcoins"
-excerpt: "Cardano RPC"
-hidden: false
-metadata:
- description: "Cardano RPC"
- image: []
- keywords: "cardano, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:06 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, CardanoRosetta, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Cardano
-const tatum = await TatumSDK.init({ network: Network.CARDANO_ROSETTA });
-
-// Define the input parameter in a single object
-const params = {
- networkIdentifier: {
- blockchain: 'CARDANO', // string, required
- network: 'NETWORK_NAME', // string, required
- },
- accountIdentifier: {
- address: 'ACCOUNT_ADDRESS', // string, required
- sub_account: {
- // Specify sub-account information if applicable
- },
- metadata: {
- chain_code: 'CHAIN_CODE', // Specify chain code if applicable
- },
- },
- includeMempool: true, // boolean, optional
- currency: {
- symbol: 'ADA', // string, required
- decimals: 6, // number, required
- metadata: {
- // Specify metadata only if applicable
- },
- },
-};
-
-// Retrieve unspent coins for an account in Cardano blockchain
-const unspentCoins = await tatum.rpc.getAccountCoins(params);
-
-// Log the unspent coins
-console.log('Unspent Coins:', unspentCoins);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getAccountCoins` method allows you to get an array of all unspent coins for a Cardano account.
-
-### Example Use Cases
-
-1. **Account Balance**: Developers can use this method to retrieve the unspent coins for a Cardano account and calculate its balance.
-
-### Request Parameters
-
-The `getAccountCoins` method requires the following parameters:
-
-- `networkIdentifier` (object, required): An object containing information about the blockchain network.
- - `blockchain` (string, required): The blockchain identifier, which should be set to `'CARDANO'` for Cardano.
- - `network` (string, required): The network name for Cardano.
-- `accountIdentifier` (object, optional): An object containing information about the account.
- - `address` (string, required): The Cardano account address associated with the operation.
- - `sub_account` (object, optional): An optional sub-account object.
- - `address` (string, optional): The sub-account address.
- - `metadata` (object, optional): An optional metadata object for the sub-account. If the SubAccount address is not sufficient to uniquely specify a SubAccount, any other identifying information can be stored here. It is important to note that two SubAccounts with identical addresses but differing metadata will not be considered equal by clients.
- - `metadata` (object, optional): An optional metadata object for the account. Blockchains that utilize a username model (where the address is not a derivative of a cryptographic public key) should specify the public key(s) owned by the address in metadata.
-- `includeMempool` (boolean, optional): An optional boolean flag to indicate whether to include mempool transactions. Default is `true`.
-- `currency` (object, required): An object specifying the currency details.
- - `symbol` (string, required): The symbol or code of the currency.
- - `decimals` (number, required): The number of decimal places for the currency.
- - `metadata` (object, optional): Any additional information related to the currency itself. For example, it would be useful to populate this object with the contract address of an ERC-20 token.
-
-### Return Object
-
-The method returns an object representing the unspent coins for the specified Cardano account. This object includes details about the unspent coins and the block identifier at which the lookup was performed.
-
-Please note that the structure of the returned object may vary based on the Cardano RPC version.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-getblock.md b/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-getblock.md
deleted file mode 100644
index b2576ece..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-getblock.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-title: "getBlock"
-slug: "rpc-cardano-getblock"
-excerpt: "Cardano RPC"
-hidden: false
-metadata:
- description: "Cardano RPC"
- image: []
- keywords: "cardano, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:02 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, CardanoRosetta, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Cardano
-const tatum = await TatumSDK.init({ network: Network.CARDANO_ROSETTA });
-
-// Define the input parameters in a single object
-const params = {
- networkIdentifier: {
- blockchain: 'CARDANO', // string, required
- network: 'NETWORK_NAME', // string, required
- subNetworkIdentifier: {
- network: 'SUB_NETWORK_NAME', // string (optional)
- metadata: {
- [key: string]: any, // object (optional)
- },
- },
- },
- blockIdentifier: {
- index: 1123941, // number (int64), required
- hash: '0x1f2cc6c5027d2f201a5453ad1119574d2aed23a392654742ac3c78783c071f85', // string (optional)
- },
-};
-
-// Call the getBlock
-const block = await tatum.rpc.getBlock(params);
-
-// Log the block details
-console.log('Block:', block);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getBlock` method allows you to retrieve information about a specific Cardano block based on the provided parameters.
-
-### Request Body
-
-The request body should contain the following parameters:
-
-- `networkIdentifier` (object, required): An object containing information about the blockchain network.
- - `blockchain` (string, required): The blockchain identifier, which should be set to `CARDANO` for Cardano.
- - `network` (string, required): The network name for Cardano.
- - `subNetworkIdentifier` (object, optional): An optional sub-network identifier object.
- - `network` (string, required): The name of the sub-network within Cardano.
- - `metadata` (object, optional): Metadata associated with the sub-network.
-- `blockIdentifier` (object): An object containing information about the block to retrieve.
- - `index` (number, required): The index of the block (Type: number, Format: int64).
- - `hash` (string): The hash of the block (optional).
-
-### Response
-
-The response will contain details about the specified Cardano block.
-
-Structure and behavior of this method may vary with different versions of the Cardano service. Always refer to the documentation specific to the version you are using for the most accurate information.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-getblocktransaction.md b/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-getblocktransaction.md
deleted file mode 100644
index 470fb520..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-getblocktransaction.md
+++ /dev/null
@@ -1,85 +0,0 @@
----
-title: "getBlockTransaction"
-slug: "rpc-cardano-getblocktransaction"
-excerpt: "Cardano RPC"
-hidden: false
-metadata:
- description: "Cardano RPC"
- image: []
- keywords: "cardano, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:02 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, CardanoRosetta, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Cardano
-const tatum = await TatumSDK.init({ network: Network.CARDANO_ROSETTA });
-
-// Define the input parameters in a single object
-const params = {
- networkIdentifier: {
- blockchain: 'CARDANO', // string, required
- network: 'NETWORK_NAME', // string, required
- subNetworkIdentifier: {
- network: 'SUB_NETWORK_NAME',
- metadata: {
- [key: string]: any
- } // string (optional)
- },
- },
- blockIdentifier: {
- index: 1123941, // number (int64), required
- hash: '0x1f2cc6c5027d2f201a5453ad1119574d2aed23a392654742ac3c78783c071f85', // string, required
- },
- transactionIdentifier: {
- hash: 'TRANSACTION_HASH', // string, required
- },
-};
-
-// Call the getBlockTransaction
-const transaction = await tatum.rpc.getBlockTransaction(params);
-
-// Log the transaction details
-console.log('Transaction:', transaction);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getBlockTransaction` method allows you to retrieve information about a specific transaction within a Cardano block based on the provided parameters.
-
-### Request Body
-
-The request body should contain the following parameters:
-
-- `networkIdentifier` (object, required): An object containing information about the blockchain network.
- - `blockchain` (string, required): The blockchain identifier, which should be set to `CARDANO` for Cardano.
- - `network` (string, required): The network name for Cardano.
- - `subNetworkIdentifier` (object, optional): An optional sub-network identifier object.
- - `network` (string, required): The name of the sub-network within Cardano.
- - `metadata` (object, optional): Metadata associated with the sub-network.
-- `blockIdentifier` (object, required): An object containing information about the block to which the transaction belongs.
- - `index` (number, required): The index of the block (Type: number, Format: int64).
- - `hash` (string, required): The hash of the block.
-- `transactionIdentifier` (object, required): An object containing information about the transaction.
- - `hash` (string, required): The hash of the transaction.
-
-### Response
-
-The response will contain details about the specified Cardano transaction.
-
-Structure and behavior of this method may vary with different versions of the Cardano service. Always refer to the documentation specific to the version you are using for the most accurate information.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-gethashoftransaction.md b/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-gethashoftransaction.md
deleted file mode 100644
index 62bad954..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-gethashoftransaction.md
+++ /dev/null
@@ -1,79 +0,0 @@
----
-title: "getHashOfTransaction"
-slug: "rpc-cardano-gethashoftransaction"
-excerpt: "Cardano RPC"
-hidden: false
-metadata:
- description: "Cardano RPC"
- image: []
- keywords: "cardano, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:02 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, CardanoRosetta, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Cardano
-const tatum = await TatumSDK.init({ network: Network.CARDANO_ROSETTA });
-
-// Define the input parameters in a single object
-const hashRequest = {
- networkIdentifier: {
- blockchain: 'CARDANO', // Specify the blockchain identifier ('CARDANO' for Cardano).
- network: 'NETWORK_NAME', // Specify the network name.
- subNetworkIdentifier: {
- network: 'SUB_NETWORK_NAME', // Specify the sub-network name (optional).
- metadata: {
- // Optional metadata key-value pairs.
- },
- },
- },
- signedTransaction: 'SIGNED_TRANSACTION', // Specify the signed transaction blob.
-};
-
-// Calculate the hash of the transaction
-const transactionHash = await tatum.rpc.getHashOfTransaction(hashRequest);
-
-// Log the transaction hash
-console.log('Transaction Hash:', transactionHash);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getHashOfTransaction` method allows you to calculate the unique transaction hash (ID) for a signed transaction. The transaction hash represents the unique identifier for a transaction on the Cardano blockchain.
-
-### Example Use Cases
-
-1. **Transaction Hash Calculation**: Developers can use this method to calculate the transaction hash for a signed transaction, which can be useful for tracking and verifying transactions on the Cardano network.
-
-### Request Parameters
-
-The `getHashOfTransaction` method requires the following parameters in the request body:
-
-- `networkIdentifier` (object, required): An object containing information about the blockchain network.
- - `blockchain` (string, required): The blockchain identifier, which should be set to `CARDANO` for Cardano.
- - `network` (string, required): The network name for Cardano.
- - `subNetworkIdentifier` (object, optional): An optional sub-network identifier object.
- - `network` (string, required): The name of the sub-network within Cardano.
- - `metadata` (object, optional): Metadata associated with the sub-network.
-- `signedTransaction` (string, required): The signed transaction blob for which you want to calculate the transaction hash.
-
-### Return Object
-
-The method returns a string representing the transaction hash (ID) of the provided signed transaction.
-
-Structure and behavior of this method may vary with different versions of the Cardano service. Always refer to the documentation specific to the version you are using for the most accurate information.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-getnetworklist.md b/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-getnetworklist.md
deleted file mode 100644
index 37d3d54a..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-getnetworklist.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: "getNetworkList"
-slug: "rpc-cardano-getnetworklist"
-excerpt: "Cardano RPC"
-hidden: false
-metadata:
- description: "Cardano RPC"
- image: []
- keywords: "cardano, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:42 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, CardanoRosetta, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Cardano
-const tatum = await TatumSDK.init({ network: Network.CARDANO_ROSETTA });
-
-// Optional metadata parameter
-const params = metadata: {
- [key: string]: any, // object (optional)
- },
-
-// Call the `getNetworkList` method
-const networkList = await tatum.rpc.getNetworkList(params);
-
-// Log the network list
-console.log('Network List:', networkList);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getNetworkList` method allows you to retrieve a list of available networks that the Rosetta server supports.
-
-### Example Use Cases
-
-1. **Supported Networks**: Developers can use this method to retrieve the list of networks supported by the Rosetta server.
-
-### Request Parameters
-
-The `getNetworkList` method has only optional metadata object.
-
-- `metadata` (object, optional)
-
-### Return Object
-
-The method returns an object representing the list of available networks supported by the Rosetta server.
-
-Structure and behavior of this method may vary with different versions of the Cardano service. Always refer to the documentation specific to the version you are using for the most accurate information.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-getnetworkstatus.md b/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-getnetworkstatus.md
deleted file mode 100644
index 3648e8c1..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-getnetworkstatus.md
+++ /dev/null
@@ -1,81 +0,0 @@
----
-title: "getNetworkStatus"
-slug: "rpc-cardano-getnetworkstatus"
-excerpt: "Cardano RPC"
-hidden: false
-metadata:
- description: "Cardano RPC"
- image: []
- keywords: "cardano, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:02 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, CardanoRosetta, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Cardano
-const tatum = await TatumSDK.init({ network: Network.CARDANO_ROSETTA });
-
-// Define the input parameters in a single object
-const params = {
- network_identifier: {
- blockchain: 'CARDANO', // string, required
- network: 'NETWORK_NAME', // string, required
- sub_network_identifier: {
- network: 'SUB_NETWORK_NAME', // string (optional)
- metadata: {
- [key: string]: any, // object (optional)
- },
- },
- },
- metadata: {
- [key: string]: any, // object (optional)
- },
-};
-
-// Retrieve the status of the Cardano network
-const getNetworkStatus = await tatum.rpc.getNetworkStatus(params);
-
-// Log the network status
-console.log('Cardano Network Status:', getNetworkStatus);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `getNetworkStatus` method allows you to retrieve the current status of a Cardano network.
-
-### Example Use Cases
-
-1. **Network Information**: Developers can use this method to retrieve the current status and information of a Cardano network, including details about the network itself and its status.
-
-### Request Parameters
-
-The `getNetworkStatus` method requires the following parameters:
-
-- `networkIdentifier` (object, required): An object containing information about the blockchain network.
- - `blockchain` (string, required): The blockchain identifier, which should be set to `CARDANO` for Cardano.
- - `network` (string, required): The network name for Cardano.
- - `subNetworkIdentifier` (object, optional): An optional sub-network identifier object.
- - `network` (string, required): The name of the sub-network within Cardano.
- - `metadata` (object, optional): Metadata associated with the sub-network.
-- `metadata` (object, optional): Metadata associated with the network status.
-
-### Return Object
-
-The method returns an object representing the current status of the Cardano network.
-
-Structure and behavior of this method may vary with different versions of the Cardano service. Always refer to the documentation specific to the version you are using for the most accurate information.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-parsetransaction.md b/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-parsetransaction.md
deleted file mode 100644
index a5a470d4..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-parsetransaction.md
+++ /dev/null
@@ -1,81 +0,0 @@
----
-title: "parseTransaction"
-slug: "rpc-cardano-parsetransaction"
-excerpt: "Cardano RPC"
-hidden: false
-metadata:
- description: "Cardano RPC"
- image: []
- keywords: "cardano, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:02 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, CardanoRosetta, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Cardano
-const tatum = await TatumSDK.init({ network: Network.CARDANO_ROSETTA });
-
-// Define the input parameters in a single object
-const parseRequest = {
- networkIdentifier: {
- blockchain: 'CARDANO', // Specify the blockchain identifier ('CARDANO' for Cardano).
- network: 'NETWORK_NAME', // Specify the network name.
- subNetworkIdentifier: {
- network: 'SUB_NETWORK_NAME', // Specify the sub-network name (optional).
- metadata: {
- // Optional metadata key-value pairs.
- },
- },
- },
- signed: true, // Specify whether the transaction is signed (boolean).
- transaction: 'TRANSACTION', // Specify the transaction blob (either unsigned or signed).
-};
-
-// Parse the transaction
-const parsedTransaction = await tatum.rpc.transactionParse(parseRequest);
-
-// Log the parsed transaction
-console.log('Parsed Transaction:', parsedTransaction);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `transactionParse` method allows you to parse either an unsigned or signed transaction and retrieve information about the transaction. It is used to examine the details of a transaction without submitting it to the blockchain.
-
-### Example Use Cases
-
-1. **Transaction Inspection**: Developers can use this method to inspect and verify the details of a transaction before submitting it to the Cardano network.
-
-### Request Parameters
-
-The `transactionParse` method requires the following parameters in the request body:
-
-- `networkIdentifier` (object, required): An object containing information about the blockchain network.
- - `blockchain` (string, required): The blockchain identifier, which should be set to `CARDANO` for Cardano.
- - `network` (string, required): The network name for Cardano.
- - `subNetworkIdentifier` (object, optional): An optional sub-network identifier object.
- - `network` (string, required): The name of the sub-network within Cardano.
- - `metadata` (object, optional): Metadata associated with the sub-network.
-- `signed` (boolean, required): A boolean indicating whether the transaction is signed. Set to `true` for a signed transaction and `false` for an unsigned transaction.
-- `transaction` (string, required): The transaction blob, which must be either the unsigned transaction blob returned by `constructionPayloads` or the signed transaction blob returned by `constructionCombine`.
-
-### Return Object
-
-The method returns an object containing parsed information about the transaction, such as transaction inputs, outputs, and other details.
-
-Structure and behavior of this method may vary with different versions of the Cardano service. Always refer to the documentation specific to the version you are using for the most accurate information.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-searchtransactions.md b/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-searchtransactions.md
deleted file mode 100644
index 70db6bf3..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-searchtransactions.md
+++ /dev/null
@@ -1,126 +0,0 @@
----
-title: "searchTransactions"
-slug: "rpc-cardano-searchtransactions"
-excerpt: "Cardano RPC"
-hidden: false
-metadata:
- description: "Cardano RPC"
- image: []
- keywords: "cardano, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:40 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-import { TatumSDK, CardanoRosetta, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Cardano
-const tatum = await TatumSDK.init({ network: Network.CARDANO_ROSETTA });
-
-// Define the input parameters in a single object
-const params = {
- networkIdentifier: {
- blockchain: 'CARDANO',
- network: 'NETWORK_NAME',
- subNetworkIdentifier: {
- network: 'SUB_NETWORK_NAME',
- metadata: {
- // Optional metadata key-value pairs.
- },
- },
- },
- operator: {
- // Specify search conditions (optional).
- },
- max_block: 5, // The largest block index to consider (optional).
- offset: 5, // The offset into the query result to start returning transactions (optional).
- limit: 5, // The maximum number of transactions to return in one call (optional).
- transactionIdentifier: {
- hash: 'TRANSACTION_HASH', // string, required
- },
- accountIdentifier: {
- address: 'ACCOUNT_ADDRESS', // string, required
- sub_account: {
- // Specify sub-account information if applicable
- },
- metadata: {
- chain_code: 'CHAIN_CODE', // Specify chain code if applicable
- },
- },
- coin_identifier: {
- identifier: 'CO' // Specify search conditions (optional).
- },
- currency: {
- symbol: 'CURRENCY_SYMBOL', // Required: Specifies the currency symbol .
- decimals: 6, // Required: Specifies the currency decimals (number).
- metadata: {
- // Optional metadata for amount object
- },
- },
- status: 'reverted', // The network-specific operation status type (optional).
- type: 'transfer', // The network-specific operation type (optional).
- address: '0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347', // Account address (optional).
- success: true, // A synthetic condition (optional).
-};
-
-// Search for transactions
-const transactions = await tatum.rpc.searchTransactions(params);
-
-// Log the retrieved transactions
-console.log('Transactions:', transactions);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `searchTransactions` method allows you to search for transactions matching a set of provided conditions in canonical blocks. This can be useful for querying transaction data based on various criteria.
-
-### Example Use Cases
-
-1. **Transaction Query**: Developers can use this method to search for transactions that meet specific criteria, such as a particular status or operation type.
-2. **Block Analysis**: Users can analyze transactions within a specific range of blocks to identify patterns or trends.
-
-## Request Parameters
-
-The `searchTransactions` method requires the following parameters in the request body:
-
-- `networkIdentifier` (object, required): An object containing information about the blockchain network.
- - `blockchain` (string, required): The blockchain identifier, which should be set to `CARDANO` for Cardano.
- - `network` (string, required): The network name for Cardano.
- - `subNetworkIdentifier` (object, optional): An optional sub-network identifier object.
- - `network` (string, optional): The name of the sub-network within Cardano.
- - `metadata` (object, optional): Metadata associated with the sub-network.
-- `operator` (enum, optional): Additional search conditions `or` and `and`.
-- `max_block` (number, optional): The largest block index to consider when searching for transactions. If not populated, the current block is considered the `max_block`. If you do not specify a `max_block`, it is possible that a newly synced block will interfere with paginated transaction queries (as the offset could become invalid with newly added rows).
-- `offset` (number, optional): The offset into the query result to start returning transactions. If any search conditions are changed, the query offset will change, and you must restart your search iteration.
-- `limit` (number, optional): The maximum number of transactions to return in one call. The implementation may return \<= `limit` transactions.
-- `transactionIdentifier` (object, required): An object containing information about the transaction.
- - `hash` (string, required): The hash of the transaction.
-- `accountIdentifier` (object, optional): An object containing information about the account.
- - `address` (string, required): The Cardano account address associated with the operation.
- - `sub_account` (object, optional): An optional sub-account object.
- - `address` (string, optional): The sub-account address.
- - `metadata` (object, optional): An optional metadata object for the sub-account. If the SubAccount address is not sufficient to uniquely specify a SubAccount, any other identifying information can be stored here. It is important to note that two SubAccounts with identical addresses but differing metadata will not be considered equal by clients.
- - `metadata` (object, optional): An optional metadata object for the account.
-- `coinIdentifier` (object, optional): Specify search conditions for coin identifier. Identifier should be populated with a globally unique identifier of a Coin. In Bitcoin, this identifier would be transaction\_hash: index.
- - `identifier` (string, required): Example: '0x2f23fd8cca835af21f3ac375bac601f97ead75f2e79143bdf71fe2c4be043e8f: 1'
-- `currency` (object, required): An object specifying the currency details. - `symbol` (string, required): The symbol or code of the currency. - `decimals` (number, required): The number of decimal places for the currency. - `metadata` (object, optional): Any additional information related to the currency itself. For example, it would be useful to populate this object with the contract address of an ERC-20 token.
-- `status` (string, optional): The network-specific operation status type (optional).
-- `type` (string, optional): The network-specific operation type (optional).
-- `address` (string, optional): AccountIdentifier.Address. This is used to get all transactions related to an AccountIdentifier.Address, regardless of SubAccountIdentifier.
-- `success` (boolean, optional): A synthetic condition populated by parsing network-specific operation statuses.
-
-### Return Object
-
-The method returns a list of transactions that match the specified search criteria.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-submittransaction.md b/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-submittransaction.md
deleted file mode 100644
index df0a314e..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-cardano/rpc-cardano-submittransaction.md
+++ /dev/null
@@ -1,79 +0,0 @@
----
-title: "submitTransaction"
-slug: "rpc-cardano-submittransaction"
-excerpt: "Cardano RPC"
-hidden: false
-metadata:
- description: "Cardano RPC"
- image: []
- keywords: "cardano, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:03 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-```typescript
-// Import required libraries and modules from Tatum SDK
-import { TatumSDK, CardanoRosetta, Network } from '@tatumio/tatum';
-
-// Initialize the Tatum SDK for Cardano
-const tatum = await TatumSDK.init({ network: Network.CARDANO_ROSETTA });
-
-// Define the input parameters in a single object
-const submitRequest = {
- networkIdentifier: {
- blockchain: 'CARDANO', // Specify the blockchain identifier ('CARDANO' for Cardano).
- network: 'NETWORK_NAME', // Specify the network name.
- subNetworkIdentifier: {
- network: 'SUB_NETWORK_NAME', // Specify the sub-network name (optional).
- metadata: {
- // Optional metadata.
- },
- },
- },
- signedTransaction: 'SIGNED_TRANSACTION', // Specify the signed transaction to submit.
-};
-
-// Submit the signed transaction to the network
-const transactionResponse = await tatum.rpc.submitTransaction(submitRequest);
-
-// Log the transaction response
-console.log('Transaction Response:', transactionResponse);
-
-// Always destroy the Tatum SDK instance when done to stop any background processes
-await tatum.destroy();
-```
-
-### Overview
-
-The `submitTransaction` method allows you to submit a signed transaction to the Cardano network for processing. After successfully constructing and signing a transaction, you can use this method to broadcast it to the network.
-
-### Example Use Cases
-
-1. **Transaction Submission**: Developers can use this method to submit a signed Cardano transaction to the network for execution. This is the final step in the transaction lifecycle.
-
-### Request Parameters
-
-The `submitTransaction` method requires the following parameters in the request body:
-
-- `networkIdentifier` (object, required): An object containing information about the blockchain network.
- - `blockchain` (string, required): The blockchain identifier, which should be set to 'CARDANO' for Cardano.
- - `network` (string, required): The network name for Cardano.
- - `subNetworkIdentifier` (object, optional): An optional sub-network identifier object.
- - `network` (string, required): The name of the sub-network within Cardano.
- - `metadata` (object, optional): Metadata associated with the sub-network.
-- `signedTransaction` (string, required): The signed transaction blob that you want to submit to the Cardano network.
-
-### Return Object
-
-The method returns an object representing the response from the Cardano network after submitting the signed transaction. This response may include details about the transaction's acceptance by the network.
-
-Structure and behavior of this method may vary with different versions of the Cardano service. Always refer to the documentation specific to the version you are using for the most accurate information.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-eos.md b/v1.0/RPC Nodes/rpc-others/rpc-eos.md
deleted file mode 100644
index ce3d6698..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-eos.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Eos"
-slug: "rpc-eos"
-excerpt: ""
-hidden: false
-createdAt: "Wed Mar 06 2024 10:35:18 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:41 GMT+0000 (Coordinated Universal Time)"
----
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_abi.md b/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_abi.md
deleted file mode 100644
index db8ff121..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_abi.md
+++ /dev/null
@@ -1,95 +0,0 @@
----
-title: "get_abi"
-slug: "rpc-eos-get_abi"
-excerpt: "Eos RPC"
-hidden: false
-metadata:
- description: "Eos RPC"
- image: []
- keywords: "eos, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:05 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### Overview
-
-The `get_abi` method is utilized to retrieve the ABI (Application Binary Interface) associated with an EOS account. ABI is critical for encoding and decoding the data correctly to interact with the smart contracts deployed by the account.
-{% tabs %}
-{% tab title="TypeScript/JavaScript" %}
-{% code overflow="wrap" lineNumbers="true" %}
-
-```typescript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Eos, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.EOS })
-
-const response = await tatum.rpc.getAbi({ accountName: 'b1' })
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-{% endtab %}
-{% endtabs %}
-
-### Example use cases:
-
-1. **Smart Contract Interaction:**
- Developers can use the `get_abi` method to obtain the ABI of a smart contract, enabling them to interact with the contract's methods and access its state variables and structures.
-
-2. **Data Encoding and Decoding:**
- The method is crucial for encoding the data sent to a smart contract and decoding the data received from it, facilitating seamless interaction with smart contracts deployed on the EOS blockchain.
-
-3. **Contract Development and Testing:**
- `get_abi` is invaluable for developers in the development and testing phases of smart contract deployment, allowing for accurate and efficient contract interaction and validation.
-
-### Request Parameters
-
-The `getAbi` method usually requires one parameter in the request body:
-
-- `accountName` (string, required): The name of the EOS account whose ABI is being requested.
-
-### Return Object
-
-The `get_abi` method typically returns an object containing the ABI details including the version, types, structs, actions, tables, and more, of the requested account:
-
-- `version` (string): The version of the ABI.
-- `types` (array): An array containing the types used in the ABI.
-- `structs` (array): An array of structures defined in the ABI.
-- `actions` (array): The actions that are defined in the ABI.
-- `tables` (array): The tables that are defined in the ABI.
-- `ricardian_clauses` (array): The ricardian clauses defined in the ABI.
-- `error_messages` (array): Possible error messages that are defined in the ABI.
-- `abi_extensions` (array): Any extensions to the ABI.
-
-### JSON-RPC Request Example
-
-```json
-{
- "account_name": "b1"
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "version": "eosio::abi/1.0",
- "types": [...],
- "structs": [...],
- "actions": [...],
- "tables": [...],
- "ricardian_clauses": [...],
- "error_messages": [...],
- "abi_extensions": [...]
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_account.md b/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_account.md
deleted file mode 100644
index 246da79a..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_account.md
+++ /dev/null
@@ -1,215 +0,0 @@
----
-title: "get_account"
-slug: "rpc-eos-get_account"
-excerpt: "Eos RPC"
-hidden: false
-metadata:
- description: "Eos RPC"
- image: []
- keywords: "eos, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:01 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### Overview
-
-The `get_account` returns an object containing various details about a specific account on the blockchain.
-
-{% tabs %}
-{% tab title="TypeScript/JavaScript" %}
-{% code overflow="wrap" lineNumbers="true" %}
-
-```typescript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Eos, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.EOS })
-
-const account = await tatum.rpc.getAccount({ accountName: 'b1' })
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-{% endtab %}
-{% endtabs %}
-
-### Example use cases:
-
-1. **Fetching Account Details:**
- Developers or users may need to retrieve specific details about an account, such as the account's balance, permissions, resource allocation (CPU, NET, and RAM usage), and other parameters.
-
-2. **Checking Resource Allocation and Consumption:**
- get_account can be used to monitor the amount of network, CPU, and RAM resources an account has allocated and consumed. This can help users manage their resources more effectively to ensure their dApps run smoothly.
-
-3. **Monitoring Staked and Unstaked Tokens:**
- Users can utilize this method to check the status of their tokens, whether they are staked or unstaked, and make decisions about staking and unstaking based on this information.
-
-### Request Parameters
-
-The `getAccount` method requires the following parameter:
-
-- `accountName` (string, required): A unique identifier assigned to every account. It is required to be 12 characters long and can only contain the characters a-z, 1-5, and . (dot).
-
-### Return Object
-
-The `get_account` method returns an object containing detailed information about the requested account. The object includes the following fields:
-
-- `account_name` (string): The name of the requested account.
-- `head_block_num` (integer): The most recent block number on the blockchain at the time of the request.
-- `head_block_time` (string): The timestamp of the most recent block on the blockchain at the time of the request.
-- `last_code_update` (string): The timestamp of the last time the account’s smart contract code was updated.
-- `created` (string): The timestamp of when the account was created.
-- `refund_request` (object): Details of any pending refund requests for the account due to unstaking resources.
-- `ram_quota` (integer): The total RAM allocated to the account.
-- `net_limit` (object): The available network bandwidth.
-- `cpu_limit` (object): CPU time for the account.
-- `total_resources` (object): A summary of the total resources (RAM, CPU, and NET) allocated to the account.
-- `core_liquid_balance` (string): The amount of liquid (available) core token (usually EOS) the account holds.
-- `self_delegated_bandwidth` (object): The amount of bandwidth the account has delegated to itself.
-- `net_weight` (integer): The amount of network bandwidth staked by the account.
-- `cpu_weight` (integer): CPU time staked by the account.
-- `ram_usage` (integer): The amount of RAM currently used by the account.
-- `privileged` (boolean): Indicates whether the account has elevated (privileged) permissions.
-- `permissions` (array): A list of the account’s permissions and their details, including the public keys associated with the account and any custom permission structures.
-- `voter_info` (object): Information related to the account’s voting, such as the proxies used, the number of votes, and the staked amount for voting.
-
-### JSON-RPC Request Example
-
-```json
-{
- "account_name": "string"
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "account_name": "b1",
- "head_block_num": 333261323,
- "head_block_time": "2023-09-27T12:52:25.000",
- "privileged": false,
- "last_code_update": "1970-01-01T00:00:00.000",
- "created": "2018-06-09T11:58:03.500",
- "core_liquid_balance": "0.2849 EOS",
- "ram_quota": 9487,
- "net_weight": "350078512340",
- "cpu_weight": "296624975145",
- "net_limit": {
- "used": 271,
- "available": "659675344495",
- "max": "659675344766",
- "last_usage_update_time": "2022-08-23T01:41:35.000",
- "current_used": 0
- },
- "cpu_limit": {
- "used": 4647,
- "available": 26734970,
- "max": 26739617,
- "last_usage_update_time": "2022-08-23T01:41:35.000",
- "current_used": 0
- },
- "ram_usage": 5010,
- "permissions": [
- {
- "perm_name": "active",
- "parent": "owner",
- "required_auth": {
- "threshold": 2,
- "keys": [
- {
- "key": "EOS5BUDFbb2erXiRP8qHQAgVboCHgHGesbCubUfgXYJhnYZKSqNbD",
- "weight": 1
- },
- {
- "key": "EOS6hQ6v8vut1V2giQCYha7J225GCzFJtF3o7fy8JYuN7k6fG4n23",
- "weight": 1
- },
- {
- "key": "EOS7RodmQofvAxgYBJzfNuwRKr6TWh5LbCBfB4uQ8tjrjQ8Ukkwqq",
- "weight": 1
- },
- {
- "key": "EOS7c9jHNgbtTMYgpXvmTb1kW61oH6kwfGioWk75ugDMhsywe6rWu",
- "weight": 1
- }
- ],
- "accounts": [],
- "waits": []
- },
- "linked_actions": []
- },
- {
- "perm_name": "owner",
- "parent": "",
- "required_auth": {
- "threshold": 2,
- "keys": [
- {
- "key": "EOS5BUDFbb2erXiRP8qHQAgVboCHgHGesbCubUfgXYJhnYZKSqNbD",
- "weight": 1
- },
- {
- "key": "EOS6hQ6v8vut1V2giQCYha7J225GCzFJtF3o7fy8JYuN7k6fG4n23",
- "weight": 1
- },
- {
- "key": "EOS7RodmQofvAxgYBJzfNuwRKr6TWh5LbCBfB4uQ8tjrjQ8Ukkwqq",
- "weight": 1
- },
- {
- "key": "EOS7c9jHNgbtTMYgpXvmTb1kW61oH6kwfGioWk75ugDMhsywe6rWu",
- "weight": 1
- }
- ],
- "accounts": [],
- "waits": []
- },
- "linked_actions": []
- }
- ],
- "total_resources": {
- "owner": "b1",
- "net_weight": "35007851.2340 EOS",
- "cpu_weight": "29662497.5145 EOS",
- "ram_bytes": 8087
- },
- "self_delegated_bandwidth": {
- "from": "b1",
- "to": "b1",
- "net_weight": "35007851.2340 EOS",
- "cpu_weight": "29662497.5145 EOS"
- },
- "refund_request": null,
- "voter_info": {
- "owner": "b1",
- "proxy": "",
- "producers": [],
- "staked": "646723487485",
- "last_vote_weight": "2768257912613634048.00000000000000000",
- "proxied_vote_weight": "0.00000000000000000",
- "is_proxy": 0,
- "flags1": 0,
- "reserved2": 0,
- "reserved3": "0.0000 EOS"
- },
- "rex_info": null,
- "subjective_cpu_bill_limit": {
- "used": 0,
- "available": 0,
- "max": 0,
- "last_usage_update_time": "2000-01-01T00:00:00.000",
- "current_used": 0
- },
- "eosio_any_linked_actions": []
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_accounts_by_authorizers.md b/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_accounts_by_authorizers.md
deleted file mode 100644
index 765bf9b5..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_accounts_by_authorizers.md
+++ /dev/null
@@ -1,87 +0,0 @@
----
-title: "get_accounts_by_authorizers"
-slug: "rpc-eos-get_accounts_by_authorizers"
-excerpt: "Eos RPC"
-hidden: false
-metadata:
- description: "Eos RPC"
- image: []
- keywords: "eos, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:05 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### Overview
-
-The `get_accounts_by_authorizers` method retrieves accounts associated with specific authorizers, serving as an essential tool for developers and users interested in understanding account access and control on the EOS blockchain.
-{% tabs %}
-{% tab title="TypeScript/JavaScript" %}
-{% code overflow="wrap" lineNumbers="true" %}
-
-```typescript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Eos, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.EOS })
-
-const response = await tatum.rpc.getAccountsByAuthorizers({
- accounts: ["eosio"]
-})
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-{% endtab %}
-{% endtabs %}
-
-### Example use cases:
-
-1. **Account Access Analysis:**
- Developers can utilize this method to discern which accounts have access through specific authorizers, fortifying access control and security management.
-
-2. **Permission Management:**
- Users managing multiple accounts can benefit from this method by identifying which accounts are controlled by specific authorizers, optimizing permission management processes.
-
-3. **Enhanced Account Retrieval:**
- This method facilitates the retrieval of accounts based on specific authorizers, fostering efficient data interaction and management on the EOS blockchain.
-
-### Request Parameters
-
-The `getAccountsByAuthorizers` method requires the following parameters in the request body:
-
-- `keys` (array of strings): An array of public keys used to retrieve accounts.
-- `accounts` (array of strings): An array of account names used to retrieve accounts.
- - `actor` (string, required): Name of the actor.
- - `permission` (string, required): Specifies the permission name.
-
-### Return Object
-
-The `get_accounts_by_authorizers` method typically returns an object containing:
-
-- `accounts` (array of strings): An array of account names associated with the provided authorizers.
-
-### JSON-RPC Request Example
-
-```json
-{
- "keys": ["EOS6MRy..."],
- "accounts": ["eosio"]
-}
-```
-
-### JSON-RPC Reponse Example
-
-```json
-{
- "accounts": ["account1", "account2"]
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_activated_protocol_features.md b/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_activated_protocol_features.md
deleted file mode 100644
index a4f50057..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_activated_protocol_features.md
+++ /dev/null
@@ -1,100 +0,0 @@
----
-title: "get_activated_protocol_features"
-slug: "rpc-eos-get_activated_protocol_features"
-excerpt: "Eos RPC"
-hidden: false
-metadata:
- description: "Eos RPC"
- image: []
- keywords: "eos, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:05 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### Overview
-
-The `get_activated_protocol_features` method retrieves the activated protocol features for a producer node in the EOS blockchain. This method is crucial for developers and block producers to identify and understand the protocol features activated on a node, ensuring proper configuration and management of producer nodes.
-{% tabs %}
-{% tab title="TypeScript/JavaScript" %}
-{% code overflow="wrap" lineNumbers="true" %}
-
-```typescript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Eos, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.EOS })
-
-const response = await tatum.rpc.getActivatedProtocolFeatures({
- lowerBound: 0,
- upperBound: 100,
- limit: 2,
- searchByBlockNum: true,
- reverse: false
-})
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-{% endtab %}
-{% endtabs %}
-
-### Example use cases:
-
-1. **Producer Node Management:**
- Developers and block producers can utilize this method to analyze and manage the activated protocol features, ensuring the optimal configuration of producer nodes.
-
-2. **Protocol Feature Exploration:**
- This method allows users and developers to explore and understand the activated protocol features on the blockchain, enhancing their interaction and experience with the EOS blockchain.
-
-3. **Enhanced Feature Retrieval:**
- The method provides extensive filtering options for retrieving activated protocol features, enabling users to efficiently manage and interact with the protocol features.
-
-### Request Parameters
-
-The `getActivatedProtocolFeatures` method requires the following parameters in the request body:
-
-- `params` (object, required): Defines the filters to retrieve the protocol features by.
- - `lowerBound` (integer): Lower bound.
- - `upperBound` (integer): Upper bound.
- - `limit` (integer, default: 10): The limit.
- - `searchByBlockNum` (boolean, required): Flag to indicate whether it has to search by block number.
- - `reverse` (boolean, required): Flag to indicate whether it has to search in reverse.
-
-### Return Object
-
-The `get_activated_protocol_features` method returns an object with the following properties:
-
-- `activated_protocol_features` (Array of strings, required): Variant type, an array of strings representing the activated protocol features.
-- `more` (integer): Represents whether there are more activated protocol features to be fetched. If there's `more` activated protocol features than the input parameter limit requested, it returns the ordinal of the next activated protocol feature which was not returned, otherwise, it returns zero.
-
-### JSON-RPC Request Example
-
-```json
-{
- "params": {
- "lower_bound": 0,
- "upper_bound": 100,
- "limit": 10,
- "search_by_block_num": true,
- "reverse": false
- }
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "activated_protocol_features": ["0a1b2c3d4e5f6789abcdef10", "1a2b3c4d5e6f7890abcdef01"],
- "more": 1
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_block.md b/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_block.md
deleted file mode 100644
index a37576d8..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_block.md
+++ /dev/null
@@ -1,125 +0,0 @@
----
-title: "get_block"
-slug: "rpc-eos-get_block"
-excerpt: "Eos RPC"
-hidden: false
-metadata:
- description: "Eos RPC"
- image: []
- keywords: "eos, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:42 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-{% hint style="warning" %}
-Please note that you are able to get data only from block number 260742168 and newer.
-{% endhint %}
-
-### Overview
-
-The `get_block` method returns an object containing various details about a specific block on the blockchain, providing block number or block id in request.
-
-{% tabs %}
-{% tab title="TypeScript/JavaScript" %}
-{% code overflow="wrap" lineNumbers="true" %}
-
-```typescript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Eos, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.EOS })
-
-const block = await tatum.rpc.getBlock({ blockNumOrId: '260742168' })
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-{% endtab %}
-{% endtabs %}
-
-### Example use cases:
-
-1. **Block Verification:**
- Developers or validators might use the `get_block` method to fetch specific block details for the purpose of verifying block information. It allows the comparison of block data retrieved from different nodes to ensure data consistency and integrity across the network.
-
-2. **Transaction Confirmation:**
- Users and services might utilize the `get_block` method to confirm transaction inclusion within a block. By examining the transactions field of the returned block object, users can ascertain whether a specific transaction has been included and, consequently, confirm its successful execution.
-
-3. **Data Analysis and Chain Exploration:**
- Researchers and analysts can employ the `get_block` method to retrieve detailed block data for analytical purposes, exploring block and transaction patterns, studying network activity, and gaining insights into blockchain operations and behavior.
-
-### Request Parameters
-
-The `getBlock` method requires the following parameter in the request body:
-
-- `blockNumOrId` (string, required): Provide either a block number or a block ID.
-
-### Return Object
-
-The `get_block` method returns an object containing the following parameters:
-
-- `timestamp` (string): Date/time string in the format YYYY-MM-DDTHH:MM:SS.sss.
-- `producer` (string): The account name of the block producer.
-- `confirmed` (integer): Number of prior blocks confirmed by this block producer in the current schedule.
-- `previous` (string, Sha256): The ID of the block that immediately precedes this one.
-- `transaction_mroot` (string, Sha256): The Merkle root of the transactions included in this block.
-- `action_mroot` (string, Sha256): The Merkle root of the actions included in this block.
-- `schedule_version` (integer): Number of times the producer schedule has changed since genesis.
-- `new_producers` (nullable array of objects): Information about any new block producers that have been elected in this block.
-- `header_extensions` (array of integers or strings): Any extensions to the block header.
-- `new_protocol_features` (array of objects): List of new protocol features.
-- `producer_signature` (string, Signature): Base58 encoded EOSIO cryptographic signature.
-- `transactions` (array of objects): List of valid transaction receipts included in block.
-- `block_extensions` (array of integers or strings): Any extensions to this block.
-- `id` (string, Sha256): The ID of this block.
-- `block_num` (integer): The height of this block in the chain.
-- `ref_block_prefix` (integer): 32-bit portion of block ID.
-
-### JSON-RPC Request Example
-
-```json
-{
- "block_num_or_id": "260742168"
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "timestamp": "2023-09-26T16:50:32.500",
- "producer": "eosio",
- "confirmed": 0,
- "previous": "0000004bc2b4483cfad9a2aeb93196c8c47744cc553d5ed30b71058e9aa2e410",
- "transaction_mroot": "0000000000000000000000000000000000000000000000000000000000000000",
- "action_mroot": "0e6e36f2db9fc3f7a7d3f1a1a7fd2aef9b9b9827060bbe5a8811e0e86e7d7d3a",
- "schedule_version": 0,
- "new_producers": null,
- "header_extensions": [],
- "new_protocol_features": [],
- "producer_signature": "SIG_K1_Jyv4wSc8yr5UWwLq9m7eKzWEVJgEo9rzUq9Zt49gCQjzjxrtBQyd1ZQsZt5Ge9wXCUsMxra1mHLJyZXFqSRcR5wSEDF1",
- "transactions": [
- {
- "status": "executed",
- "cpu_usage_us": 758,
- "net_usage_words": 14,
- "trx": [ "2", "e4be63d97b553a5d7b2c9b0
-
-d21e753b69a3c0bf4a7f9f0b2ff806c16d8a8e959" ]
- }
- ],
- "block_extensions": [],
- "id": "0000004cc2b4483cfad9a2aeb93196c8c47744cc553d5ed30b71058e9aa2e410",
- "block_num": 76,
- "ref_block_prefix": 3708016389
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_block_info.md b/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_block_info.md
deleted file mode 100644
index 2ad8f000..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_block_info.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: "get_block_info"
-slug: "rpc-eos-get_block_info"
-excerpt: "Eos RPC"
-hidden: false
-metadata:
- description: "Eos RPC"
- image: []
- keywords: "eos, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:04 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-{% hint style="warning" %}
-Please note that you are able to get data only from block number 260742168 and newer.
-{% endhint %}
-
-### Overview
-
-The `get_block_info` method retrieves crucial information about a specific block in the EOS blockchain. It returns an object containing details such as block time, block number, previous block ID, producer, and transaction count. Similar to `get_block` but returns a fixed-size smaller subset of the block data.
-
-{% tabs %}
-{% tab title="TypeScript/JavaScript" %}
-{% code overflow="wrap" lineNumbers="true" %}
-
-```typescript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Eos, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.EOS })
-
-const blockInfo = await tatum.rpc.getBlockInfo()
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-{% endtab %}
-{% endtabs %}
-
-### Example use cases:
-
-1. **Fetching Specific Block Details:**
- Developers and users may utilize the `get_block_info` method to gather information about a particular block, aiding in debugging or validating blockchain states and transactions.
-
-2. **Block Verification:**
- Validators and network participants can employ this method to verify the integrity and authenticity of a block, ensuring the security and reliability of the network.
-
-3. **Data Analysis and Chain Exploration:**
- Blockchain analysts and enthusiasts might use `get_block_info` to study block patterns and transaction activities, gaining insights into the network’s operations and behaviors.
-
-### Request Parameters
-
-The `getBlockInfo` method requires the following parameter in the request body:
-
-- `blockNumOrId` (string, required): It could be either a block number or a block ID.
-
-### Return Object
-
-The `get_block_info` method returns an object containing the following parameters:
-
-- `block_num` (integer): The block number.
-- `ref_block_num` (integer): The reference block number.
-- `id` (string): The ID of the block.
-- `timestamp` (string): The timestamp when the block was produced.
-- `producer` (string): The name of the block producer.
-- `confirmed` (integer): The number of confirmed transactions in the block.
-- `previous` (string): The ID of the previous block.
-- `transaction_mroot` (string): The Merkle root of the transactions in the block.
-- `action_mroot` (string): The Merkle root of the actions in the block.
-- `schedule_version` (integer): The schedule version.
-- `producer_signature` (string): The signature of the block producer.
-- `ref_block_prefix` (integer): The reference block prefix.
-
-### JSON-RPC Request Example
-
-```json
-{
- "block_num_or_id": "260742168"
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "block_num": 260742168,
- "ref_block_num": 39960,
- "id": "0f8a9c180c996f9a88e463ca22428b3ed13c7ddc5ad09fc9c77c3c635ef9872b",
- "timestamp": "2022-08-03T16:00:36.000",
- "producer": "eosasia11111",
- "confirmed": 240,
- "previous": "0f8a9c1787cb055ab97b9beae18b762d6c3b4cfebf25060ddcc47213a2ef64d2",
- "transaction_mroot": "03313763ba0a854edbd46517bc515d090ff8e64c842e19ab91fb61f6f7bb0ce8",
- "action_mroot": "7c91b3be9fab14fe589a99312c6366d4077f49a80fd1f0ad4077f7575bbb4fe8",
- "schedule_version": 2023,
- "producer_signature": "SIG_K1_KkDoLCNaRyV62pxoUW8XQDgbZ31TrvSEDVebKFrL6fU8EsVkEFL7Wx8YMXyx2ydqY9KhPSYKQZD6dtD2cnbBmsETsZsdxt",
- "ref_block_prefix": 3395544200
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_code.md b/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_code.md
deleted file mode 100644
index 9ab3b292..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_code.md
+++ /dev/null
@@ -1,95 +0,0 @@
----
-title: "get_code"
-slug: "rpc-eos-get_code"
-excerpt: "Eos RPC"
-hidden: false
-metadata:
- description: "Eos RPC"
- image: []
- keywords: "eos, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:01 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### Overview
-
-The `get_code` method returns an object containing the smart contract WASM code for a specified account on the EOS blockchain. This method is paramount for developers who are looking to analyze or understand the WASM code of deployed smart contracts, enabling an in-depth interaction and integration with the smart contracts.
-{% tabs %}
-{% tab title="TypeScript/JavaScript" %}
-{% code overflow="wrap" lineNumbers="true" %}
-
-```typescript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Eos, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.EOS })
-
-const response = await tatum.rpc.getCode({
- accountName: "eosio.token",
- codeAsWasm: 1
-})
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-{% endtab %}
-{% endtabs %}
-
-### Example use cases:
-
-1. **Smart Contract Analysis:**
- Developers use this method to retrieve and analyze the WASM code of smart contracts, allowing for comprehensive understanding and debugging of the contract logic.
-
-2. **WASM Code Inspection:**
- This method is vital for users and developers wishing to inspect the WASM code, ensuring the contract's integrity, functionality, and security.
-
-3. **Enhanced Integration and Interaction:**
- Retrieving the WASM code facilitates seamless integration and interaction with smart contracts, ensuring proper deployment, execution, and management of contracts on the EOS blockchain.
-
-### Request Parameters
-
-The `getCode` method requires the following parameters in the request body:
-
-- `accountName` (string, required): The name of the account whose smart contract WASM code needs to be retrieved. Acceptable types are NamePrivileged, NameBasic, NameBid, and NameCatchAll.
-- `codeAsWasm` (integer, required): This must be 1 (true).
-
-### Return Object
-
-The `get_code` method returns an object containing:
-
-- `name` (string): The name of the account from which the WASM code was retrieved. Acceptable types are NamePrivileged, NameBasic, NameBid, and NameCatchAll.
-- `code_hash` (string): A Sha256 hash representing the WASM code of the retrieved smart contract.
-- `wast` (string): The WebAssembly text format representation of the smart contract.
-- `wasm` (string): The WebAssembly binary representation of the smart contract.
-- `abi` (object): The ABI (Application Binary Interface) of the smart contract, representing the binary representation of the contract's interface.
-
-### JSON-RPC Request Example
-
-```json
-{
- "accountName": "eosio.token",
- "codeAsWasm": 1
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "name": "eosio.token",
- "code_hash": "a1b2c3d4e5f67890abcdef1234567890abcdef1234567890abcdef1234567890ab",
- "wast": "... (WAST string) ...",
- "wasm": "... (WASM binary string) ...",
- "abi": { ... (ABI object) ... }
-}
-
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_currency_balance.md b/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_currency_balance.md
deleted file mode 100644
index 84220b6a..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_currency_balance.md
+++ /dev/null
@@ -1,90 +0,0 @@
----
-title: "get_currency_balance"
-slug: "rpc-eos-get_currency_balance"
-excerpt: "Eos RPC"
-hidden: false
-metadata:
- description: "Eos RPC"
- image: []
- keywords: "eos, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:44 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### Overview
-
-The `get_currency_balance` method is used to retrieve the balance of a specific currency/token for a given account on the EOS blockchain. This method is essential for users and developers who wish to query and manage account balances, ensuring accurate and up-to-date financial data.
-
-{% tabs %}
-{% tab title="TypeScript/JavaScript" %}
-{% code overflow="wrap" lineNumbers="true" %}
-
-```typescript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Eos, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.EOS })
-
-const response = await tatum.rpc.getCurrencyBalance({
- account: 'eosio',
- code: 'eosio.token',
- symbol: 'EOS'
-})
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-{% endtab %}
-{% endtabs %}
-
-### Example use cases:
-
-1. **Balance Querying:**
- Users and developers can utilize the `get_currency_balance` method to query the balances of specific currencies or tokens, enabling effective account management and financial planning.
-
-2. **Financial Management:**
- This method is pivotal for financial management in decentralized applications, allowing for the implementation of features related to balance checking, fund transfer validations, and more.
-
-3. **Smart Contract Interaction:**
- Developers can leverage this method to interact with token contracts to retrieve the balance of an account, facilitating the development of functionalities around token transactions and balance validations in dApps.
-
-### Request Parameters
-
-The `getCurrencyBalance` method requires the following parameters in the request body:
-
-- `account` (string, required): The name of the account for which the balance is being requested.
-- `code` (string, required): The smart contract that operates the currency.
-- `symbol` (string, optional): The symbol of the currency/token. If not provided, the balances of all tokens available under the smart contract will be returned.
-
-### Return Object
-
-Upon a successful request, the method returns an array containing the balances of the specified currency/token for the given account:
-
-- Each item in the array represents a balance in the format `"amount SYMBOL"` (e.g., `"100.0000 EOS"`).
-
-### JSON-RPC Request Example
-
-```json
-{
- "account": "eosio",
- "code": "eosio.token",
- "symbol": "EOS"
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-[
- "1667.0290 EOS"
-]
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_currency_stats.md b/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_currency_stats.md
deleted file mode 100644
index 0d1957ec..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_currency_stats.md
+++ /dev/null
@@ -1,93 +0,0 @@
----
-title: "get_currency_stats"
-slug: "rpc-eos-get_currency_stats"
-excerpt: "Eos RPC"
-hidden: false
-metadata:
- description: "Eos RPC"
- image: []
- keywords: "eos, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:03 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### Overview
-
-The `get_currency_stats` method is utilized to retrieve the statistics for a specific currency on the EOS blockchain. By employing this method, users and developers can obtain crucial information about a currency, such as its supply, maximum supply, and issuer, thereby enabling in-depth analysis and insights into the currency's status and distribution.
-
-{% tabs %}
-{% tab title="TypeScript/JavaScript" %}
-{% code overflow="wrap" lineNumbers="true" %}
-
-```typescript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Eos, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.EOS })
-
-const response = await tatum.rpc.getCurrencyStats({
- code: 'eosio.token',
- symbol: 'EOS'
-})
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-{% endtab %}
-{% endtabs %}
-
-### Example use cases:
-
-1. **Token Analysis:**
- Individuals and analysts can utilize the `get_currency_stats` method to gather comprehensive details about a token's supply and issuer, facilitating profound analysis and research on the token’s characteristics and distribution.
-
-2. **Smart Contract Interaction:**
- Developers can use this method to obtain necessary information about a token, which can aid in interacting efficiently with smart contracts that deal with tokens, for operations like transferring tokens or querying balances.
-
-3. **Market Analysis:**
- `get_currency_stats` is instrumental for acquiring essential details about a token, which are critical for performing market analysis. This enables users and potential investors to make informed and insightful decisions based on the available token data.
-
-### Request Parameters
-
-The `getCurrencyStats` method requires the following parameters in the request body:
-
-- `code` (string, required): The contract that operates the token.
-- `symbol` (string, required): The symbol of the token for which the statistics are being requested.
-
-### Return Object
-
-The `get_currency_stats` method typically returns an object containing the statistics of the requested currency. This object includes:
-
-- `supply` (string): The total supply of the token in circulation.
-- `max_supply` (string): The maximum supply of the token that can ever be created.
-- `issuer` (string): The account name of the issuer of the token.
-
-### JSON-RPC Request Example
-
-```json
-{
- "code": "eosio.token",
- "symbol": "EOS"
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "EOS": {
- "supply": "1168690795.8555 EOS",
- "max_supply": "10000000000.0000 EOS",
- "issuer": "eosio"
- }
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_info.md b/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_info.md
deleted file mode 100644
index a3d32abb..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_info.md
+++ /dev/null
@@ -1,104 +0,0 @@
----
-title: "get_info"
-slug: "rpc-eos-get_info"
-excerpt: "Eos RPC"
-hidden: false
-metadata:
- description: "Eos RPC"
- image: []
- keywords: "eos, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:00 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### Overview
-
-The `get_info` RPC method in the EOS blockchain is used to retrieve various details about the blockchain's state, such as the head block, the last irreversible block, and the chain ID. It is one of the most fundamental RPC calls in the EOSIO blockchain, providing essential information about the network's status.
-{% tabs %}
-{% tab title="TypeScript/JavaScript" %}
-{% code overflow="wrap" lineNumbers="true" %}
-
-```typescript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Eos, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.EOS })
-
-const info = await tatum.rpc.getInfo()
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-{% endtab %}
-{% endtabs %}
-
-### Example use cases:
-
-1. **Checking Blockchain Status:**
- Developers and users often use the `get_info` method to quickly check the status of the EOS blockchain, such as the head block number and the last irreversible block number, to ensure they are interacting with the most recent and confirmed state of the blockchain.
-
-2. **Synchronization and Validation:**
- For node operators and block producers, `get_info` is crucial to verify that their node is synchronized with the network, and to compare the `chain_id` and other details to ensure they are on the correct chain and avoid forks.
-
-3. **Development and Debugging:**
- Developers frequently use `get_info` during the development and debugging of dApps and smart contracts, to fetch real-time information about the blockchain, validate transactions, and test the behavior of their applications against the current state of the blockchain.
-
-### Request Parameters
-
-The `getInfo` method does not require any parameters; it is a simple GET request to the endpoint.
-
-### Return Object
-
-The `get_info` method returns an object with the following response parameters:
-
-- `server_version` (string): The version of the nodeos software running on the node.
-- `chain_id` (string): The unique identifier for the EOSIO blockchain.
-- `head_block_num` (integer): The most recent block number on the blockchain.
-- `head_block_id` (string): The unique identifier of the head block.
-- `head_block_time` (string): The timestamp of when the head block was produced.
-- `head_block_producer` (string): The name of the block producer that produced the head block.
-- `last_irreversible_block_num` (integer): The most recent block that has been irreversibly confirmed on the blockchain.
-- `last_irreversible_block_id` (string): The unique identifier of the last irreversible block.
-- `virtual_block_cpu_limit` (integer): The current limit on CPU usage for virtual blocks.
-- `virtual_block_net_limit` (integer): The current limit on NET usage for virtual blocks.
-- `block_cpu_limit` (integer): The current limit on CPU usage for blocks.
-- `block_net_limit` (integer): The current limit on NET usage for blocks.
-- `server_version_string` (string): The server version as a string.
-- `fork_db_head_block_num` (integer): Sequential block number representing the best known head in the fork database tree.
-- `fork_db_head_block_id` (string): Hash representing the best known head in the fork database tree.
-
-### JSON-RPC Response Example
-
-```json
-{
- "server_version": "7e1ad13e",
- "chain_id": "aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906",
- "head_block_num": 333261268,
- "last_irreversible_block_num": 333260936,
- "last_irreversible_block_id": "13dd2888c6e933ac455978baf53554605d95e0e2d2abd0c1159ddb218936fe03",
- "head_block_id": "13dd29d4aa69b67d138d0bbb82ee4d1de74ec0cd404d58902381ea9d5bdbff67",
- "head_block_time": "2023-09-27T12:51:57.500",
- "head_block_producer": "eoseouldotio",
- "virtual_block_cpu_limit": 200000,
- "virtual_block_net_limit": 1048576000,
- "block_cpu_limit": 200000,
- "block_net_limit": 1048576,
- "server_version_string": "v4.0.4",
- "fork_db_head_block_num": 333261268,
- "fork_db_head_block_id": "13dd29d4aa69b67d138d0bbb82ee4d1de74ec0cd404d58902381ea9d5bdbff67",
- "server_full_version_string": "v4.0.4-7e1ad13e1e98b1e0703d0ea072b4fca5419cfdbe",
- "total_cpu_weight": "383377176232761",
- "total_net_weight": "96156545705220",
- "earliest_available_block_num": 260742168,
- "last_irreversible_block_time": "2023-09-27T12:49:11.500"
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_producers.md b/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_producers.md
deleted file mode 100644
index f4778c9b..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_producers.md
+++ /dev/null
@@ -1,94 +0,0 @@
----
-title: "get_producers"
-slug: "rpc-eos-get_producers"
-excerpt: "Eos RPC"
-hidden: false
-metadata:
- description: "Eos RPC"
- image: []
- keywords: "eos, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:41 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### Overview
-
-The `get_producers` method is designed to retrieve a list of producers from the EOS blockchain. Producers are essential entities in the EOS network responsible for producing blocks, and this method provides valuable insights into their details and statuses, including active, pending, and proposed producers.
-
-{% tabs %}
-{% tab title="TypeScript/JavaScript" %}
-{% code overflow="wrap" lineNumbers="true" %}
-
-```typescript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Eos, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.EOS })
-
-const response = await tatum.rpc.getProducers({
- limit: '10',
- lowerBound: '0',
- json: true
-})
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-{% endtab %}
-{% endtabs %}
-
-### Example use cases:
-
-1. **Monitoring Network Health:**
- Developers and network monitors can use the `get_producers` method to observe the active, pending, and proposed producers, assessing the overall health and consensus of the network.
-
-2. **Network Statistics:**
- This method aids in gathering statistical data about the network, including the number and statuses of producers, facilitating enhanced network analysis and management.
-
-3. **Voting and Governance:**
- `get_producers` can be instrumental for users involved in EOS governance, helping them to make informed decisions by providing a current list of producers along with their statuses.
-
-### Request Parameters
-
-The `get_producers` method requires the following parameters in the request body:
-
-- `limit` (string, required): The total number of producers to retrieve.
-- `lowerBound` (string, required): In conjunction with limit, it can be used to paginate through the results. For example, limit=10 and lower_bound=10 would represent page 2.
-- `json` (boolean, required): Indicates whether the result should be returned in JSON format.
-
-### Return Object
-
-The `getProducers` method typically returns an object containing lists of active, pending, and proposed producers:
-
-- `active` (Array of objects, nullable): A list of currently active producers.
-- `pending` (Array of objects, nullable): A list of producers that are pending.
-- `proposed` (Array of objects, nullable): A list of producers that are proposed.
-
-### JSON-RPC Request Example
-
-```json
-{
- "limit": "10",
- "lower_bound": "0",
- "json": true
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "active": [...],
- "pending": [...],
- "proposed": [...]
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_raw_abi.md b/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_raw_abi.md
deleted file mode 100644
index 1c279090..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_raw_abi.md
+++ /dev/null
@@ -1,86 +0,0 @@
----
-title: "get_raw_abi"
-slug: "rpc-eos-get_raw_abi"
-excerpt: "Eos RPC"
-hidden: false
-metadata:
- description: "Eos RPC"
- image: []
- keywords: "eos, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:06 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### Overview
-
-The `get_raw_abi` method is used to fetch the raw, serialized ABI (Application Binary Interface) for a specified account, providing essential details needed for interacting with smart contracts on the EOS network.
-
-{% tabs %}
-{% tab title="TypeScript/JavaScript" %}
-{% code overflow="wrap" lineNumbers="true" %}
-
-```typescript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Eos, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.EOS })
-
-const rawAbi = await tatum.rpc.getRawAbi({ accountName: 'b1' })
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-{% endtab %}
-{% endtabs %}
-
-### Example use cases:
-
-1. **Smart Contract Interaction:**
- Developers or users may use the `get_raw_abi` method to obtain the raw ABI of a smart contract, essential for decoding binary data and enabling effective interaction with the contract.
-2. **ABI Analysis and Verification:**
- The method allows developers and analysts to study and analyze the ABI of a contract, verify its integrity, and understand its structure and methods by comparing the retrieved `abi_hash` with known hash values.
-3. **Development and Debugging:**
- This method is crucial for developers during the development and debugging phases, enabling quick access to and assessment of the ABI, ensuring alignment with the contract’s intended design and functionality.
-
-### Request Parameters
-
-The `getRawAbi` method has one parameter:
-
-- `accountName` (string, required): The unique EOSIO account name of the smart contract whose ABI is to be retrieved.
-
-### Return Object
-
-The `get_raw_abi` method returns an object with the following parameters:
-
-- `account_name` (string, required): The name of the account whose ABI was retrieved.
-- `code_hash` (string, required): The hash of the smart contract code.
-- `abi_hash` (string, required): The hash of the ABI of the smart contract.
-- `abi` (string, required): The raw, serialized ABI data.
-
-### JSON-RPC Request Example
-
-```json
-{
- "account_name": "b1"
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "account_name": "b1",
- "code_hash": "0000000000000000000000000000000000000000000000000000000000000000",
- "abi_hash": "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855",
- "abi": ""
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_raw_code_and_abi.md b/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_raw_code_and_abi.md
deleted file mode 100644
index efa165cb..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_raw_code_and_abi.md
+++ /dev/null
@@ -1,86 +0,0 @@
----
-title: "get_raw_code_and_abi"
-slug: "rpc-eos-get_raw_code_and_abi"
-excerpt: "Eos RPC"
-hidden: false
-metadata:
- description: "Eos RPC"
- image: []
- keywords: "eos, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:02 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### Overview
-
-The `get_raw_code_and_abi` method is used to retrieve both the raw code and the ABI (Application Binary Interface) for a contract, based on the account name. This is pivotal for developers who wish to interact with, decode, and understand the underlying code and interfaces of smart contracts deployed on the EOS blockchain.
-
-{% tabs %}
-{% tab title="TypeScript/JavaScript" %}
-{% code overflow="wrap" lineNumbers="true" %}
-
-```typescript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Eos, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.EOS })
-
-const response = await tatum.rpc.getRawCodeAndAbi({ accountName: 'eosio' })
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-{% endtab %}
-{% endtabs %}
-
-### Example use cases:
-
-1. **Understanding Smart Contracts:**
- Developers can use the `get_raw_code_and_abi` method to gain insights into the raw code and ABI of smart contracts, enabling them to understand and interact with the contract's methods, state variables, and structures more effectively.
-
-2. **Development and Debugging:**
- This method is crucial for developers in the development and debugging phases, allowing for precise interaction and validation of the contract's code and interfaces, thereby facilitating a smoother development process.
-
-3. **Enhanced Interaction with Smart Contracts:**
- With the detailed insight provided by this method, developers can optimize their interaction with the smart contracts, making the development of decentralized applications more efficient and robust.
-
-### Request Parameters
-
-The `geRrawCodeAndAbi` method requires the following parameter in the request body:
-
-- `accountName` (string, required): This can be `NamePrivileged`, `NameBasic`, `NameBid`, or `NameCatchAll`. It represents the name of the account for which the raw code and ABI are being requested.
-
-### Return Object
-
-Upon a successful request, the method returns an object containing the following details:
-
-- `account_name` (string): Name of the account.
-- `wasm` (string): The base64 encoded WebAssembly (WASM) code of the smart contract.
-- `abi` (string): The base64 encoded ABI of the smart contract.
-
-### JSON-RPC Request Example
-
-```json
-{
- "account_name": "eosio"
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "account_name": "eosio",
- "wasm": "base64EncodedWASM",
- "abi": "base64EncodedABI"
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_required_keys.md b/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_required_keys.md
deleted file mode 100644
index 5281e802..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_required_keys.md
+++ /dev/null
@@ -1,107 +0,0 @@
----
-title: "get_required_keys"
-slug: "rpc-eos-get_required_keys"
-excerpt: "Eos RPC"
-hidden: false
-metadata:
- description: "Eos RPC"
- image: []
- keywords: "eos, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:06 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### Overview
-
-The `get_required_keys` method returns the required keys that are needed to sign a transaction. This feature is extremely valuable for users and developers aiming to ensure secure and accurate transaction signatures, thus maintaining the integrity of transactions within the EOS blockchain.
-
-{% tabs %}
-{% tab title="TypeScript/JavaScript" %}
-{% code overflow="wrap" lineNumbers="true" %}
-
-```typescript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Eos, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.EOS })
-
-const response = await tatum.rpc.getRequiredKeys({
- transaction: { /* Transaction Object. See request params below. */ },
- availableKeys: ["EOS..."]
-})
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-{% endtab %}
-{% endtabs %}
-
-### Example use cases:
-
-1. **Secure Transaction Signing:**
- Users and developers can use the `get_required_keys` method to identify the specific keys required to sign a transaction, enhancing the security and accuracy of the signing process and avoiding unauthorized or faulty transactions.
-
-2. **Blockchain Interaction:**
- This method is crucial for interactions and operations on the EOS blockchain where transactions are involved, ensuring that only the correct keys are utilized to sign the transactions, maintaining the validity and authenticity of the transactions.
-
-3. **Smart Contract Interaction:**
- Developers interacting with smart contracts on the EOS blockchain can leverage this method to determine the appropriate keys to sign transactions related to smart contract execution, thereby maintaining the correctness and reliability of contract interactions.
-
-### Request Parameters
-
-The `getRequiredKeys` method mandates the following parameters in the request body:
-
-- `transaction` (object, required): Represents the transaction that is set to be signed.
- - `expiration`: (string, required) - A date and time indicating when the transaction expires.
- - `refBlockNum`: (number, required) - The reference block number.
- - `refBlockPrefix`: (number, required) - The reference block prefix.
- - `maxNetUsageWords`: (string | number, required) - The maximum net usage words.
- - `maxCpuUsageMs`: (string | number, required) - The maximum CPU usage in milliseconds.
- - `delaySec`: (number, required) - The delay in seconds.
- - `contextFreeActions`: (Array of Action, required) - Context-free actions.
- - `account`: (string, required) - EOSIO account name.
- - `name`: (string, required) - Name of the action.
- - `authorization`: (Array of objects, required)
- - `actor`: (string, required) - EOSIO account name that is the actor.
- - `permission`: (string, required) - Permission level for the actor.
- - `data`: (object, required)
- - `hexData`: (string, required) - Hexadecimal representation of the data for the action.
- - `actions` (Array of objects, required)
- - `account`: (string, required) - EOSIO account name.
- - `name`: (string, required) - Name of the action.
- - `authorization` (Array of objects, required)
- - `actor`: (string, required) - EOSIO account name that is the actor.
- - `permission`: (string, required) - Permission level for the actor.
- - `data`: (object, required)
- - `hexData`: (string, required) - Hexadecimal representation of the data for the action.
-- `availableKeys` (array of strings, required): Represents the available public keys.
-
-### Return Object
-
-The `get_required_keys` method typically returns an object containing the keys that are required to sign the transaction.
-
-### JSON-RPC Request Example
-
-```json
-{
- "transaction": { /* Transaction Object */ },
- "available_keys": ["EOS..."]
-}
-```
-
-## JSON-RPC Response Example
-
-```json
-{
- "required_keys": ["EOS..."]
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_table_by_scope.md b/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_table_by_scope.md
deleted file mode 100644
index acf32ea6..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_table_by_scope.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: "get_table_by_scope"
-slug: "rpc-eos-get_table_by_scope"
-excerpt: "Eos RPC"
-hidden: false
-metadata:
- description: "Eos RPC"
- image: []
- keywords: "eos, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:02 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### Overview
-
-The `get_table_by_scope` method retrieves the table scope for a given contract in the EOS blockchain. It is essential for developers and users who interact with smart contracts and need to query table data associated with a specific contract. This method provides flexibility by allowing filtered and limited results, making it highly adaptable to various use cases.
-{% tabs %}
-{% tab title="TypeScript/JavaScript" %}
-{% code overflow="wrap" lineNumbers="true" %}
-
-```typescript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Eos, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.EOS })
-
-const response = await tatum.rpc.getTableByScope({
- code: 'eosio.token',
- table: 'accounts',
- lowerBound: '0',
- upperBound: '100',
- limit: 10,
- reverse: false,
- show_payer: false
-})
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-{% endtab %}
-{% endtabs %}
-
-### Example use cases:
-
-1. **Smart Contract Interaction:**
- Developers can use this method to interact with and retrieve table data for a specific contract, which is crucial for accurate and efficient contract interaction and validation.
-
-2. **Data Analysis and Management:**
- By retrieving table scope, users and developers can perform detailed data analysis and management, which aids in optimizing and improving smart contract functionalities.
-
-3. **Enhanced Querying:**
- The flexible filtering options provided by this method facilitate enhanced querying capabilities, allowing users to retrieve precise and relevant data according to their requirements.
-
-### Request Parameters
-
-The `getTableByScope` method requires the following parameters in the request body:
-
-- `code` (string, required): The name of the contract to return table data for.
-- `table` (string): To filter the results by table.
-- `lowerBound` (string): Filters results to return the first element that is not less than the provided value in set.
-- `upperBound` (string): Filters results to return the first element that is greater than the provided value in set.
-- `limit` (integer , default: 10): Limit the number of results returned.
-- `reverse` (boolean, default: false): Reverse the order of returned results.
-- `showPayer` (boolean, default: false): Show RAM payer.
-
-### Return Object
-
-The `get_table_by_scope` method typically returns an array containing the requested table scope details related to the specified contract.
-
-### JSON-RPC Request Example
-
-```json
-{
- "code": "eosio.token",
- "table": "accounts",
- "lower_bound": "0",
- "upper_bound": "100",
- "limit": 10,
- "reverse": false,
- "show_payer": false
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "rows": [
- {
- "code": "eosio.token",
- "scope": "........ehbo5",
- "table": "stat",
- "payer": "eosio.token",
- "count": 1
- }
- ],
- "more": "111222333445"
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_table_rows.md b/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_table_rows.md
deleted file mode 100644
index 2e06ef8c..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-get_table_rows.md
+++ /dev/null
@@ -1,104 +0,0 @@
----
-title: "get_table_rows"
-slug: "rpc-eos-get_table_rows"
-excerpt: "Eos RPC"
-hidden: false
-metadata:
- description: "Eos RPC"
- image: []
- keywords: "eos, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:04 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### Overview
-
-The `get_table_rows` method retrieves rows from a specified table in a given smart contract on the EOS blockchain. This method is essential for developers and users who need to interact with and analyze the data stored in smart contract tables. It provides multiple filtering options, ensuring extensive flexibility in querying specific data.
-{% tabs %}
-{% tab title="TypeScript/JavaScript" %}
-{% code overflow="wrap" lineNumbers="true" %}
-
-```typescript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Eos, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.EOS })
-
-const response = await tatum.rpc.getTableRows({
- code: 'eosio.token',
- table: 'accounts',
- scope: 'eosio',
- limit: 10
-})
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-{% endtab %}
-{% endtabs %}
-
-### Example use cases:
-
-1. **Smart Contract Data Interaction:**
- Developers may find this method critical for interacting with the data within the tables of a smart contract, allowing for effective management and analysis of stored data.
-
-2. **Detailed Data Analysis:**
- Users can employ this method to conduct detailed data analysis, which is pivotal for optimizing data use in smart contracts and enhancing functionalities.
-
-3. **Enhanced Query Flexibility:**
- The diverse filtering options of this method enable the querying of specific data according to user needs, ensuring efficient and effective data retrieval and interaction.
-
-### Request Parameters
-
-The `getTableRows` method requires the following parameters in the request body:
-
-- `code` (string, required): The name of the smart contract that controls the provided table.
-- `table` (string, required): The name of the table to query.
-- `scope` (string, required): The account to which this data belongs.
-- `indexPosition` (string): Position of the index used; accepted parameters are primary, secondary, tertiary, fourth, fifth, sixth, seventh, eighth, ninth, tenth.
-- `keyType` (string): The type of key specified by indexPosition (e.g., uint64_t or name).
-- `encodeType` (string): The encoding type used.
-- `lowerBound` (string): Filters results to return the first element that is not less than the provided value in set.
-- `upperBound` (string): Filters results to return the first element that is greater than the provided value in set.
-- `limit` (integer , default: 10): Limits the number of results returned.
-- `reverse` (boolean, default: false): Reverses the order of returned results.
-- `showPayer` (boolean, default: false): Shows RAM payer.
-
-### Return Object
-
-The `get_table_rows` method typically returns an object containing the requested rows from the specified table associated with the provided smart contract.
-
-### JSON-RPC Request Example
-
-```json
-{
- "code": "eosio.token",
- "table": "accounts",
- "scope": "eosio",
- "limit": 10
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "rows": [
- {"30010000000000000000000000000000011030555d4db7b23b01000000000000000000000000003041000000000000000000000000000000000000000000000000000000000000000000"},
- {"c00e000000000000000000000000000000c0270900000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"},
- {"002400000000000000000000000000000064000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"},
- {"50330000000000000000000000000000004c040000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"}
- ],
- "more": true,
- "next_key": "595056260442244752"
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-push_transaction.md b/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-push_transaction.md
deleted file mode 100644
index 3653ca09..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-push_transaction.md
+++ /dev/null
@@ -1,98 +0,0 @@
----
-title: "push_transaction"
-slug: "rpc-eos-push_transaction"
-excerpt: "Eos RPC"
-hidden: false
-metadata:
- description: "Eos RPC"
- image: []
- keywords: "eos, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:01 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### Overview
-
-The `push_transaction` method is utilized to transmit a transaction to the EOS blockchain. This method takes a transaction in JSON format and endeavors to apply it to the blockchain, facilitating numerous interactions such as transferring tokens and invoking smart contracts.
-{% tabs %}
-{% tab title="TypeScript/JavaScript" %}
-{% code overflow="wrap" lineNumbers="true" %}
-
-```typescript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Eos, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.EOS })
-
-const transaction = {
- signatures: [/* array of signatures */],
- compression: false,
- packedContextFreeData: 'string', // json to hex
- packedTrx: 'string' // Transaction object json to hex
-}
-
-const response = await tatum.rpc.pushTransaction(transaction)
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-{% endtab %}
-{% endtabs %}
-
-### Example use cases:
-
-1. **Transaction Submission:**
- Developers and users might employ the `push_transaction` method to broadcast transactions to the EOS network, allowing for various interactions and operations on the blockchain.
-
-2. **Smart Contract Interaction:**
- Invoking actions on smart contracts deployed on the EOS blockchain is another crucial functionality of this method, granting users the ability to interface with decentralized applications.
-
-3. **Token Transfer:**
- For transferring EOS tokens or other tokens available on the EOS blockchain between accounts, the `push_transaction` method is used.
-
-### Request Parameters
-
-The `pushTransaction` method mandates the following parameters in the request body:
-
-- `signatures` (array of strings, required) - An array of strings representing signatures needed to authorize the transaction.
-- `compression` (boolean, required) - A boolean indicating the status of compression used, typically false.
-- `packedContextFreeData` (string, required) - Represents the JSON converted to hex.
-- `packedTrx` (string, required) - Specifies the transaction object, converted from JSON to hex.
-
-### Return Object
-
-When a transaction is successfully broadcasted, the `push_transaction` method typically returns nothing but a 200 OK status.
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc": "2.0",
- "id": 1,
- "method": "push_transaction",
- "params": {
- "signatures": ["SIG_K1_..."],
- "compression": false,
- "packedContextFreeData": "746573742064617461", // Example hex of JSON data
- "packedTrx": "00e1f5055c95b089c2e0d0e4" // Example hex of JSON transaction object
- }
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "id": 1
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-push_transactions.md b/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-push_transactions.md
deleted file mode 100644
index aea6b994..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-push_transactions.md
+++ /dev/null
@@ -1,107 +0,0 @@
----
-title: "push_transactions"
-slug: "rpc-eos-push_transactions"
-excerpt: "Eos RPC"
-hidden: false
-metadata:
- description: "Eos RPC"
- image: []
- keywords: "eos, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:03 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### Overview
-
-The `push_transactions` method is designed to submit multiple transactions to the EOS blockchain simultaneously. This method expects an array of transactions in JSON format and attempts to apply them to the blockchain, enabling a range of blockchain interactions like transferring tokens, invoking smart contracts, and more.
-
-{% tabs %}
-{% tab title="TypeScript/JavaScript" %}
-{% code overflow="wrap" lineNumbers="true" %}
-
-```typescript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Eos, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.EOS })
-
-const transactions = [{
- expiration: "2023-09-27T10:00:00",
- refBlockNum: 12345,
- refBlockPrefix: 67890,
- maxNetUsageWords: "10",
- maxCpuUsageMs: "10",
- delaySec: 0,
- contextFreeActions: [],
- actions: [],
- transactionExtensions: []
-}]
-
-const response = await tatum.rpc.pushTransaction(transactions)
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-{% endtab %}
-{% endtabs %}
-
-### Example use cases:
-
-1. **Bulk Transaction Submission:**
- Developers and users can use the `push_transactions` method to broadcast multiple transactions to the EOS network in one go, facilitating various blockchain interactions and operations.
-
-2. **Bulk Smart Contract Interaction:**
- This method is vital for invoking actions on multiple smart contracts deployed on the EOS blockchain, allowing users to interact with multiple decentralized applications simultaneously.
-
-3. **Bulk Token Transfer:**
- `push_transactions` is used for transferring EOS tokens or other tokens deployed on the EOS blockchain between multiple accounts in a single request.
-
-### Request Parameters
-
-The `pushTransactions` method requires the following parameters in the request body:
-
-- `transactions` (array of Transaction Objects, required), each containing:
- - `expiration` (string, required): Time that the transaction must be confirmed by.
- - `refBlockNum` (integer, required)
- - `refBlockPrefix` (integer, required): 32-bit portion of block ID.
- - `maxNetUsageWords` (string or integer, required): A whole number.
- - `maxCpuUsageMs` (string or integer, required): A whole number.
- - `delaySec` (integer, required): Number of seconds to delay execution (used for scheduling).
- - `contextFreeActions` (array of objects, required): Actions that are context-free.
- - `actions` (array of objects, required): Actions that are context-dependent.
- - `transactionExtensions` (array of array of integers or strings): Extensions to the transaction.
-
-### Return Object
-
-Upon successful broadcast of transactions, the `push_transactions` method typically does not return any object but acknowledges with a 200 OK status.
-
-### JSON-RPC Request Example
-
-```json
-[
- {
- "expiration": "2023-09-27T10:00:00",
- "ref_block_num": 12345,
- "ref_block_prefix": 67890,
- "max_net_usage_words": "10",
- "max_cpu_usage_ms": "10",
- "delay_sec": 0,
- "context_free_actions": [],
- "actions": [],
- "transaction_extensions": []
- }
-]
-```
-
-### JSON-RPC Response Example
-
-200 OK status implies successful broadcast, and typically no object is returned.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-send_transaction.md b/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-send_transaction.md
deleted file mode 100644
index e5c72a20..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-send_transaction.md
+++ /dev/null
@@ -1,86 +0,0 @@
----
-title: "send_transaction"
-slug: "rpc-eos-send_transaction"
-excerpt: "Eos RPC"
-hidden: false
-metadata:
- description: "Eos RPC"
- image: []
- keywords: "eos, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:39 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### Overview
-
-The `send_transaction` method is designed to submit a transaction to the EOS blockchain. This method expects a transaction in JSON format and will attempt to apply it to the blockchain, enabling various blockchain interactions such as transferring tokens, invoking smart contracts, etc.
-{% tabs %}
-{% tab title="TypeScript/JavaScript" %}
-{% code overflow="wrap" lineNumbers="true" %}
-
-```typescript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Eos, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.EOS })
-
-const response = await tatum.rpc.sendTransaction({
- signatures: [/* array of signatures */],
- compression: false,
- packedContextFreeData: 'string', // json to hex
- packedTrx: 'string' // Transaction object json to hex
-})
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-{% endtab %}
-{% endtabs %}
-
-### Example use cases:
-
-1. **Transaction Submission:**
- Developers and users can utilize the `send_transaction` method to broadcast their transactions to the EOS network, enabling various blockchain interactions and operations.
-
-2. **Smart Contract Interaction:**
- This method is crucial for invoking actions on smart contracts deployed on the EOS blockchain, allowing users to interact with decentralized applications.
-
-3. **Token Transfer:**
- `send_transaction` is used for transferring EOS tokens or other tokens deployed on the EOS blockchain between accounts.
-
-### Request Parameters
-
-The `sendTransaction` method requires the following parameters in the request body:
-
-- `signatures` (array of strings, required): Array of signatures required to authorize the transaction.
-- `compression` (boolean): Compression used, usually false.
-- `packedContextFreeData` (string): JSON converted to hex.
-- `packedTrx` (string): Transaction object converted from JSON to hex.
-
-### Return Object
-
-The `send_transaction` method typically does not return any object but acknowledges with a 200 OK status upon a successful transaction broadcast.
-
-### JSON-RPC Request Example
-
-```json
-{
- "signatures": ["SIG_K1_..."],
- "compression": false,
- "packed_context_free_data": "0x...",
- "packed_trx": "0x..."
-}
-```
-
-### JSON-RPC Response Example
-
-200 OK status implies successful broadcast, and typically no object is returned.
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-trace-api-get_block.md b/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-trace-api-get_block.md
deleted file mode 100644
index f336488c..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-eos/rpc-eos-trace-api-get_block.md
+++ /dev/null
@@ -1,126 +0,0 @@
----
-title: "trace-api-get_block"
-slug: "rpc-eos-trace-api-get_block"
-excerpt: "Eos RPC"
-hidden: false
-metadata:
- description: "Eos RPC"
- image: []
- keywords: "eos, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:04 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-{% hint style="warning" %}
-Please note that you are able to get data only from block number 260742168 and newer.
-{% endhint %}
-
-### How to use it
-
-{% tabs %}
-{% tab title="TypeScript/JavaScript" %}
-{% code overflow="wrap" lineNumbers="true" %}
-
-```typescript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Eos, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.EOS })
-
-const block = await tatum.rpc.traceApiGetBlock({ blockNum: '260742168' })
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-{% endtab %}
-{% endtabs %}
-
-{% hint style="info" %}
-This method is available only on the full archive node.
-{% endhint %}
-
-### Overview
-
-The `get_block` method of the Trace API retrieves detailed information concerning a specific block in the blockchain, returning a JSON object that conforms to the BlockTraceV1 schema. This method is crucial for applications and services requiring access to block and transaction details such as the list of transactions, actions within those transactions, the producer of the block, and more.
-
-### Example use cases:
-
-1. **Block Verification:**
- Developers or validators might use the `get_block` method to fetch specific block details for the purpose of verifying block information. It allows the comparison of block data retrieved from different nodes to ensure data consistency and integrity across the network.
-
-2. **Transaction Confirmation:**
- Users and services might utilize the `get_block` method to confirm transaction inclusion within a block. By examining the transactions field of the returned block object, users can ascertain whether a specific transaction has been included and, consequently, confirm its successful execution.
-
-3. **Data Analysis and Chain Exploration:**
- Researchers and analysts can employ the `get_block` method to retrieve detailed block data for analytical purposes, exploring block and transaction patterns, studying network activity, and gaining insights into blockchain operations and behavior.
-
-### Request Parameters
-
-The `getBlock` method accepts the following parameters:
-
-- `blockNum` (integer, required): The height of this block in the chain.
-
-### Return Object
-
-The return object provides detailed information about the requested block and contains the following fields:
-
-- `id` (string): A unique identifier for the block.
-- `number` (integer): The height of this block in the chain.
-- `previous_id` (string): The unique identifier of the previous block in the chain.
-- `status` (string): String indicating whether the block is "pending" or "irreversible".
-- `timestamp` (string): The timestamp when the block was produced.
-- `producer` (string): Information about who produced the block.
-- `transaction_mroot` (string): The Merkle root of all transactions in the block.
-- `action_mroot` (string): The Merkle root of all actions in the block.
-- `schedule_version` (integer): Indicates the number of times the producer schedule has changed since genesis.
-- `transactions` (array): An array containing TransactionTraceV1 objects representing each transaction included in the block.
-
-### JSON-RPC Request Example
-
-```json
-{
- "block_num": "260742168"
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "id": "string",
- "number": 0,
- "previous_id": "string",
- "status": "string",
- "timestamp": "string",
- "producer": "string",
- "transactions": [
- {
- "id": "string",
- "actions": [
- {
- "global_sequence": 0,
- "receiver": "string",
- "account": "string",
- "action": "string",
- "authorization": [
- {
- "account": "string",
- "permission": "string"
- }
- ],
- "data": {}
- }
- ]
- }
- ]
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana.md b/v1.0/RPC Nodes/rpc-others/rpc-solana.md
deleted file mode 100644
index 5547c56d..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Solana"
-slug: "rpc-solana"
-excerpt: ""
-hidden: false
-createdAt: "Wed Mar 06 2024 10:35:18 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Wed Mar 06 2024 13:09:53 GMT+0000 (Coordinated Universal Time)"
----
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getaccountinfo.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getaccountinfo.md
deleted file mode 100644
index a25465b9..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getaccountinfo.md
+++ /dev/null
@@ -1,110 +0,0 @@
----
-title: "getaccountinfo"
-slug: "rpc-solana-getaccountinfo"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:03 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const res = await tatum.rpc.getAccountInfo('ChkH4bTk7c5NSGbxvXx89yY2oU7rFJsr3Cq1gPNCCPVe')
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getAccountInfo` RPC method is used to fetch and retrieve specific and detailed information about a particular account on the Solana blockchain. This information includes the current state of the account, its associated data, and the account's current balance.
-
-This method could be used in scenarios where detailed account data is required, for example, to verify transactions, check account balances, or to review the account's history.
-
-{% embed url=" %}
-
-### Parameters
-
-The `getAccountInfo` method accepts two parameters:
-
-- `accountPubkey`(string, required): The public key of the account for which information is to be fetched.
- - Example: `"ChkH4bTk7c5NSGbxvXx89yY2oU7rFJsr3Cq1gPNCCPVe"`
-- `options` (object, optional): Configuration object containing the following fields:
- - `commitment` (string, optional): Specifies the confirmation level of data to be fetched.
- - Values: `finalized` `confirmed` `processed`
- - `encoding` (string, optional): Encoding format for Account data
- - Values: `base58` `base64` `base64+zstd` `jsonParsed`
-
-### Return object
-
-The `getAccountInfo` method returns an object containing the following fields:
-
-- `context`: An object containing details about the context in which the account information was fetched.
- - `slot`: The slot at which the data was fetched.
-- `value`: An object containing the account's information.
- - `owner`: The public key of the account's owner.
- - `lamports`: The account's current balance.
- - `data`: data associated with the account, either as encoded binary data or JSON format `{: }` - depending on encoding parameter
- - `executable`: Whether the account is marked as executable.
- - `rentEpoch`: The rent epoch value of the account.
- - `size`: The data size of the account
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc": "2.0",
- "id": 1,
- "method": "getAccountInfo",
- "params": [
- "ChkH4bTk7c5NSGbxvXx89yY2oU7rFJsr3Cq1gPNCCPVe",
- {
- "commitment": "finalized",
- "encoding": "base64"
- }
- ]
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "id": 1,
- "result": {
- "context": {
- "slot": 123456
- },
- "value": {
- "owner": "Base58('11111111111111111111111111111111')",
- "lamports": 1000000,
- "data": "Base64('...')",
- "executable": false,
- "rentEpoch": 20,
- "size": 120
- }
- }
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getbalance.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getbalance.md
deleted file mode 100644
index be0b9e3d..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getbalance.md
+++ /dev/null
@@ -1,86 +0,0 @@
----
-title: "getbalance"
-slug: "rpc-solana-getbalance"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:02 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const res = await tatum.rpc.getBalance('8Ew6iQXcTRHAUNNu3X9VBn1g1bJkXEZJ9gFD2AGKtdPB')
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getBalance` RPC method is used to retrieve the current balance of a specified account on the Solana blockchain. It's a straightforward and efficient way to monitor and keep track of account balances.
-
-This method is typically used in scenarios where you need to check the available balance before initiating a transaction or for accounting purposes in a wallet application.
-
-### Parameters
-
-The `getBalance` method requires one parameter:
-
-- (string, required) Pubkey of account to query, as base-58 encoded string
- - Example: `"8Ew6iQXcTRHAUNNu3X9VBn1g1bJkXEZJ9gFD2AGKtdPB"`
-
-### Return object
-
-The `getBalance` method returns an object containing the following fields:
-
-- `context`: An object containing details about the context in which the balance was fetched.
- - `slot`: The slot at which the data was fetched.
-- `value`: The current balance of the account, in lamports.
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc": "2.0",
- "id": 1,
- "method": "getBalance",
- "params": [
- "8Ew6iQXcTRHAUNNu3X9VBn1g1bJkXEZJ9gFD2AGKtdPB",
- ]
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "id": 1,
- "result": {
- "context": {
- "slot": 194573649
- },
- "value": 2484257209
- }
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getblock.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getblock.md
deleted file mode 100644
index d7e7765e..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getblock.md
+++ /dev/null
@@ -1,187 +0,0 @@
----
-title: "getblock"
-slug: "rpc-solana-getblock"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:06 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const slotNumber = 430
-
-const config = {
- encoding: "jsonParsed",
- transactionDetails: "full",
- rewards: false,
- maxSupportedTransactionVersion: 0,
-}
-
-const res = await tatum.rpc.getBlock(slotNumber, config)
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getBlock` method returns identity and transaction information about a confirmed block in the ledger. It provides detailed data about each transaction within the block, including pre and post transaction balances, transaction status, fees charged, and more.
-
-This method is essential for blockchain explorers or any application that needs to track and represent blockchain transaction data. For instance, it could be used by a wallet application to show transaction details or by a network analytics tool for data gathering and analysis.
-
-{% embed url=" %}
-
-### Parameters
-
-This method takes the following parameters:
-
-- `slot` (number, required): Slot number
-- `options` (object, optional): This object can contain the following fields:
- - `commitment`(string, optional): Specifies the level of commitment to apply when fetching data.
- - Values: `finalized` `confirmed` `processed`
- - `encoding` (string, optional): Encoding format for each returned transaction. The default is `json`. Other possible values include: `jsonParsed`, `base58`, `base64`.
- - `transactionDetails` (string, optional): Level of transaction detail to return. The default is `full`. Other possible values include: `accounts`, `signatures`, `none`.
- - `maxSupportedTransactionVersion` (number, optional): The max transaction version to return in responses.
- - `rewards` (bool, optional): Whether to populate the `rewards` array. The default includes rewards.
-
-### Return Object
-
-The method returns a JSON object that includes detailed information about the block and the transactions it contains. If the specified block is not confirmed, the result will be `null`.
-
-The returned JSON object includes the following fields:
-
-- `blockhash`: The blockhash of this block, as base-58 encoded string.
-- `previousBlockhash`: The blockhash of this block's parent, as base-58 encoded string. If the parent block is not available due to ledger cleanup, this field will return "11111111111111111111111111111111".
-- `parentSlot`: The slot index of this block's parent.
-- `transactions`: An array of JSON objects containing detailed transaction information. This field is present if "full" transaction details are requested.
- - `transaction:` Transaction object, either in JSON format or encoded binary data, depending on encoding parameter
- - `meta:` Transaction status metadata object, containing `null` or:
- - `err:` Error if transaction failed, null if transaction succeeded. TransactionError definitions
- - `fee:` Fee this transaction was charged, as u64 integer
- - `preBalances:` Array of numbers representing account balances from before the transaction was processed
- - `postBalances:` Array of numbers representing account balances after the transaction was processed
- - `innerInstructions:` List of inner instructions or `null` if inner instruction recording was not enabled during this transaction
- - `preTokenBalances:` List of token balances from before the transaction was processed or omitted if token balance recording was not yet enabled during this transaction
- - `postTokenBalances:` List of token balances from after the transaction was processed or omitted if token balance recording was not yet enabled during this transaction
- - `logMessages:` Array of string log messages or `null` if log message recording was not enabled during this transaction
- - `rewards:` Transaction-level rewards, populated if rewards are requested; an array of JSON objects containing:
- - `pubkey:` The public key, as base-58 encoded string, of the account that received the reward
- - `lamports:` Number of reward lamports credited or debited by the account
- - `postBalance:` Account balance in lamports after the reward was applied
- - `rewardType:` Type of reward: "fee", "rent", "voting", "staking"
- - `commission:` Vote account commission when the reward was credited, only present for voting and staking rewards
- - DEPRECATED: `status:` Transaction status
- - `"Ok":` Transaction was successful
- - `"Err":` Transaction failed with TransactionError
- - `loadedAddresses:` Transaction addresses loaded from address lookup tables. Undefined if `maxSupportedTransactionVersion` is not set in request params.
- - `writable:` Ordered list of base-58 encoded addresses for writable loaded accounts
- - `readonly:`Ordered list of base-58 encoded addresses for readonly loaded accounts
- - `returnData:` The most-recent return data generated by an instruction in the transaction, with the following fields:
- - `programId:` The program that generated the return data, as base-58 encoded Pubkey
- - `data:` The return data itself, as base-64 encoded binary data
- - `computeUnitsConsumed:` Number of compute units consumed by the transaction
- - `version:` Transaction version. Undefined if `maxSupportedTransactionVersion` is not set in request params.
-- `signatures`: An array of signatures strings, corresponding to the transaction order in the block. This field is present if "signatures" are requested for transaction details.
-- `rewards`: Block-level rewards, present if rewards are requested.
-- `blockTime`: Estimated production time, as Unix timestamp (seconds since the Unix epoch).
-- `blockHeight`: The number of blocks beneath this block.
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc": "2.0",
- "id": 1,
- "method": "getBlock",
- "params": [
- 430,
- {
- "encoding": "json",
- "maxSupportedTransactionVersion": 0,
- "transactionDetails": "full",
- "rewards": false
- }
- ]
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "result": {
- "blockHeight": 428,
- "blockTime": null,
- "blockhash": "3Eq21vXNB5s86c62bVuUfTeaMif1N2kUqRPBmGRJhyTA",
- "parentSlot": 429,
- "previousBlockhash": "mfcyqEXB3DnHXki6KjjmZck6YjmZLvpAByy2fj4nh6B",
- "transactions": [
- {
- "meta": {
- "err": null,
- "fee": 5000,
- "innerInstructions": [],
- "logMessages": [],
- "postBalances": [499998932500, 26858640, 1, 1, 1],
- "postTokenBalances": [],
- "preBalances": [499998937500, 26858640, 1, 1, 1],
- "preTokenBalances": [],
- "rewards": null,
- "status": {
- "Ok": null
- }
- },
- "transaction": {
- "message": {
- "accountKeys": [
- "3UVYmECPPMZSCqWKfENfuoTv51fTDTWicX9xmBD2euKe",
- "AjozzgE83A3x1sHNUR64hfH7zaEBWeMaFuAN9kQgujrc",
- "SysvarS1otHashes111111111111111111111111111",
- "SysvarC1ock11111111111111111111111111111111",
- "Vote111111111111111111111111111111111111111"
- ],
- "header": {
- "numReadonlySignedAccounts": 0,
- "numReadonlyUnsignedAccounts": 3,
- "numRequiredSignatures": 1
- },
- "instructions": [
- {
- "accounts": [1, 2, 3, 0],
- "data": "37u9WtQpcm6ULa3WRQHmj49EPs4if7o9f1jSRVZpm2dvihR9C8jY4NqEwXUbLwx15HBSNcP1",
- "programIdIndex": 4
- }
- ],
- "recentBlockhash": "mfcyqEXB3DnHXki6KjjmZck6YjmZLvpAByy2fj4nh6B"
- },
- "signatures": [
- "2nBhEBYYvfaAe16UMNqRHre4YNSskvuYgx3M6E4JP1oDYvZEJHvoPzyUidNgNX5r9sTyN1J9UxtbCXy2rqYcuyuv"
- ]
- }
- }
- ]
- },
- "id": 1
-}js
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getblockcommitment.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getblockcommitment.md
deleted file mode 100644
index 8ebb4d1b..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getblockcommitment.md
+++ /dev/null
@@ -1,89 +0,0 @@
----
-title: "getblockcommitment"
-slug: "rpc-solana-getblockcommitment"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:02 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const res = await tatum.rpc.getBlockCommitment(5)
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getBlockCommitment` method returns the commitment for a particular block. Commitment in Solana refers to the amount of cluster stake in lamports that has voted on the block at each depth from 0 to `MAX_LOCKOUT_HISTORY` + 1.
-
-This method is crucial for understanding the level of consensus or agreement about a block in the network, as it indicates how much of the network's total stake has confirmed the block. It can be used by blockchain explorers to show the confirmation status of transactions and by network monitors to track the progress of the blockchain.
-
-{% embed url=" %}
-
-### Parameters
-
-This method takes the following parameter:
-
-- `number` (required): The block number, identified by Slot.
-
-### Return Object
-
-The method returns a JSON object that includes detailed information about the block's commitment and the total active stake in the current epoch. If the specified block is not known, the `commitment` field will be `null`.
-
-The returned JSON object includes the following fields:
-
-- `commitment`: Commitment, comprising either:
- - `` - Unknown block.
- - `` - Commitment, an array of integers logging the amount of cluster stake in lamports that has voted on the block at each depth from 0 to `MAX_LOCKOUT_HISTORY` + 1.
-- `totalStake`: The total active stake, in lamports, of the current epoch.
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc": "2.0",
- "id": 1,
- "method": "getBlockCommitment",
- "params": [5]
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "result": {
- "commitment": [
- 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
- 0, 0, 0, 0, 0, 10, 32
- ],
- "totalStake": 42
- },
- "id": 1
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getblockheight.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getblockheight.md
deleted file mode 100644
index a67fce94..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getblockheight.md
+++ /dev/null
@@ -1,77 +0,0 @@
----
-title: "getblockheight"
-slug: "rpc-solana-getblockheight"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:04 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const res = await tatum.rpc.getBlockHeight()
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getBlockHeight` method returns the current block height of the node. Block height refers to the number of blocks preceding the current one in the blockchain.
-
-This method is beneficial for understanding the current status of the blockchain, as it provides the most recent block number processed by the node. It can be used for monitoring the progress of the blockchain, troubleshooting node synchronisation issues, and determining the confirmation status of a transaction by comparing its block number with the current block height.
-
-{% embed url=" %}
-
-### Parameters
-
-`options` (object, optional): This object can contain the following fields:
-
-- `commitment`(string, optional): Specifies the level of commitment to apply when fetching data.
- - Values: `finalized` `confirmed` `processed`
-- `minContextSlot` (number, optional): This field can be used to specify the minimum slot that the request can be evaluated at.
-
-### Return Object
-
-The method returns a single number, representing the current block height.
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc":"2.0",
- "id":1,
- "method":"getBlockHeight"
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "result": 1233,
- "id": 1
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getblockproduction.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getblockproduction.md
deleted file mode 100644
index eda74b35..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getblockproduction.md
+++ /dev/null
@@ -1,93 +0,0 @@
----
-title: "getblockproduction"
-slug: "rpc-solana-getblockproduction"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:03 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const res = await tatum.rpc.getBlockProduction()
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getBlockProduction` method provides information about the recent block production from the current or previous epoch. This can be used to monitor the performance and activity of validators on the Solana network.
-
-{% embed url=" %}
-
-### Parameters
-
-- `options` (object, optional): This object can contain the following fields:
- - `commitment`(string, optional): Specifies the level of commitment to apply when fetching data.
- - Values: `finalized` `confirmed` `processed`
- - `identity` (string, optional): Only return results for this validator identity (base-58 encoded).
- - `range` (object, optional): Slot range to return block production for.
- - `firstSlot` (number): First slot to return block production information for (inclusive).
- - `lastSlot` (number, optional): Last slot to return block production information for (inclusive).
-
-### Return Object
-
-The result will be a JSON object with value equal to object with the following fields:
-
-- `byIdentity` (object): A dictionary of validator identities, as base-58 encoded strings. The value is a two-element array containing the number of leader slots and the number of blocks produced.
-- `range` (object): Block production slot range with fields `firstSlot` and `lastSlot` indicating the first and last slot of block production information respectively.
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc": "2.0",
- "id": 1,
- "method": "getBlockProduction"
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "result": {
- "context": {
- "slot": 9887
- },
- "value": {
- "byIdentity": {
- "85iYT5RuzRTDgjyRa3cP8SYhM2j21fj7NhfJ3peu1DPr": [9888, 9886]
- },
- "range": {
- "firstSlot": 0,
- "lastSlot": 9887
- }
- }
- },
- "id": 1
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getblocks.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getblocks.md
deleted file mode 100644
index 83aadb66..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getblocks.md
+++ /dev/null
@@ -1,74 +0,0 @@
----
-title: "getblocks"
-slug: "rpc-solana-getblocks"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:43 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const res = await tatum.rpc.getBlocks(5,10)
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getBlocks` method returns a list of confirmed blocks between two specified slots. This can be useful when needing to examine a specific range of blocks for transaction analysis, data verification, or other blockchain analysis tasks.
-
-### Parameters
-
-- `endSlot` (number, required): This is the upper limit of the slot range from which blocks are to be returned.
-- `startSlot` (number, optional): This is the lower limit of the slot range. If not provided, the method will return blocks from the start of the blockchain to the `endSlot`. Note that `startSlot` must be no more than 500,000 blocks lower than the `end_slot`.
-- `options` (object, optional): This object can contain the following fields:
- - `commitment`(string, optional): Specifies the level of commitment to apply when fetching data.
- - Values: `finalized` `confirmed` Note that `processed` is not supported.
-
-### Return Object
-
-The method returns an array of integers, each representing a confirmed block between `startSlot` and either `endSlot` (if provided) or the latest confirmed block, inclusive. The maximum range allowed is 500,000 slots.
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc": "2.0",
- "id": 1,
- "method": "getBlocks",
- "params": [5, 10]
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "result": [5, 6, 7, 8, 9, 10],
- "id": 1
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getblockswithlimit.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getblockswithlimit.md
deleted file mode 100644
index eb65643f..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getblockswithlimit.md
+++ /dev/null
@@ -1,76 +0,0 @@
----
-title: "getblockswithlimit"
-slug: "rpc-solana-getblockswithlimit"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:02 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const res = await tatum.rpc.getBlocksWithLimit(5, 3)
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getBlocksWithLimit` method returns a list of confirmed blocks starting at a given slot and up to a specified limit. This can be helpful when you need to retrieve a specific number of recent blocks for transaction analysis or blockchain data verification purposes.
-
-### Parameters
-
-This method requires and optionally accepts the following parameters:
-
-- `startSlot` (number, required): This is the slot from which the method will start returning blocks.
-- `limit` (number, optional): This is the number of blocks to be returned starting from the `startSlot`. If not provided, the method will return all blocks from the `startSlot` to the end of the blockchain. Note that `limit` must be no more than 500,000 blocks higher than the `startSlot`.
-- `options` (object, optional): This object can contain the following fields:
- - `commitment`(string, optional): Specifies the level of commitment to apply when fetching data.
- - Values: `finalized` `confirmed` Note that `processed` is not supported.
-
-### Return Object
-
-The method returns an array of integers, each representing a confirmed block starting from the `startSlot` and up to the `limit` blocks, inclusive.
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc": "2.0",
- "id":1,
- "method":"getBlocksWithLimit",
- "params":[5, 3]
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "result": [5, 6, 7],
- "id": 1
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getblocktime.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getblocktime.md
deleted file mode 100644
index 271f1a6c..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getblocktime.md
+++ /dev/null
@@ -1,76 +0,0 @@
----
-title: "getblocktime"
-slug: "rpc-solana-getblocktime"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:04 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const res = await tatum.rpc.getBlockTime(5)
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getBlockTime` method returns the estimated production time of a block. Each validator in the Solana network reports their UTC time to the ledger at regular intervals by intermittently adding a timestamp to a vote for a specific block. A requested block's time is then calculated from the stake-weighted mean of these vote timestamps recorded on the ledger in a set of recent blocks.
-
-This method is useful in understanding when a particular block was produced, which is essential for various analysis and audit purposes.
-
-{% embed url=" %}
-
-### Parameters
-
-- `blockNumber` (number, required): This is the number of the block for which you want to retrieve the production time. The block number is identified by its slot.
-
-### Return Object
-
-The method returns an integer or null:
-
-- If the production time of the block is available, the method returns the estimated production time as a Unix timestamp (seconds since the Unix epoch).
-- If the production time of the block is not available, the method returns null.
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc":"2.0", "id":1,
- "method": "getBlockTime",
- "params":[5]
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "result": 1574721591,
- "id": 1
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getclusternodes.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getclusternodes.md
deleted file mode 100644
index 3dbfcd0f..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getclusternodes.md
+++ /dev/null
@@ -1,87 +0,0 @@
----
-title: "getclusternodes"
-slug: "rpc-solana-getclusternodes"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:01 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const res = await tatum.rpc.getClusterNodes()
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getClusterNodes` method returns information about all the nodes participating in the cluster. This method can be used for network analysis, monitoring, and audit purposes. For example, you can use it to track the versions of software running on various nodes, identify the public keys of nodes, or determine the network addresses for various services.
-
-{% embed url=" %}
-
-### Parameters
-
-This method does not require any parameters.
-
-### Return Object
-
-The method returns an array of JSON objects, each containing the following fields:
-
-- `pubkey`: Node's public key, as base-58 encoded string.
-- `gossip`: Gossip network address for the node.
-- `tpu`: TPU network address for the node.
-- `rpc`: JSON RPC network address for the node, or `null` if the JSON RPC service is not enabled.
-- `version`: The software version of the node, or `null` if the version information is not available.
-- `featureSet`: The unique identifier of the node's feature set.
-- `shredVersion`: The shred version the node has been configured to use.
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc": "2.0",
- "id": 1,
- "method": "getClusterNodes"
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "result": [
- {
- "gossip": "10.239.6.48:8001",
- "pubkey": "9QzsJf7LPLj8GkXbYT3LFDKqsj2hHG7TA3xinJHu8epQ",
- "rpc": "10.239.6.48:8899",
- "tpu": "10.239.6.48:8856",
- "version": "1.0.0 c375ce1f"
- }
- ],
- "id": 1
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getepochinfo.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getepochinfo.md
deleted file mode 100644
index 91af7f5e..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getepochinfo.md
+++ /dev/null
@@ -1,87 +0,0 @@
----
-title: "getepochinfo"
-slug: "rpc-solana-getepochinfo"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:44 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const res = await tatum.rpc.getEpochInfo()
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getEpochInfo` method returns information about the current epoch on the Solana network. This includes the current slot, block height, epoch number, slot index, the number of slots in this epoch, and the total number of transactions processed without error since genesis. This data can be essential for developers and operators of Solana nodes to understand the current state of the network and to track its progress over time.
-
-{% embed url=" %}
-
-### Parameters
-
-- `options` (object, optional): A configuration object containing:
- - `commitment`(string, optional): Specifies the level of commitment to apply when fetching data.
- - `minContextSlot` (number, optional): The minimum slot that the request can be evaluated at.
-
-### Return Object
-
-The result field will be an object with the following fields:
-
-- `absoluteSlot`: The current slot.
-- `blockHeight`: The current block height.
-- `epoch`: The current epoch.
-- `slotIndex`: The current slot relative to the start of the current epoch.
-- `slotsInEpoch`: The number of slots in this epoch.
-- `transactionCount`: Total number of transactions processed without error since genesis.
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc":"2.0",
- "id":1,
- "method":"getEpochInfo"
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "result": {
- "absoluteSlot": 166598,
- "blockHeight": 166500,
- "epoch": 27,
- "slotIndex": 2790,
- "slotsInEpoch": 8192,
- "transactionCount": 22661093
- },
- "id": 1
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getepochschedule.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getepochschedule.md
deleted file mode 100644
index 2cb7d28e..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getepochschedule.md
+++ /dev/null
@@ -1,85 +0,0 @@
----
-title: "getepochschedule"
-slug: "rpc-solana-getepochschedule"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:02 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const res = await tatum.rpc.getEpochSchedule()
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getEpochSchedule` method returns the epoch schedule information from this cluster's genesis config. This includes the maximum number of slots in each epoch, the number of slots before the beginning of an epoch to calculate a leader schedule for that epoch, whether epochs start short and grow, the first normal-length epoch, and the first normal slot. This data can be useful for planning and understanding the progression of epochs in the Solana network.
-
-{% embed url=" %}
-Try this Feature
-{% endembed %}
-
-### Parameters
-
-None
-
-### Return Object
-
-The result field will be an object with the following fields:
-
-- `slotsPerEpoch`: The maximum number of slots in each epoch.
-- `leaderScheduleSlotOffset`: The number of slots before beginning of an epoch to calculate a leader schedule for that epoch.
-- `warmup`: Whether epochs start short and grow.
-- `firstNormalEpoch`: The first normal-length epoch, log2(slotsPerEpoch) - log2(MINIMUM\_SLOTS\_PER\_EPOCH).
-- `firstNormalSlot`: MINIMUM\_SLOTS\_PER\_EPOCH \* (2.pow(firstNormalEpoch) - 1).
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc":"2.0",
- "id":1,
- "method":"getEpochSchedule"
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "result": {
- "firstNormalEpoch": 8,
- "firstNormalSlot": 8160,
- "leaderScheduleSlotOffset": 8192,
- "slotsPerEpoch": 8192,
- "warmup": true
- },
- "id": 1
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getfeeformessage.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getfeeformessage.md
deleted file mode 100644
index e2a4c07e..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getfeeformessage.md
+++ /dev/null
@@ -1,84 +0,0 @@
----
-title: "getfeeformessage"
-slug: "rpc-solana-getfeeformessage"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:42 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const message = {
- // Message content goes here...
-}
-const res = await tatum.rpc.getFeeForMessage(message)
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getFeeForMessage` method is used to estimate the transaction fee for a given message. This is very useful when you are preparing to send a transaction and you want to estimate the transaction cost. This can be used in situations where you need to validate whether a user has enough funds to cover the transaction fee or to provide an estimate of the cost to the user.
-
-### Parameters
-
-- `message`(string, required): Base-64 encoded Message for which the fee should be estimated.
- - Example: "`AQABAgIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEBAQAA`"
-- `options` (object, optional): Configuration object containing the following fields:
- - `commitment` (string, optional): Specifies the confirmation level of data to be fetched.
- - Values: `finalized` `confirmed` `processed`
- - `minContextSlot` (number, optional): The minimum slot that the request can be evaluated at
- - Example: `1000`
-
-### Return Object
-
-The result will be a JSON object with `value` equal to Fee corresponding to the message at the specified blockhash
-
-### JSON-RPC Request Example
-
-```json
-{
- "id":1,
- "jsonrpc":"2.0",
- "method":"getFeeForMessage",
- "params":[
- "AQABAgIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEBAQAA",
- {
- "commitment":"processed"
- }
- ]
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "result": { "context": { "slot": 5068 }, "value": 5000 },
- "id": 1
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getfirstavailableblock.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getfirstavailableblock.md
deleted file mode 100644
index 6240652f..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getfirstavailableblock.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: "getfirstavailableblock"
-slug: "rpc-solana-getfirstavailableblock"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:05 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const res = await tatum.rpc.getFirstAvailableBlock()
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getFirstAvailableBlock` method returns the slot of the lowest confirmed block that has not been purged from the ledger. This method is useful when you want to start parsing the ledger from the oldest available data, or when you want to check how far back the data in your node goes. This can be critical in scenarios where historical block data is required for backtracking transactions or auditing purposes.
-
-{% embed url=" %}
-
-### Parameters
-
-This method does not require any parameters.
-
-### Return Object
-
-The method returns an integer representing the slot of the oldest confirmed block that has not been purged from the ledger.
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc":"2.0",
- "id":1,
- "method":"getFirstAvailableBlock"
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "result": 250000,
- "id": 1
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getgenesishash.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getgenesishash.md
deleted file mode 100644
index fe12d42e..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getgenesishash.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: "getgenesishash"
-slug: "rpc-solana-getgenesishash"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:01 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const res = await tatum.rpc.getGenesisHash()
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getGenesisHash` method returns the genesis hash of the Solana network. The genesis hash is an important piece of information in the blockchain world. It is the initial block or the very first block in a blockchain. The genesis hash can be used for various use cases such as to verify the integrity of data, as a reference point in the blockchain, and for debugging purposes.
-
-{% embed url=" %}
-
-### Parameters
-
-None
-
-### Return Object
-
-- Returns a string, which is a Hash as base-58 encoded string.
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc":"2.0",
- "id":1,
- "method":"getGenesisHash"
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "result": "GH7ome3EiwEr7tu9JuTh2dpYWBJK3z69Xm1ZE3MEE6JC",
- "id": 1
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-gethealth.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-gethealth.md
deleted file mode 100644
index 39b7a387..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-gethealth.md
+++ /dev/null
@@ -1,99 +0,0 @@
----
-title: "gethealth"
-slug: "rpc-solana-gethealth"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:04 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const res = await tatum.rpc.getHealth()
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getHealth` method is used to monitor the current health of the node. This method can be beneficial for maintenance and troubleshooting purposes. For instance, you may use this method to check the health status of your node periodically or to validate if a newly set up node is functioning correctly.
-
-Please note that if one or more `--known-validator` arguments are provided to `solana-validator`, "ok" is returned when the node is within `HEALTH_CHECK_SLOT_DISTANCE` slots of the highest known validator; otherwise, an error is returned. If no known validators are provided, "ok" is always returned.
-
-{% embed url=" %}
-
-### Parameters
-
-This method does not require any parameters.
-
-### Return Object
-
-If the node is healthy, it returns "ok". If the node is unhealthy, a JSON RPC error response is returned. The specifics of the error response are unstable and may change in the future.
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc": "2.0",
- "id": 1,
- "method": "getHealth"
-}
-```
-
-### JSON-RPC Response Examples
-
-- Healthy node response:
-
- ```json
- { "jsonrpc": "2.0", "result": "ok", "id": 1 }
- ```
-- Unhealthy node response (generic):
-
- ```json
- {
- "jsonrpc": "2.0",
- "error": {
- "code": -32005,
- "message": "Node is unhealthy",
- "data": {}
- },
- "id": 1
- }
- ```
-- Unhealthy node response (if additional information is available):
-
- ```json
- {
- "jsonrpc": "2.0",
- "error": {
- "code": -32005,
- "message": "Node is behind by 42 slots",
- "data": {
- "numSlotsBehind": 42
- }
- },
- "id": 1
- }
- ```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-gethighestsnapshotslot.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-gethighestsnapshotslot.md
deleted file mode 100644
index 0fed7b59..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-gethighestsnapshotslot.md
+++ /dev/null
@@ -1,91 +0,0 @@
----
-title: "gethighestsnapshotslot"
-slug: "rpc-solana-gethighestsnapshotslot"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:05 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const res = await tatum.rpc.getHighestSnapshotSlot()
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getHighestSnapshotSlot` method provides the highest slot information for which the node has snapshots. It determines the highest full snapshot slot and, if available, the highest incremental snapshot slot based on the full snapshot slot.
-
-This method can be used in a variety of scenarios, including managing data storage and synchronisation of blockchain data. By knowing the highest snapshot slot, developers can estimate the amount of data that needs to be downloaded to sync a new node, or to ensure the node is up to date with the current state of the blockchain.
-
-{% embed url=" %}
-
-### Parameters
-
-None
-
-### Return Object
-
-When the node has a snapshot, this method returns a JSON object with the following fields:
-
-- `full`: The highest full snapshot slot.
-- `incremental`: The highest incremental snapshot slot based on the full snapshot slot, if available.
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc":"2.0",
- "id":1,
- "method":"getHighestSnapshotSlot"
-}
-```
-
-### JSON-RPC Response Example
-
-Here is an example response when the node has a snapshot:
-
-```json
-{
- "jsonrpc": "2.0",
- "result": {
- "full": 100,
- "incremental": 110
- },
- "id": 1
-}
-```
-
-In case the node does not have a snapshot, the response would be:
-
-```json
-{
- "jsonrpc": "2.0",
- "error": { "code": -32008, "message": "No snapshot" },
- "id": 1
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getidentity.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getidentity.md
deleted file mode 100644
index 63375f37..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getidentity.md
+++ /dev/null
@@ -1,77 +0,0 @@
----
-title: "getidentity"
-slug: "rpc-solana-getidentity"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:40 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const res = await tatum.rpc.getIdentity()
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getIdentity` method is used to retrieve the identity pubkey for the current node. This pubkey represents a unique identifier for the node in the Solana network.
-
-Use cases for this method might include retrieving the identity of a node for tracking or monitoring purposes, or validating the identity of a node in scenarios where only certain nodes are trusted for certain operations.
-
-{% embed url=" %}
-
-### Parameters
-
-This method does not require any parameters.
-
-### Return Object
-
-The result field will be a JSON object with the following fields:
-
-- `identity`: The identity pubkey of the current node as a base-58 encoded string.
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc": "2.0",
- "id": 1,
- "method": "getIdentity"
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "result": {
- "identity": "2r1F4iWqVcb8M1DbAjQuFpebkQHY9hcVU4WuW2DJBppN"
- },
- "id": 1
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getinflationgovernor.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getinflationgovernor.md
deleted file mode 100644
index 6557473e..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getinflationgovernor.md
+++ /dev/null
@@ -1,85 +0,0 @@
----
-title: "getinflationgovernor"
-slug: "rpc-solana-getinflationgovernor"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:42 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const res = await tatum.rpc.getInflationGovernor()
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getInflationGovernor` method is used to retrieve the current inflation governor in the Solana blockchain.
-
-{% embed url=" %}
-
-### Parameters
-
-- `options` (object, optional): Configuration object containing the following fields:
- - `commitment`(string, optional): Specifies the level of commitment to apply when fetching data.
- - Values: `finalized` `confirmed` `processed`
-
-### Return Object
-
-The method returns a JSON object with the following fields:
-
-- `initial`: The initial inflation percentage from time 0.
-- `terminal`: Terminal inflation percentage.
-- `taper`: Rate per year at which inflation is lowered. The rate reduction is derived using the target slot time in the genesis config.
-- `foundation`: Percentage of total inflation allocated to the foundation.
-- `foundationTerm`: Duration of foundation pool inflation in years.
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc": "2.0",
- "id": 1,
- "method": "getInflationGovernor"
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "result": {
- "foundation": 0.05,
- "foundationTerm": 7,
- "initial": 0.15,
- "taper": 0.15,
- "terminal": 0.015
- },
- "id": 1
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getinflationrate.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getinflationrate.md
deleted file mode 100644
index da1b6176..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getinflationrate.md
+++ /dev/null
@@ -1,81 +0,0 @@
----
-title: "getinflationrate"
-slug: "rpc-solana-getinflationrate"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:05 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const res = await tatum.rpc.getInflationRate()
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getInflationRate` method is used to retrieve the specific inflation values for the current epoch in the Solana blockchain.
-
-{% embed url=" %}
-
-### Parameters
-
-No parameters are required for this method.
-
-### Return Object
-
-The method returns a JSON object with the following fields:
-
-- `total`: Total inflation rate.
-- `validator`: Inflation allocated to validators.
-- `foundation`: Inflation allocated to the foundation.
-- `epoch`: The epoch for which these values are valid.
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc": "2.0",
- "id": 1,
- "method": "getInflationRate"
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "result": {
- "epoch": 100,
- "foundation": 0.001,
- "total": 0.149,
- "validator": 0.148
- },
- "id": 1
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getinflationreward.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getinflationreward.md
deleted file mode 100644
index 55365e54..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getinflationreward.md
+++ /dev/null
@@ -1,100 +0,0 @@
----
-title: "getinflationreward"
-slug: "rpc-solana-getinflationreward"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:38 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const addresses = ["Address1", "Address2", "Address3"]
-const config = {
- epoch: 2
-}
-
-const res = await tatum.rpc.getInflationReward(addresses, config)
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getInflationReward` method returns the inflation or staking reward for a list of addresses for a particular epoch on the Solana blockchain.
-
-### Parameters
-
-- An array of addresses (array of strings, optional): These are the addresses to query, as base-58 encoded strings.
-- A configuration object (optional): This object can contain the following fields:
- - `commitment` (string, optional): Specifies the level of commitment to apply when fetching data.
- - Values: `finalized` `confirmed` `processed`
- - `epoch` (number, optional): An epoch for which the reward occurs. If omitted, the previous epoch will be used.
- - `minContextSlot` (number, optional): The minimum slot that the request can be evaluated at.
-
-### Return Object
-
-The method returns a JSON array where each object represents the reward details for the corresponding address in the input array. Each object has the following fields:
-
-- `epoch`: The epoch for which the reward occurred.
-- `effectiveSlot`: The slot in which the rewards are effective.
-- `amount`: The reward amount in lamports.
-- `postBalance`: The post-balance of the account in lamports.
-- `commission` : The vote account commission when the reward was credited.
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc": "2.0",
- "id": 1,
- "method": "getInflationReward",
- "params": [
- [
- "6dmNQ5jwLeLk5REvio1JcMshcbvkYMwy26sJ8pbkvStu",
- "BGsqMegLpV6n6Ve146sSX2dTjUMj3M92HnU8BbNRMhF2"
- ],
- {"epoch": 2}
- ]
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "result": [
- {
- "amount": 2500,
- "effectiveSlot": 224,
- "epoch": 2,
- "postBalance": 499999442500
- },
- null
- ],
- "id": 1
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getlargestaccounts.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getlargestaccounts.md
deleted file mode 100644
index 455ba2df..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getlargestaccounts.md
+++ /dev/null
@@ -1,90 +0,0 @@
----
-title: "getlargestaccounts"
-slug: "rpc-solana-getlargestaccounts"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:00 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const res = await tatum.rpc.getLargestAccounts()
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getLargestAccounts` method returns the 20 largest accounts by lamport balance. This method may cache results for up to two hours.
-
-### Parameters
-
-- `options` (object, optional): A configuration object containing:
- - `commitment`(string, optional): Specifies the level of commitment to apply when fetching data.
- - Values: `finalized` `confirmed` `processed`
- - `filter` (string, optional): Filters the results by account type. Possible values are `circulating` or `nonCirculating`.
-
-### Return Object
-
-The result field will be an `RpcResponse` JSON object with a `value` field equal to an array of objects, each containing:
-
-- `address`: Base-58 encoded address of the account.
-- `lamports`: Number of lamports in the account.
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc": "2.0",
- "id": 1,
- "method": "getLargestAccounts"
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "result": {
- "context": {
- "slot": 54
- },
- "value": [
- {
- "lamports": 999974,
- "address": "99P8ZgtJYe1buSK8JXkvpLh8xPsCFuLYhz9hQFNw93WJ"
- },
- {
- "lamports": 42,
- "address": "uPwWLo16MVehpyWqsLkK3Ka8nLowWvAHbBChqv2FZeL"
- },
- // ...additional accounts...
- ]
- },
- "id": 1
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getlatestblockhash.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getlatestblockhash.md
deleted file mode 100644
index 77c35df9..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getlatestblockhash.md
+++ /dev/null
@@ -1,90 +0,0 @@
----
-title: "getlatestblockhash"
-slug: "rpc-solana-getlatestblockhash"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:01 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const res = await tatum.rpc.getLatestBlockhash({commitment: 'processed'})
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getLatestBlockhash` method returns the latest blockhash of the ledger. The blockhash is essential for transaction processing to ensure transaction uniqueness and to provide cryptographic security for the ledger. This method is critical in scenarios where the latest blockhash is needed for transaction signing or to confirm the most recent state of the blockchain.
-
-{% embed url=" %}
-
-### Parameters
-
-- `options` (object, optional): This object can contain the following fields:
- - `commitment`(string, optional): Specifies the level of commitment to apply when fetching data.
- - Values: `finalized` `confirmed` `processed`
- - `minContextSlot` (number, optional): The minimum slot that the request can be evaluated at.
-
-### Return Object
-
-The method returns a `RpcResponse` JSON object with `value` field set to a JSON object including:
-
-- `blockhash`: The latest blockhash as a base-58 encoded string.
-- `lastValidBlockHeight` : The last block height at which the blockhash will be valid.
-
-### JSON-RPC Request Example
-
-```json
-{
- "id":1,
- "jsonrpc":"2.0",
- "method":"getLatestBlockhash",
- "params":[
- {
- "commitment":"processed"
- }
- ]
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "result": {
- "context": {
- "slot": 2792
- },
- "value": {
- "blockhash": "EkSnNWid2cvwEVnVx9aBqawnmiCNiDgp3gUdkDPTKN1N",
- "lastValidBlockHeight": 3090
- }
- },
- "id": 1
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getleaderschedule.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getleaderschedule.md
deleted file mode 100644
index 5697af1c..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getleaderschedule.md
+++ /dev/null
@@ -1,91 +0,0 @@
----
-title: "getleaderschedule"
-slug: "rpc-solana-getleaderschedule"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:03 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const res = await tatum.rpc.getLeaderSchedule({
- identity: '4Qkev8aNZcqFNSRhQzwyLMFSsi94jHqE8WNVTJzTP99F'
-})
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getLeaderSchedule` method returns the leader schedule for an epoch. This method is useful for understanding the rotation of leadership among the validators, which is key in maintaining a decentralized and secure network. The schedule can be fetched for a specific epoch, or for the current epoch if no parameter is specified.
-
-### Parameters
-
-- `slot` (number, optional): Fetch the leader schedule for the epoch that corresponds to the provided slot. If unspecified, the leader schedule for the current epoch is fetched.
-- `options` (object, optional): A configuration object containing:
- - `commitment`(string, optional): Specifies the level of commitment to apply when fetching data.
- - Values: `finalized` `confirmed` `processed`
- - `identity` (string, optional): Only return results for this validator identity (base-58 encoded).
-
-### Return Object
-
-The method returns one of the two following values:
-
-- `null` - If requested epoch is not found.
-- `object` - The result field will be a dictionary of validator identities, as base-58 encoded strings, and their corresponding leader slot indices as values (indices are relative to the first slot in the requested epoch).
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc": "2.0",
- "id": 1,
- "method": "getLeaderSchedule",
- "params": [
- null,
- {
- "identity": "4Qkev8aNZcqFNSRhQzwyLMFSsi94jHqE8WNVTJzTP99F"
- }
- ]
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "result": {
- "4Qkev8aNZcqFNSRhQzwyLMFSsi94jHqE8WNVTJzTP99F": [
- 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20,
- 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38,
- 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56,
- 57, 58, 59, 60, 61, 62, 63
- ]
- },
- "id": 1
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getmaxretransmitslot.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getmaxretransmitslot.md
deleted file mode 100644
index a90d6a34..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getmaxretransmitslot.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: "getmaxretransmitslot"
-slug: "rpc-solana-getmaxretransmitslot"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:03 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const res = await tatum.rpc.getMaxRetransmitSlot()
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getMaxRetransmitSlot` method returns the highest slot number seen from the retransmit stage. This can be useful for monitoring the progress of the network or for determining the highest slot number that has been processed by a specific node.
-
-{% embed url=" %}
-
-### Parameters
-
-None
-
-### Return Object
-
-The method returns a value representing the highest slot number observed in the retransmit stage.
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc": "2.0",
- "id": 1,
- "method": "getMaxRetransmitSlot"
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "result": 1234,
- "id": 1
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getmaxshredinsertslot.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getmaxshredinsertslot.md
deleted file mode 100644
index cf78d713..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getmaxshredinsertslot.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: "getmaxshredinsertslot"
-slug: "rpc-solana-getmaxshredinsertslot"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:43 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const res = await tatum.rpc.getMaxShredInsertSlot()
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getMaxShredInsertSlot` method returns the highest slot number observed after a shred insert. This can be useful for monitoring the highest slot number that a specific node has processed after the shred insert stage, providing insights into the node's synchronisation status.
-
-{% embed url=" %}
-
-### Parameters
-
-None
-
-### Return Object
-
-The method returns a value representing the highest slot number observed after a shred insert.
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc": "2.0",
- "id": 1,
- "method": "getMaxShredInsertSlot"
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "result": 1234,
- "id": 1
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getminimumbalanceforrentexemption.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getminimumbalanceforrentexemption.md
deleted file mode 100644
index 4fe06c60..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getminimumbalanceforrentexemption.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: "getminimumbalanceforrentexemption"
-slug: "rpc-solana-getminimumbalanceforrentexemption"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:06 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const res = await tatum.rpc.getMinimumBalanceForRentExemption(50)
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getMinimumBalanceForRentExemption` method returns the minimum balance required to make an account rent exempt. This is useful when setting up a new account or assessing the cost of maintaining an account in a rent-free state.
-
-{% embed url=" %}
-
-### Parameters
-
-- `dataSize` (number, optional): The account's data length.
-- `options` (object, optional): A configuration object containing:
- - `commitment`(string, optional): Specifies the level of commitment to apply when fetching data.
- - Values: `finalized` `confirmed` `processed`
-
-### Return Object
-
-The result field will be a number indicating the minimum lamports required in the account to remain rent free.
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc": "2.0",
- "id": 1,
- "method": "getMinimumBalanceForRentExemption",
- "params": [50]
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "result": 500,
- "id": 1
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getmultipleaccounts.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getmultipleaccounts.md
deleted file mode 100644
index 4852b333..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getmultipleaccounts.md
+++ /dev/null
@@ -1,131 +0,0 @@
----
-title: "getmultipleaccounts"
-slug: "rpc-solana-getmultipleaccounts"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:06 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const accounts = [
- "GPHrLJNBeFDkHEChoN6CyHFLroen7jVU3HBmJQXvqGQa",
- "4DBehwe4U1gHaE575LZVnjN1MfyPSyWjidadRJoQcyAR",
- ];
-
-const res = await tatum.rpc.getMultipleAccounts(accounts)
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getMultipleAccounts` RPC method fetches information about multiple accounts. This is handy when you need to retrieve data about multiple accounts simultaneously, such as for a portfolio management application or a multi-account wallet.
-
-{% embed url=" %}
-
-### Parameters
-
-The `getMultipleAccounts` method accepts an array of public keys and an optional `GetMultipleAccountsOptions` object:
-
-- `publicKeys`(array of strings, required): An array of public keys of the accounts to be fetched.
- - Example: `["accountPubkey1", "accountPubkey2"]`
-- `options` (object, optional): Configuration object containing the following fields:
- - `commitment` (string, optional): Specifies the confirmation level of data to be fetched.
- - Values: `finalized` `confirmed` `processed`
- - `minContextSlot` (number, optional): The minimum slot to include in the response.
- - Example: `1000`
- - `dataSlice` (object, optional): The range of data to include in the response.
- - `offset` (number, optional): The starting index of the data slice.
- - Example: `0`
- - `length` (number, optional): The length of the data slice.
- - Example: `100`
- - `encoding` (string, optional): The encoding for the account data.
- - Values: `base58` `base64` `base64+zstd` `jsonParsed`
-
-### Return object
-
-The result will be a JSON object with `value` equal to an array of:
-
-- `null` - if the account at that Pubkey doesn't exist, or
-- `object` - a JSON object containing:
- - `data`: `[string, encoding]|object` - data associated with the account, either as encoded binary data or JSON format `{program: state}` - depending on encoding parameter
- - `executable`: A boolean indicating whether the account is executable.
- - `lamports`: The current balance of the account, in lamports.
- - `owner`: The public key of the account's owner.
- - `rentEpoch:`The epoch at which this account will next owe rent, as u64
- - `size:`The data size of the account
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc": "2.0",
- "id": 1,
- "method": "getMultipleAccounts",
- "params": [
- ["accountPubkey1", "accountPubkey2"],
- {
- "commitment": "finalized",
- "minContextSlot": 1000,
- "dataSlice": { "offset": 0, "length": 100 },
- "encoding": "base64"
- }
- ]
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc":"2.0",
- "id":1,
- "result":{
- "context":{
- "slot":123456
- },
- "value":[
- {
- "owner": "Base58('11111111111111111111111111111111')",
- "lamports": 1000000,
- "data": "Base64('...')",
- "executable": false,
- "rentEpoch": 20,
- "size": 120
- },
- {
- "owner": "Base58('11111111111111111111111111111111')",
- "lamports": 1000000,
- "data": "Base64('...')",
- "executable": false,
- "rentEpoch": 20,
- "size": 120
- }
- ]
- }
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getprogramaccounts.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getprogramaccounts.md
deleted file mode 100644
index 75af33c5..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getprogramaccounts.md
+++ /dev/null
@@ -1,131 +0,0 @@
----
-title: "getprogramaccounts"
-slug: "rpc-solana-getprogramaccounts"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:42 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to use it
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const res = await tatum.rpc.getProgramAccounts('BPFLoaderUpgradeab1e11111111111111111111111')
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getProgramAccounts` RPC method retrieves all accounts owned by a specific program on the Solana blockchain. This method can be useful when monitoring the state of a program or tracking the accounts associated with a particular smart contract.
-
-Currently pagination is not supported. Requests to `getProgramAccounts` should include the `dataSlice` and/or `filters` parameters to improve response time and return only intended results.
-
-### Parameters
-
-The `getProgramAccounts` method accepts a program ID and an optional object:
-
-- `programId`(string, required): Pubkey of program, as base-58 encoded string
- - Example: `"BPFLoaderUpgradeab1e11111111111111111111111"`
-- `options` (object, optional): Configuration object containing the following fields:
- - `commitment` (string, optional): Specifies the confirmation level of data to be fetched.
- - Values: `finalized` `confirmed` `processed`
- - `minContextSlot` (number, optional): The minimum slot that the request can be evaluated at
- - Example: `123456`
- - `withContext` (boolean, optional): Whether to wrap the result in an RpcResponse JSON object
- - Example: `true`
- - `encoding` (string, optional): The encoding format for the returned Account data
- - Example: `base58` `base64` `base64+zstd` `jsonParsed`
- - `dataSlice` (object, optional): Limit the returned account data using the provided \`offset: number\` and \`length: number\` fields;
- - only available for "base58", "base64" or "base64+zstd" encodings.
- - Example: `{ offset: 0, length: 100 }`
- - `filters` (array, optional): An array of filter objects to filter the accounts based on certain conditions.
- - Example: `[{ memcmp: { offset: 0, bytes: "base64" } }`
-
-### Return object
-
-The `getProgramAccounts` method returns an array of objects, each containing the following fields:
-
-- `pubkey`: The public key of the account.
-- `account`: An object containing:
- - `data`: The account's data, encoded according to the requested format.
- - `executable`: Whether the account is executable.
- - `lamports`: The account's current balance.
- - `owner`: The account's owner public key.
- - `rentEpoch`: The epoch at which the account will owe rent again.
- - `size`: The data size of the account
-
-If `withContext` is set to true, the response will also include a `context` object:
-
-- `context`: An object containing details about the context in which the data was fetched.
- - `slot`: The slot at which the data was fetched.
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc": "2.0",
- "id": 1,
- "method": "getProgramAccounts",
- "params": [
- "BPFLoaderUpgradeab1e11111111111111111111111",
- {
- "commitment": "finalized",
- "minContextSlot": 123456,
- "withContext": true,
- "encoding": "base64",
- "dataSlice": { "offset": 0, "length": 100 },
- "filters": [{ "memcmp": { "offset": 0, "bytes": "base64" } }]
- }
- ]
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "id": 1,
- "result": {
- "context": {
- "slot": 123456
- },
- "value": [
- {
- "pubkey": "9ehXDD5bnhSpFVRf99veikjgq8VajtRH7e3D9aVPLqYd",
- "account": {
- "data": "base64 encoded data",
- "executable": false,
- "lamports": 10000,
- "owner": "BPFLoaderUpgradeab1e11111111111111111111111",
- "rentEpoch": 10
- "size": 120
- }
- }
- //... more accounts
- ]
- }
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getrecentperformancesamples.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getrecentperformancesamples.md
deleted file mode 100644
index 9f326aa3..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getrecentperformancesamples.md
+++ /dev/null
@@ -1,109 +0,0 @@
----
-title: "getrecentperformancesamples"
-slug: "rpc-solana-getrecentperformancesamples"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:05 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const res = await tatum.rpc.getRecentPerformanceSamples(limit)
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getRecentPerformanceSamples` method returns a list of recent performance samples, in reverse slot order. Performance samples are taken every 60 seconds and include the number of transactions and slots that occur in a given time window. This data can be used to monitor network performance and understand the activity within the Solana network.
-
-{% embed url=" %}
-
-### Parameters
-
-- `limit` (usize, optional): The number of samples to return (maximum 720).
-
-### Return Object
-
-The result will be an array of objects with the following fields:
-
-- `slot`: Slot in which sample was taken at.
-- `numTransactions`: Number of transactions in sample.
-- `numSlots`: Number of slots in sample.
-- `samplePeriodSecs`: Number of seconds in a sample window.
-- `numNonVoteTransaction`: Number of non-vote transactions in sample.
-
-Note: `numNonVoteTransaction` is present starting with v1.15. To get the number of voting transactions, compute: numTransactions - numNonVoteTransaction.
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc":"2.0",
- "id":1,
- "method":"getRecentPerformanceSamples",
- "params": [4]
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "result": [
- {
- "numSlots": 126,
- "numTransactions": 126,
- "numNonVoteTransaction": 1,
- "samplePeriodSecs": 60,
- "slot": 348125
- },
- {
- "numSlots": 126,
- "numTransactions": 126,
- "numNonVoteTransaction": 1,
- "samplePeriodSecs": 60,
- "slot": 347999
- },
- {
- "numSlots": 125,
- "numTransactions": 125,
- "numNonVoteTransaction": 0,
- "samplePeriodSecs": 60,
- "slot": 347873
- },
- {
- "numSlots": 125,
- "numTransactions": 125,
- "numNonVoteTransaction": 0,
- "samplePeriodSecs": 60,
- "slot": 347748
- }
- ],
- "id": 1
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getrecentprioritizationfees.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getrecentprioritizationfees.md
deleted file mode 100644
index d52fa8e1..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getrecentprioritizationfees.md
+++ /dev/null
@@ -1,102 +0,0 @@
----
-title: "getrecentprioritizationfees"
-slug: "rpc-solana-getrecentprioritizationfees"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 12:59:40 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const accounts = ['CxELquR1gPP8wHe33gZ4QxqGB3sZ9RSwsJ2KshVewkFY']
-
-const res = await tatum.rpc.getRecentPrioritizationFees(accounts)
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getRecentPrioritizationFees` method returns a list of prioritization fees from recent blocks. This method can be used to determine the fees required to prioritize transactions for faster processing.
-
-{% embed url=" %}
-
-### Parameters
-
-- `accountAddresses` (array, optional): An array of account addresses (up to a maximum of 128 addresses), as base-58 encoded strings.
-
- **Note**: If this parameter is provided, the response will reflect a fee to land a transaction locking all of the provided accounts as writable.
-
-### Return Object
-
-The result is an array of objects with the following fields:
-
-- `slot`: The slot in which the fee was observed.
-- `prioritizationFee`: The per-compute-unit fee paid by at least one successfully landed transaction, specified in increments of 0.000001 lamports.
-
-### JSON-RPC Request Example
-
-```json
-{
- "jsonrpc": "2.0",
- "id": 1,
- "method": "getRecentPrioritizationFees",
- "params": [
- ["CxELquR1gPP8wHe33gZ4QxqGB3sZ9RSwsJ2KshVewkFY"]
- ]
-}
-```
-
-### JSON-RPC Response Example
-
-```json
-{
- "jsonrpc": "2.0",
- "result": [
- {
- "slot": 348125,
- "prioritizationFee": 0
- },
- {
- "slot": 348126,
- "prioritizationFee": 1000
- },
- {
- "slot": 348127,
- "prioritizationFee": 500
- },
- {
- "slot": 348128,
- "prioritizationFee": 0
- },
- {
- "slot": 348129,
- "prioritizationFee": 1234
- }
- ],
- "id": 1
-}
-```
diff --git a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getsignaturesforaddress.md b/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getsignaturesforaddress.md
deleted file mode 100644
index 04ea2131..00000000
--- a/v1.0/RPC Nodes/rpc-others/rpc-solana/rpc-solana-getsignaturesforaddress.md
+++ /dev/null
@@ -1,106 +0,0 @@
----
-title: "getsignaturesforaddress"
-slug: "rpc-solana-getsignaturesforaddress"
-excerpt: "Solana RPC"
-hidden: false
-metadata:
- description: "Solana RPC"
- image: []
- keywords: "solana, rpc"
- robots: "index"
-createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Sat Apr 06 2024 13:09:03 GMT+0000 (Coordinated Universal Time)"
----
-[block:html]
-{
- "html": "
\n
Archive Method
\n
Only on the full archive nodes. Complex queries might take longer and incur additional cost
\n
"
-}
-[/block]
-
-
-### How to Use It
-
-{% code overflow="wrap" lineNumbers="true" %}
-
-```javascript
-// yarn add @tatumio/tatum
-
-import { TatumSDK, Solana, Network } from '@tatumio/tatum'
-
-const tatum = await TatumSDK.init({ network: Network.SOLANA })
-
-const address = 'H8UvHwUaXKmHyr1UzEy1y5F5KjU6kGXMDFddxEjqJ2Sn'
-const options = {limit: 10} // optional
-
-const res = await tatum.rpc.getSignaturesForAddress(address, options)
-
-await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs
-```
-
-{% endcode %}
-
-### Overview
-
-The `getSignaturesForAddress` method fetches the signatures for confirmed transactions that include the given address in their `accountKeys` list. Returns signatures backwards in time from the provided signature or most recent confirmed block. This is especially useful for tracking the transaction history of an address, auditing transactions, or for debugging purposes.
-
-### Parameters
-
-- `address`(string, required): The address for which to fetch the transaction signatures.
- - Example: `"H8UvHwUaXKmHyr1UzEy1y5F5KjU6kGXMDFddxEjqJ2Sn"`
-- `options` (object, optional): Configuration object containing the following fields:
- - `commitment` (string, optional): Specifies the confirmation level of data to be fetched.
- - Values: `finalized` `confirmed` `processed`
- - `minContextSlot` (number, optional): The minimum slot that the request can be evaluated at
- - Example: `1000`
- - `limit`(number, optional): The maximum number of signatures to return (between 1 and 1,000).
- - Example: `10`
- - `before`(string, optional): Start searching backwards from this transaction signature. If not provided the search starts from the top of the highest max confirmed block.
- - Example: `"5Z7dVQaRBAjBjJZVhdJygdAEyRm3N8D1BQot9aJuthFU"`
- - `until`(string, optional): Search until this transaction signature, if found before limit reached
- - Example: `"5Z7dVQaRBAjBjJZVhdJygdAEyRm3N8D1BQot9aJuthFU"`
-
-### Return Object
-
-An array of `