Ledger Metadata Access Utility

This utility furnishes the means to interface with distributed ledger data, primarily focused on retrieving the maximal issuance quantity for a specified digital asset on a designated network, resolving the numeric identifier for a given network name, and obtaining a restricted collection of Remote Procedure Call (RPC) addresses for a specific network identifier.

Operation

The utility exposes the subsequent capabilities:

• Fetch Asset Volume: Obtains the complete circulating supply of a token given its contract identifier and network ID.
• Resolve Network ID: Fetches the numeric ID corresponding to a provided network designation.
• Acquire Pruned RPC Feed: Retrieves a curated subset of RPC endpoints associated with a specific network ID.

Fetch Asset Volume

To ascertain the total issuance volume of a token, one must supply the network ID and the token's contract address.

Mandatory Inputs:

• chain_id: The unique numeric identifier of the distributed ledger substrate.
• token_address: The canonical contract location of the asset.

Illustrative Example:

To determine the full supply of the asset located at 0x6B2a01A5f79dEb4c2f3c0eDa7b01DF456FbD726a on network 56, utilize the following structure:

{ "chain_id": 56, "token_address": "0x6B2a01A5f79dEb4c2f3c0eDa7b01DF456FbD726a" }

The utility will subsequently yield the asset's total circulating volume, for example:

46141292590

Resolve Network ID

To ascertain the network's numeric ID, the network's formal name must be supplied.

Mandatory Input:

• chain_name: The textual designation of the distributed ledger environment.

Illustrative Example:

To resolve the network identifier for BNB Smart Chain Mainnet, employ the subsequent syntax:

{ "chain_name": "BNB Smart Chain Mainnet" }

The utility will then output the corresponding numeric identifier, for instance:

56

Acquire Pruned RPC Feed

To secure a filtered collection of RPC connection points, the network ID is required. Additional refinement can be applied using the isOpenSource flag and the tracking parameter.

Mandatory Input:

• chain_id: The numeric identifier of the distributed ledger substrate.

Optional Parameters:

• isOpenSource (optional): Criterion for filtering based on open-source availability status.
• tracking (optional): Filter selection based on tracking status (permitted values: none, yes, limited, unspecified).

Illustrative Example:

To retrieve the RPC access points for network ID 1, the following configuration is used:

{ "chain_id": "1" }

The utility will then furnish the scoped list of RPC addresses pertinent to network ID 1.