Differences from Ethereum

How Chiliz Chain differs from Ethereum for EVM developers: a fork of BNB Smart Chain with PoSA consensus, ~3-second blocks, CHZ gas, CAP-20 Fan Tokens, and full EVM tooling compatibility.

If you are coming from Ethereum, most of what you know still applies: Chiliz Chain is EVM-compatible, so contracts written in Solidity deploy without modification and standard tooling (Hardhat, Foundry, viem, ethers, MetaMask, OpenZeppelin) works out of the box.

The key point: Chiliz Chain is a fork of BNB Smart Chain (BSC), which itself took Ethereum's EVM but not its consensus.

So Chiliz Chain is identical to Ethereum at the contract level, but BSC-like at the consensus and economic level.

At a glance

Property	Ethereum	Chiliz Chain
Consensus	Proof of Stake (Gasper)	Proof of Staked Authority (PoSA)
Block-producing validators	Hundreds of thousands, permissionless	13, elected (as of 2026)
Block time	~12 seconds	~3 seconds
Finality	Deterministic, ~13 minutes (2 epochs)	Probabilistic (~15 to 100 blocks, by tx value)
Gas token	ETH	CHZ
Fee model	EIP-1559 (base fee + priority tip)	EIP-1559 (base fee + priority tip)
Mainnet chain ID	1	88888
Testnet chain ID	(varies)	88882 (Spicy)
EVM version	Prague	Prague
Solidity	Latest	Up to 0.8.30
Max contract size	24 KB	24 KB
Native token standard	ERC-20	CAP-20 (Fan Tokens)

Consensus, block time, and finality

Ethereum uses permissionless Proof of Stake with a very large validator set. Chiliz Chain uses Proof of Staked Authority (PoSA), a hybrid of Proof of Authority and Proof of Stake with a small, elected set of block-producing validators (currently 13). They are elected each epoch and changes over time; the current validators are listed on the staking dApp.

An epoch on Chiliz Chain is:

• Chiliz Mainnet: 28,800 blocks, roughly 1 day.

• Spicy Testnet: 7,200 blocks, roughly 6 hours.

Finality on Chiliz Chain is probabilistic: the deeper a block is buried, the less likely a reorganization becomes. On Mainnet, supermajority (2/3) confirmation is reached at a median of 14 blocks (~42 seconds, up to ~35 blocks in the worst case), and full validator-set confirmation at a median of 47 blocks (~141 seconds).

As a practical guide, wait for more confirmations the more value is at stake:

Transaction value	Suggested confirmations	Approximate time
Low	15 blocks	~45 seconds
Standard	40 blocks	~2 minutes
High	100 blocks	~5 minutes

Read more in Consensus Mechanisms and About Validators.

Gas and fees

Chiliz Chain implements EIP-1559, so fee estimation and priority fees behave the way Ethereum developers expect.

There are two practical differences:

• The gas token is CHZ, not ETH. The deployer wallets must be funded with CHZ.

• The base fee is 2500 gwei.

Current network fee minimums:

• EIP-1559 transactions: set priority fee to at least 1 gwei and max fee per gas to at least 2501 gwei (2500 base + 1 priority).

• Legacy transactions: set gas price to at least 2501 gwei.

Transaction fees are typically well under $0.01. For live figures, see the scan.chiliz.com gas tracker.

Fan Tokens and CAP-20

Chiliz Chain's native token is the Fan Token, issued under the CAP-20 standard.

CAP-20 is functionally equivalent to Ethereum's ERC-20. Since the 2026 Decimal Fan Token migration, CAP-20 tokens use 18 decimals, like standard ERC-20 tokens.

See About Fan Tokens and the CAP-20 glossary entry.

Interoperability

Chiliz Chain is interoperable with Ethereum and other chains through LayerZero OFT bridging. See Use Omnichain Tokens.

What is the same as Ethereum

You do not need to relearn these:

• Solidity contracts deploy unchanged (compile for EVM version Prague, Solidity up to 0.8.30).

• Hardhat, Foundry, Remix, viem, ethers, and web3.js all work by pointing at a Chiliz RPC endpoint.

• MetaMask and other EVM wallets work after adding the network.

• OpenZeppelin contracts and standard ERC interfaces work as-is.

• The 24 KB max contract size (EIP-170) applies, exactly like Ethereum.

Gotchas when migrating a contract from Ethereum

Most contracts port over untouched.

Watch for these Chiliz-specific behaviors:

• Gas token is CHZ. Anywhere your scripts or contracts assume ETH for gas or value, use CHZ instead.

• Fan Token decimals. Fan Tokens used 0 decimals until the 2026 Decimal migration, and now use 18. If your contract interacts with Fan Tokens, do not hardcode a decimals value: read token.decimals() dynamically, since legacy 0-decimal contracts may still be encountered on-chain. See Write a Smart Contract and the 2026 migration page.

• Smaller validator set. With a small block-producing validator set (currently 13), decentralization and reorg assumptions differ from Ethereum. For high-value operations, wait a few blocks for finality.

• System contracts. Chiliz Chain carries system contracts at fixed addresses (for example the validator set and staking contracts). They generally do not interfere with application contracts, but you may see transactions to low system addresses on the explorer. See Smart Contract Addresses.

Migration checklist

• Point your tooling at a Chiliz RPC endpoint and chain ID 88888 (Mainnet) or 88882 (Spicy Testnet).

• Fund your deployer wallet with CHZ.

• Compile for EVM version Prague, Solidity up to 0.8.30.

• If you interact with Fan Tokens, handle 18 decimals and read decimals() dynamically.

• Keep deployed contracts within the 24 KB limit.