Data governance

Data Methodology

How WE Terminal separates verified BOT Chain facts, official aggregate statistics, and curated research fields.

Provenance first
Live RPC

Verified network telemetry

Chain ID, latest and recent blocks, transaction counts, gas usage, utilization, timestamps, and gas price read from BOT Chain JSON-RPC.

Official explorer

Verified chain aggregates

Counters and 30-day daily series for accounts, transactions, fees, gas, block time, and network utilization from the BOT Chain explorer statistics service.

Modeled fields

Curated protocol research

Protocol profiles, financial fields, rankings, and research series remain curated until WE Terminal operates a contract-attributed indexer.

Metric definitions

Definitions used by the public network dashboard.

Active accounts

Unique externally owned accounts active during a complete UTC day, as published by BOT Chain explorer statistics.

Explorer Stats

Daily transactions

Transactions recorded during a complete UTC day. The separate 24-hour counter is explicitly labeled as rolling 24H.

Explorer Stats

Network utilization

Explorer-provided utilization ratio converted to a percentage. Approximate current-day points are excluded from daily comparisons.

Explorer Stats

Gas price

Current JSON-RPC gas-price reading, with the latest complete-day explorer average used only when the live RPC field is unavailable.

RPC + Explorer

Block time

Explorer-wide average block time. Recent-block sampling is also retained in the RPC adapter for operational verification.

Explorer Stats

Freshness policy

Public pages revalidate network output every 60 seconds. The global RPC status refreshes in the browser every 30 seconds.

Explorer series are cached for five minutes. Current UTC-day points marked approximate are excluded from complete-day comparisons.

Timeouts and partial failures produce degraded or unavailable states; WE Terminal does not invent replacement values.

Current boundary

WE Terminal does not yet claim verified protocol TVL, revenue, trading volume, users, or retention. Those fields require a canonical contract registry and dedicated event indexing.

Primary BOT Chain sources

Direct links used to verify network identity and inspect underlying public records.