1. How to Migrate from BscScan to BscTrace

Migrating from BscScan APIs to BscTrace/MegaNode requires switching from REST-based, module/action-style endpoints to JSON-RPC 2.0 calls (and MegaNode Enhanced APIs for transfers, token data, holders, etc.).

BscScan-style APIs rely heavily on:

• HTTP GET
• Query parameters
• Human-oriented response wrappers (status, message, result)

BscTrace/MegaNode rely on:

• JSON-RPC 2.0
• POST requests with structured method calls
• Direct blockchain-native return values (hex-encoded Wei, raw RPC objects)

This guide illustrates the differences clearly and provides concrete examples.

2. API Call Example — Getting Native Balance

This section shows the migration from BSCScan/Etherscan V2 balance API to MegaNode (JSON-RPC).

We break the example into:

1. cURL Comparison
2. Request Structure Comparison
3. Response Comparison
4. Summary of Key Differences

2.1 cURL Comparison

A) BscScan / Etherscan V2 (REST GET)

curl "https://api.etherscan.io/v2/api?apikey=YOUR_API_KEY&chainid=56&module=account&action=balance&address=0xfF3f428583c15a5681584e9e5e86e270418AC4d3&tag=latest"

B) BscTrace / MegaNode (JSON-RPC POST)

curl -X POST https://bsc-mainnet.nodereal.io/v1/YOUR_API_KEY \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "method": "eth_getBalance",
    "params": [
      "0xfF3f428583c15a5681584e9e5e86e270418AC4d3",
      "latest"
    ],
    "id": 1
  }'

2.2 Request Structure Comparison

2.3 Response Comparison

A) BscScan / Etherscan V2 Response

{
  "status": "1",
  "message": "OK",
  "result": "0"
}

Notable characteristics:

• Contains wrapper fields: status, message
• result is stringified Wei, decimal
• API is not purely blockchain-native; it is a browser-style wrapper

B) BscTrace / MegaNode JSON-RPC Response

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": "0x18b907bc31ae8172d100e0"
}

Notable characteristics:

• Pure JSON-RPC 2.0 format
• result is hexadecimal Wei (0x-prefixed)
• No wrapper fields (status, message)
• Directly compatible with Ethereum RPC tooling

2.4 Key Differences

3. Quick Tip: Searching for API

Users can quickly locate API methods using the built-in documentation search.

Navigate to: https://docs.nodereal.io → API Reference → Jump To → Search Here

This allows users to instantly find:

• RPC methods
• Enhanced APIs (nr_*)
• Trace-related APIs
• Token, asset, holder, and NFT endpoints

4. Supported API

I. Account Module APIs

The following APIs under the Account module can be mapped to MegaNode's supported methods, often involving standard RPC calls or MegaNode's enhanced asset/transfer APIs.

II. Token Module APIs

Token-related queries are supported either via direct eth_call on the contract methods (totalSupply, balanceOf) or via MegaNode's enhanced APIs for aggregated data and holders/inventory.

III. Block Module APIs

Block information can be obtained via standard RPC, or enhanced MegaNode APIs for aggregated daily statistics.

IV. Gas Tracker APIs

Gas price and usage information, including some historical and estimation features, can be migrated.

V. Log & Transaction APIs

Log retrieval uses standard RPC, and transaction status checks map to receipt lookups.

VI. Contracts APIs (Verification and Deployment)

Contract verification requires dedicated services, while creator information is available via tracing.

VII. Geth/Parity Proxy APIs (Standard RPC - Native Support)

All BSCScan Geth/Parity Proxy endpoints are directly supported by standard JSON-RPC methods available on MegaNode.

5. Not Supported API

These APIs are currently not supported by BscTrace or MegaNode. They may be added in the future depending on feature roadmap and indexing availability.

Other not supported functions:

• Get Estimation of Confirmation Time
• Retrieves the average daily block size.
• Retrieves the daily average time to mine a block.