What is BESC Hyperchain?
BESC Hyperchain is a permissioned, EVM-compatible blockchain built on Hyperledger Besu and secured by IBFT 2.0 consensus. It is designed from the ground up for institutions, regulated businesses, and developers who need the full power of the Ethereum Virtual Machine — with compliance controls, instant finality, and a governed validator economy that no public chain delivers natively.
The Problem with Public Chains
Public blockchains like Ethereum, BNB Chain, and Polygon are permissionless by design. For consumer apps that's a feature. For institutions it creates problems that cannot be fixed at the application layer:
- Sanctioned addresses can transact freely — no protocol-level block exists on any major chain
- Validators are anonymous; no accountable party for block production
- Excluding a bad actor requires a hard fork (see: Ethereum DAO hack, 2016)
- Finality is probabilistic — Ethereum takes ~12 minutes for "safe" finality
- MEV allows validators to front-run and reorder user transactions for personal profit
BESC Hyperchain solves all of this at the protocol level — not the application layer.
What Makes It Different
| Feature | BESC Hyperchain | Ethereum | BNB Chain |
|---|---|---|---|
| Permissioning | ✅ Native, node-level enforcement | ❌ None | ❌ None |
| Finality | ✅ 3s — instant, deterministic | ⏳ ~12 min (2 epochs) | ⏳ ~45s |
| Validator vetting | ✅ Governance vote required | ❌ Anonymous (32 ETH) | ⚠️ Top 21 by stake |
| Compliance governance | ✅ Validator Court (on-chain jury) | ❌ Impossible | ❌ Impossible |
| MEV / front-running | ✅ Zero — round-robin, no competition | ❌ Significant | ❌ Significant |
| EVM compatibility | ✅ Full (Berlin → Cancun) | ✅ Full | ✅ Full |
| Block time | ✅ 3 seconds | 12 seconds | 3 seconds |
| Reorg possible? | ✅ No — mathematically impossible | ❌ Before 2 epochs | ❌ Yes |
Protocol-Level Permissioning — No Other EVM Chain Has This
Every transaction on BESC Hyperchain is evaluated against the Account Permissioning Contract the moment it arrives at any node. A blocked address cannot send a transaction through any path — the check happens before the transaction is accepted, queued, or forwarded to validators. There is no application-layer workaround, no alternate RPC endpoint, no direct contract call that bypasses this check. It is enforced in Besu itself at every node in the network simultaneously.
On Ethereum: if a sanctioned entity sends a transaction, anonymous validators include it — they have no compliance obligation and no mechanism to refuse. On BESC Hyperchain, the blocked address never reaches a validator.
Decentralized Compliance via Validator Court
Critically, no single person controls who gets blocked. All blocking decisions go through the on-chain Validator Court — a jury of active PoS validators who vote on every case within 48 hours. Community members file reports with on-chain evidence. Legal orders and OFAC sanctions are submitted as evidence and voted on. Verdicts execute automatically on-chain — no admin action.
In cases of active, imminent threats, operators may apply a temporary block to stop harm immediately. This automatically opens a Validator Court case — if validators vote to Dismiss, the block is lifted. No permanent action without a vote.
Instant Deterministic Finality
IBFT 2.0 delivers true finality in 3 seconds. The moment a block is committed by 3 of 4 consensus nodes, it is mathematically irreversible. No forks. No reorganizations. No uncle blocks.
| Chain | Time to True Finality |
|---|---|
| BESC Hyperchain | 3 seconds — deterministic |
| Ethereum | ~12 minutes (2 epochs) |
| BNB Chain | ~45 seconds (probabilistic) |
| Polygon PoS | ~5 minutes (Ethereum checkpoint) |
| Bitcoin | ~60 minutes (6 blocks) |
For settlement systems and financial applications, this eliminates an entire category of risk.
Vetted Validators, Zero MEV
BESC Hyperchain has two distinct layers — and it's important not to confuse them:
The 4 IBFT Relayers are the block-producing consensus nodes. They propose, vote on, and seal blocks every 3 seconds via the IBFT 2.0 protocol, and forward block rewards and gas fees into the Validator Registry after each block. They are not the governance validators — they are the chain's engine.
The Validator Registry (28+ validators) is where real governance voting happens. These are the validators who vote on compliance cases in the Validator Court, vote to approve new validator applicants, and can vote to deactivate misbehaving validators. They must pass a governance approval vote (>50% supermajority) from existing validators to be admitted, and cannot participate anonymously.
No public chain — Ethereum, BNB Chain, or Polygon — has an equivalent vetted, governed validator set with on-chain compliance voting.
Because proposers rotate deterministically round-robin, there is no competitive incentive to reorder transactions. Zero MEV. No sandwich attacks. No front-running. Transaction ordering is fair and predictable for every user on every block.
Full Cancun EVM — Zero Developer Friction
Despite being a permissioned chain, BESC Hyperchain runs a fully up-to-date EVM with all hardforks through Cancun active from genesis block 0. Every Ethereum tool works with zero modification:
MetaMask · Hardhat · Foundry · ethers.js v5/v6 · viem · web3.js · OpenZeppelin · Remix · Tenderly · Wagmi · RainbowKit · Gnosis Safe
Key Components
- Hyperledger Besu — The only enterprise Ethereum client with first-class permissioning support
- IBFT 2.0 Consensus — Byzantine fault-tolerant, instant finality, 4 authorized consensus nodes
- Validator Registry — On-chain staking economy with 28+ validators and proportional reward distribution every 3 seconds
- Validator Court — On-chain jury system for all compliance decisions — decentralized, automatic, immutable
- Cross-Chain Bridge — Native bridge to Ethereum, BNB Chain, XRP Ledger, and Solana
- Dual Explorers — USA (New York) + global Blockscout instances with AI-powered transaction classification
Native Token
BESC is the native currency (18 decimals). Used for gas, validator self-stake, and delegation. On external chains it is represented as wBESC (9 decimals) via the bridge.