Explorer client

​

What it does

​

Why use it

• Check before you call. Confirm a user-supplied address is a verified contract, or a token with the decimals you expect, before you send a transaction to it.
• Load ABIs at runtime. For contracts the SDK doesn’t include, fetch the verified ABI instead of pasting it in by hand.
• Clear errors. Network failures, HTTP errors and bad addresses all throw ExplorerError or InvalidAddressError with a message that says what to do.

​

createExplorerClient

function createExplorerClient(options: { chainId: 677 | 968 }): ExplorerClient;

​

Example

import { createExplorerClient } from "@uzolabs/sdk/explorer";
import { getAddresses } from "@uzolabs/sdk/contracts";

const explorer = createExplorerClient({ chainId: 677 });
const { usdt, bridgeRouter } = getAddresses(677);

const info = await explorer.getAddressInfo(usdt);
console.log(info);

const contract = await explorer.getContract(bridgeRouter);
console.log(contract.name, contract.isVerified, contract.proxyType, contract.implementations);

{
  isContract: true,
  isVerified: true,
  name: 'Tether USD',
  token: { symbol: 'USDT', decimals: 6 }
}
TransparentUpgradeableProxy true eip1967 [ '0xD7F50Ee55787C8fFA82abD634801E56f0578a2B3' ]

​

Limits

• The client doesn’t retry or time out on its own. If BOTScan is slow, wrap calls in your own retry.
• BOTScan’s rate limits aren’t documented. Cache results that don’t change, such as a verified ABI.
• For anything else BOTScan offers, such as transaction history or logs, call its API directly. See Use the BOTScan API.

​

Next steps