Native BESC and genesis

Native BESC is BESC HyperChain's own coin. It pays for gas and sits directly in the chain's accounts, the same way ETH does on Ethereum or BNB on BNB Chain. It isn't a token contract, and it uses 18 decimals.

Its starting supply was created at genesis, in the chain's first block on August 20, 2025. The chain publicly launched on October 8, 2025 (per BESC's launch announcement). The native total in the live panel is the BESC HyperChain explorer's own total-supply figure.

According to the BESC team, nobody can mint native BESC after genesis. That can't be fully confirmed from explorer data alone, so this guide presents it as the team's statement.

New BESC from validator rewards

Validators are the computers that produce BESC HyperChain's blocks. For each block, the validator receives a reward of 0.002 BESC, as shown in the explorer's block-reward data.

According to the BESC team, these rewards are the only new native BESC created after genesis, and the team offsets this issuance with burns (see Burns below). The live panel multiplies the current block number by 0.002 to estimate the rewards paid since genesis.

Separately from those rewards, 499,418.66 BESC is currently staked with validators. It's held in the chain's validator registry contract and shown in the live panel as Staked with validators.

Wrapping: BESC and WBESC

Many apps on BESC HyperChain, such as decentralized exchanges, need a standard token contract rather than the chain's native coin. WBESC (wrapped BESC) fills that role. It works like ETH and WETH on Ethereum, and it also uses 18 decimals.

Say you wrap 1,000 BESC. Your 1,000 BESC are locked in the WBESC contract (not burned), and you receive 1,000 WBESC. When you unwrap, your 1,000 WBESC are burned and the contract releases your 1,000 BESC back to you.

So BESC and WBESC are the same coins in two forms. Adding them together would count the same coins twice.

WBESC is backed 1:1 by the native BESC locked in its contract. Right now, the BESC locked in the contract covers 100.00% of the WBESC supply. Both figures are in the live panel, and you can check them on the explorer.

Bridging to other chains

BESC also exists as wrapped tokens on other chains: wBESC on BNB Chain, Ethereum and Robinhood Chain, and a wrapped BESC token on Solana. The official bridge, wbescbridge.com, moves BESC between these chains and BESC HyperChain. The bridge holds native BESC in the bridge vault (0x5711…aB9d), the address the bridge app names as its receiver on BESC HyperChain.

Say you hold 100 wBESC on BNB Chain and bridge 50 of them to BESC HyperChain:

1. Your 50 wBESC are burned on BNB Chain.
2. The bridge releases 50 native BESC from its vault.
3. You now hold 50 BESC on BESC HyperChain, and still have 50 wBESC on BNB Chain.

Going the other way works in reverse: your native BESC goes into the vault, and the same amount of wrapped tokens is minted for you on the destination chain.

According to the BESC team, bridging only moves existing native BESC in and out of the vault; it doesn't create new native BESC.

Who holds the assets: both bridges, wbescbridge.com and bescbridge.com (USDC and BUSDC), are run by their operators' servers, and the assets behind them sit in ordinary wallets (EOAs), not in a contract, so nothing on-chain enforces that they stay there. The bridge vault above is one of those wallets: it is an EOA, and on-chain records show it has also made trades and liquidity transactions on BescSwap. The Bridges & exit liquidity section below shows what each bridge holds right now against the tokens it issued on BESC HyperChain.

A note on decimals: wBESC on BNB Chain, Ethereum and Robinhood Chain uses 9 decimals, while native BESC uses 18. Wallets and the bridge handle this for you, but it matters if you read balances directly from a contract.

Burns

Burning means sending coins to an address nobody controls. On BESC HyperChain that's the dead address, 0x0000…dEaD. Coins sent there can never move again. They stay visible at that address, so anyone can see how much has been burned; the live panel shows it as Burned forever.

wBESC can be burned the same way on BNB Chain, by sending it to the dead address there. The live panel shows that amount next to BNB Chain.

According to the BESC team, BESC is also burned alongside MONEY in MONEY burn events.

Why explorer totals can't just be added

Each explorer shows a total for its own chain. It's tempting to add them up, but that counts some coins more than once. Two examples:

Native BESC and WBESC

When 1,000 BESC are wrapped, the native supply still includes those 1,000 BESC, now locked in the WBESC contract, and the WBESC supply shows another 1,000. Adding both gives 2,000, but only 1,000 coins exist.

The bridge vault and wrapped tokens

When BESC is bridged out, the native coins go into the bridge vault and wrapped tokens are minted on the other chain. The same coins now show up in two places: as native BESC in the vault, and as wrapped tokens on the other chain's explorer. Adding both counts them twice.

That's why this guide shows each figure on its own, next to where it comes from, and doesn't add them into a single total.

Check it yourself

The live balances and token supplies are read from these addresses, and the native total from the BESC HyperChain explorer itself (see below the table). Open any address on its explorer to see the same numbers.

The native total is the BESC HyperChain explorer's own figure, which you can open directly at explorer.beschyperchain.com (the result is in wei, the smallest unit: divide it by 10¹⁸ to get BESC).

About sources: live figures are read from the addresses above or from the BESC HyperChain explorer, and the block number comes from the chain itself. “≈ issued since genesis” is an estimate (blocks × 0.002). The percentages are calculated from two read figures each: the WBESC backing from the BESC locked in the WBESC contract and WBESC's supply, and each native tile's share from its figure and the native total. Statements that come from the BESC team are marked “according to the BESC team”.