⇄
KLV Reconcile
Cross-chain supply
Where does KLV supply actually live?
KLV began as a TRON TRC-20 token and migrated to native KleverChain. This page reconciles the two chains — how much supply sits on each, and whether it adds up to the fixed 10B cap.
Supply reconciliation
KleverChain
native · KLV
—
Holders
—
% of max supply
—
% of combined
—
TRON TRC-20
legacy · —
—
Holders
—
% of max supply
—
% of combined
—
True circulating · net of reserve
—
TRON-backing reserve
—
Fixed max supply
—
Combined raw · both totals
—
Combined ÷ max
—
—
KleverChain — top 50 holders
| # | Address (klv1…) | Balance · % of chain |
|---|---|---|
| Loading… | ||
TRON TRC-20 — top 50 holders
| # | Address (T…) | Balance · % of chain |
|---|---|---|
| Loading… | ||
TRON KLV is backed by a KleverChain reserve. The legacy TRON TRC-20 KLV is redeemable 1:1 for native KLV via Klever's two-way Swap bridge, so a KleverChain reserve wallet holds native KLV backing it. That reserve is counted on both chains — as native KLV inside KleverChain's total and as the TRON tokens it backs — which is why the raw combined total exceeds the 10B cap. Netting the reserve out reconciles supply to the cap.
Supply distribution, not per-wallet matching. KleverChain (
Supply distribution, not per-wallet matching. KleverChain (
klv1…) and TRON (T…) use different address formats and do not map 1:1 — this reconciles totals and distribution per chain, not individual wallets.