Introduction to Mandala Chain
What Mandala is, the stack it runs on, and where to read next.
Mandala Chain is an Ethereum Layer 2 built on the Arbitrum Orbit stack. It posts batches to Ethereum, settles via AnyTrust, and uses KPG (Kepeng) as its native gas token. If you can deploy on Arbitrum One, you can deploy on Mandala with the same toolchain, the same Solidity, and the same wallets pointed at a different RPC.
Kepeng (KPG) takes its name from the traditional Balinese kepeng coin, a perforated bronze coin still used in temple offerings and village governance across Bali. The native token of an Indonesia-rooted L2 carries that name forward.
Mandala at a glance
| Detail | Value |
|---|---|
| Chain ID | 20010 |
| Native gas token | KPG (Kepeng), 18 decimals |
| Stack | Arbitrum Orbit (Nitro), AnyTrust DA |
| Settlement | Ethereum L1 |
| Block production | On demand, only when there is a transaction |
| RPC | https://rpc1-mainnet.mandalachain.io |
| Explorer | explorer.mandalachain.io (Blockscout) |
How it fits together
Three layers, one transaction path. Your dApp talks to Mandala. Mandala batches transactions, hands the data to a Data Availability Committee (DAC), and posts a small batch header back to Ethereum.
Three things to notice in that picture:
- The DAC stores the bulk of transaction data, not Ethereum. That is what makes Mandala roughly an order of magnitude cheaper than rollups that post full data to Ethereum calldata.
- The sequencer is on demand. It produces a block when at least one transaction has arrived. There are no empty blocks and no fixed slot time.
- Withdrawals back to Ethereum still go through a challenge window. Funds bridged out of Mandala finalize on Ethereum after the standard Arbitrum dispute period.
The pages that follow expand on each of those.