Architecture Overview

BESC Hyperchain is built on five layers that work together to deliver a fast, compliant, and developer-friendly blockchain. Each layer solves a specific problem that public chains like Ethereum and BNB Chain leave unsolved.

Layer Stack

┌─────────────────────────────────────────────────────────────┐
│                    Application Layer                         │
│   Smart Contracts · Tokens · Bridge · DeFi · DApps          │
│   (any EVM contract works — zero modification required)      │
├─────────────────────────────────────────────────────────────┤
│                   EVM Execution Layer                        │
│   Cancun EVM · All Solidity Versions · Full Opcode Set       │
│   Berlin → London → Shanghai → Cancun — active from block 0 │
├─────────────────────────────────────────────────────────────┤
│                  Permissioning Layer                         │
│   Account Permissioning Contract · TX Gating at Node Level   │
│   Validator Court — on-chain jury for compliance decisions   │
├─────────────────────────────────────────────────────────────┤
│                   Consensus Layer                            │
│   IBFT 2.0 · 4 Vetted Relayer Nodes · 3-Second Blocks       │
│   Instant Deterministic Finality · Zero MEV                  │
├─────────────────────────────────────────────────────────────┤
│                    Network Layer                             │
│   Hyperledger Besu 23.7.3 · DevP2P / RLPx · Dual RPC        │
│   USA (New York) + Global (Asia-Pacific) infrastructure      │
└─────────────────────────────────────────────────────────────┘

Consensus: IBFT 2.0 — Instant Finality

Four authorized consensus nodes (called relayers) participate in block production using the Istanbul Byzantine Fault Tolerant v2 protocol. These nodes:

• Propose and vote on blocks every 3 seconds
• Require a 2/3 supermajority (3 of 4) to seal a block
• Tolerate 1 node failure without any service interruption
• Submit block rewards into the on-chain Validator Registry after each block

Because block proposers are known, authorized entities — not anonymous miners or anonymous stakers — finality is deterministic and instant. The moment 3 of 4 nodes commit a block, it is mathematically irreversible. There are no chain reorganizations, no uncle blocks, no probabilistic waiting periods.

How this compares: Ethereum needs ~12 minutes (2 epochs) for "safe" finality. BNB Chain needs ~45 seconds (15 blocks) for practical finality. BESC Hyperchain delivers finality in 3 seconds — permanently and with certainty.

See IBFT 2.0 Consensus → for the full technical breakdown.

Permissioning: Protocol-Level Compliance — Unique to BESC

Before any transaction enters the block, every node evaluates it against the Account Permissioning Contract (0x7fE182b8Dd4Af1cE7DeD446dB7174fbE6656695c). If the sender address is on the blocked list, the transaction is rejected at the node level and never reaches the network.

This is enforced at the Besu client level — it is not an application-layer firewall that can be bypassed by calling a contract directly. It applies to every transaction on the network, from every source.

How this compares: Ethereum, BNB Chain, Polygon, and Avalanche have no equivalent. Blocking a bad actor on Ethereum would require a contentious hard fork — as demonstrated by the DAO hack in 2016. On BESC Hyperchain, it requires a Validator Court vote.

Who controls it: The Validator Court — an on-chain jury of active PoS validators who vote on every blocking case. No single individual can permanently block an address. Network operators may apply emergency temporary blocks for active threats, but a validator vote is required for any permanent action.

See Account Permissioning → for the full governance model.

Validator Economy

Beyond the 4 IBFT relayer nodes, BESC Hyperchain has an on-chain Validator Registry (0x76bF888EB22f6d11AD8C2348847062db746647E0) where approved entities register as validators by self-staking BESC. Currently 28+ validators are registered.

The 4 relayer nodes forward the 0.002 BESC block reward — plus all gas fees from each block — into this registry after every block. Rewards are distributed proportionally to all registered validators and their delegators based on stake and commission rates.

New validators require a supermajority governance vote (>50% of active validators) to be admitted. Anonymous entities cannot simply stake to become a validator — the same governance process that runs the Validator Court also controls validator admission.

See Validator Registry → for contract details and staking mechanics.

EVM Compatibility

The EVM is fully up-to-date — Berlin, London, Shanghai, and Cancun hardforks are all active from genesis block 0. Every standard Ethereum opcode, precompile, and EIP is supported. Solidity contracts compile and deploy identically to Ethereum mainnet.

All standard tooling works with zero configuration changes beyond the RPC URL and chain ID: MetaMask, Hardhat, Foundry, ethers.js v5/v6, viem, OpenZeppelin, Remix, Tenderly, Wagmi, RainbowKit.

See EVM Compatibility → for the full specification.

Infrastructure

BESC Hyperchain operates geographically distributed infrastructure for low-latency access worldwide:

Endpoint	Location	URL
RPC (Primary)	New York, USA	https://hyper.beschyperchain.com
RPC (Global)	Asia-Pacific	https://rpc.beschyperchain.com
Explorer (Primary)	New York, USA	https://explorer2.beschyperchain.com
Explorer (Global)	Asia-Pacific	https://explorer.beschyperchain.com
Bridge	—	https://wbescbridge.com

Both RPC endpoints serve the same chain. Both explorers are full Blockscout v11 instances with the complete feature set — including AI-powered Account History that classifies every transaction in human-readable English.