Mandala KPG: Ethereum Layer 2 Gas & Utility Token

Mandala KPG, also known as Kepeng, is the native gas token of Mandala Chain, an Ethereum Layer 2 built using the Arbitrum Orbit stack. Every transaction on Mandala Chain uses KPG for gas, giving the token a direct role in powering network activity. The name comes from the traditional Balinese kepeng coin, connecting Mandala’s blockchain infrastructure with its Indonesian roots. The network uses AnyTrust for data availability and settles on Ethereum Layer 1, while maintaining EVM compatibility for developers and applications.

Beyond its role as a gas asset, KPG is connected to Mandala Chain’s broader vision of modular and sovereign blockchain infrastructure. The platform highlights digital identity, AI-ready infrastructure, interoperability, enterprise applications, asset tokenization, finance, logistics, insurance, and other use cases. This article explores KPG’s role within Mandala Chain, how its Ethereum Layer 2 architecture works, and how the token fits into the project’s wider ecosystem.

For more insights and updates on the latest cryptocurrency trends, check out our Nifty Finances platform, your gateway to smarter financial decisions in the digital economy.

What Is Mandala KPG?

KPG, or Kepeng, is the native gas token of Mandala Chain. Mandala Chain identifies KPG as the network’s native currency and states that every transaction fee on Mandala is paid in KPG. This gives the token a fundamental role in the day-to-day operation of the blockchain, because users need KPG to pay for transactions and smart-contract activity on the network.

Mandala Chain is an Ethereum Layer 2 built using the Arbitrum Orbit stack, with Ethereum serving as its settlement layer. Although Mandala uses an EVM-equivalent execution environment, it does not use ETH as its native gas currency. Instead, the network uses KPG, giving Mandala its own native denomination for transaction fees.

KPG and Transaction Fees

The primary utility of KPG is paying for gas on Mandala Chain. Every transaction requires a network fee, and that fee is denominated in KPG rather than ETH. Mandala’s documentation notes that wallets display KPG balances, gas prices are expressed in KPG-gwei, and decentralized applications on the network estimate fees in KPG.

This distinction is important for users familiar with Ethereum or other EVM networks. The transaction process remains familiar because Mandala is EVM-equivalent, but the token used to pay for network execution is different. Developers can use standard Ethereum-compatible tools such as MetaMask, Hardhat, Foundry, ethers, and viem while configuring them for Mandala’s network.

In practical terms, KPG functions as the fuel that allows activity to take place on Mandala. Users interacting with smart contracts, sending transactions, or using applications deployed on the network need an appropriate KPG balance to cover those fees.

18 Decimals and Mandala Mainnet

KPG uses 18 decimals, the same decimal precision commonly associated with ETH and many EVM-compatible tokens. Mandala’s official network details list KPG (Kepeng) as the native currency of the mainnet and specify 18 decimals. The network itself has Chain ID 20010, while its canonical settlement chain is Ethereum L1.

The 18-decimal structure allows KPG to represent very small units of the native currency when calculating transaction fees. This is particularly relevant for blockchain applications, where gas costs can involve fractional token amounts rather than only whole units.

From Balinese Kepeng to Digital KPG

The name Kepeng connects Mandala’s digital gas token with a traditional Balinese form of currency. Mandala’s documentation explains that the name comes from the traditional Balinese kepeng coin, a perforated coin associated with ceremonial practices and village governance. The project presents KPG as a modern digital continuation of that cultural reference.

This gives KPG a cultural identity beyond its technical function. The original kepeng represents a historical form of exchange and community connection, while KPG applies the name to the native currency used to power transactions on a modern blockchain network.

The Foundation of Mandala’s Network Economy

KPG therefore combines a practical blockchain function with Mandala Chain’s Indonesia-rooted identity. Its primary utility is paying network gas fees, making it essential for transactions and smart-contract execution on Mandala mainnet. Other potential roles, including governance and staking, appear in Mandala’s broader tokenomics materials, but the project’s FAQ specifically identifies gas payment as KPG’s primary utility today.

Through this design, KPG serves as both the operational currency of Mandala Chain and a digital reference to the traditional Balinese kepeng.

KPG as Mandala Chain’s Native Gas Token

KPG, or Kepeng, serves as the native gas token of Mandala Chain. Mandala’s official documentation states that every transaction fee on the network is paid in KPG, making the token an essential part of how users interact with the blockchain. Mandala Chain is an Ethereum Layer 2 built on the Arbitrum Orbit stack, but instead of using ETH as its native gas currency, it uses KPG. The mechanics of paying transaction fees are similar to ETH-based networks; the primary difference is the token used to denominate those fees.

Paying for Transactions and Smart Contracts

When users send transactions on Mandala Chain, the network requires gas to process and execute those operations. KPG provides the currency used to pay those costs. This applies not only to straightforward transfers but also to activity involving smart contracts and decentralized applications deployed on Mandala.

For example, interacting with a smart contract can involve multiple computational operations, with the associated gas cost denominated in KPG. The amount required depends on the gas used by the transaction and the applicable gas price. Mandala’s documentation notes that the network uses KPG-gwei for gas pricing, giving users an Ethereum-like fee structure while replacing ETH with KPG as the underlying gas token.

This makes KPG part of the basic transaction process rather than simply an optional ecosystem asset.

KPG Performs the Gas Role of ETH

Users familiar with Ethereum can think of KPG as performing the role that ETH performs as the native gas currency on Ethereum. The underlying technologies differ because Mandala is an Arbitrum Orbit Layer 2, but the basic concept is similar: users need the network’s native gas token to pay for execution.

Mandala specifically notes that ETH bridged from Ethereum arrives on Mandala as ETH but is not used for gas. Bridged KPG, by contrast, becomes the user’s gas balance on the network.

This distinction is important when moving assets between Ethereum and Mandala. Holding ETH on Mandala does not automatically provide the KPG required to pay transaction fees.

Why Users Need KPG

KPG is therefore necessary for users who want to actively interact with Mandala applications. Without an adequate KPG balance, a wallet may hold other assets on the network but still be unable to submit transactions that require gas.

Mandala’s wallet documentation illustrates this directly: when adding Mandala to MetaMask, the wallet displays KPG as the network currency, and users need KPG to send transactions.

This applies across the ecosystem, including decentralized applications, token transfers, and smart-contract interactions. Developers can continue using familiar EVM tools such as MetaMask, Hardhat, Foundry, ethers, and viem, while configuring those tools for Mandala’s network and its KPG gas currency.

Current Gas Utility vs. Broader Tokenomics

Mandala’s documentation makes an important distinction between KPG’s current utility and potential additional functions. Paying gas is identified as KPG’s primary utility today. The project’s broader tokenomics describe possible roles involving governance, staking, and fee distribution, but Mandala states that these additional roles will be detailed when the relevant documentation is released.

This means KPG’s present role should be understood first and foremost as the operational currency that powers transactions on Mandala Chain. Its broader economic functions form part of the project’s wider tokenomics framework, but they should not be treated as current, fully documented utilities without further official specifications.

By making KPG the native gas token, Mandala gives its network an independent fee currency while retaining the familiar transaction model associated with EVM-compatible blockchains.

Mandala Chain’s Ethereum Layer 2 Architecture

Mandala Chain is an Ethereum Layer 2 built on the Arbitrum Orbit stack, using Arbitrum Nitro technology and AnyTrust data availability. Rather than operating as an independent blockchain disconnected from Ethereum, Mandala processes transactions on its own Layer 2 environment while settling its state on Ethereum Layer 1. This architecture gives developers an Ethereum-compatible environment while allowing Mandala to use its own native gas currency, KPG (Kepeng).

Built on Arbitrum Orbit

Mandala uses the Arbitrum Orbit framework as the foundation of its Layer 2 architecture. Its execution environment is EVM-equivalent, meaning applications designed for Ethereum or compatible Arbitrum environments can generally be deployed on Mandala without requiring developers to learn a different programming model. The official documentation states that the same Solidity, wallets, and development toolchain used for Arbitrum can be used on Mandala by pointing them toward the appropriate network RPC.

This compatibility extends to established Ethereum development tools, including Hardhat, Foundry, ethers, and viem. Developers can therefore continue using familiar workflows for writing, testing, deploying, and interacting with smart contracts.

EVM Compatibility for Ethereum Developers

Mandala’s EVM-equivalent design is particularly relevant for developers already familiar with Ethereum infrastructure. The network documentation states that Solidity compiler output, EVM opcodes, and standard precompiles behave identically to Ethereum in the relevant execution environment. In practical terms, moving an existing dApp to Mandala generally involves configuring the application and wallet for Mandala rather than rebuilding the application’s fundamental smart-contract architecture.

Developers can connect common EVM tools to Mandala using its network configuration, including:

• Hardhat and Foundry for smart-contract development and deployment.
• ethers and viem for application-side blockchain interaction.
• MetaMask and Rabby for wallet connectivity.
• Solidity for writing compatible smart contracts.

Transaction Batching and Ethereum Settlement

Mandala’s transaction flow separates execution from Ethereum settlement. The sequencer receives transactions, orders them, and produces Layer 2 blocks. The batch poster then bundles those transactions and sends the batch information toward Ethereum. Under Mandala’s AnyTrust configuration, the bulk of transaction data is stored by a Data Availability Committee, while a batch header and availability information are posted to Ethereum.

This approach allows Mandala to process activity on its Layer 2 while retaining Ethereum as the settlement layer. AnyTrust also reduces the amount of transaction data that needs to be posted directly to Ethereum compared with a full rollup-data approach.

Chain ID 20010 and Native KPG

Mandala mainnet uses Chain ID 20010 and identifies KPG (Kepeng) as its native currency. KPG has 18 decimals and serves as the network’s gas token. Unlike Ethereum, where ETH is used to pay gas, Mandala denominates transaction fees in KPG.

The use of KPG does not change the underlying EVM development model. Instead, it is one of the network-specific parameters developers and users need to account for when connecting wallets, deploying contracts, or interacting with applications.

Familiar Infrastructure With a Different Network

For Ethereum and Arbitrum developers, Mandala’s architecture is designed to minimize the technical differences involved in moving applications to another Layer 2. The core development concepts remain familiar: Solidity contracts, EVM execution, standard Ethereum tooling, and Ethereum-based settlement. The main network-specific details include Mandala’s Chain ID, RPC configuration, AnyTrust data-availability model, and KPG gas currency.

As a result, Mandala combines an Arbitrum-based Layer 2 architecture with Ethereum compatibility while maintaining its own network parameters and native KPG economy.

How AnyTrust Supports Mandala’s Infrastructure

Mandala Chain uses AnyTrust data availability (DA) as part of its Arbitrum Orbit architecture. Instead of posting the full transaction data directly to Ethereum, Mandala uses a Data Availability Committee (DAC) to store the bulk of that data. Ethereum still serves as the settlement layer, while the DAC handles the data availability component required for the Layer 2 to be independently verified. This design is one of the defining architectural characteristics of Mandala’s infrastructure.

Mandala’s AnyTrust Data Availability Model

In a conventional rollup configuration, transaction data is posted to Ethereum so that independent parties can retrieve it and reconstruct the Layer 2’s state. AnyTrust changes where that data is stored. Mandala’s batch poster sends the full transaction data to the DAC, while a smaller batch header containing information about the data is posted to Ethereum. The DAC then signs a Data Availability Certificate, which the batch poster includes with the Layer 1 batch information.

The result is a division of responsibilities between Ethereum and the DAC:

• Mandala’s sequencer orders transactions and produces Layer 2 blocks.
• The batch poster bundles transactions into batches.
• The DAC stores the bulk transaction data and provides availability certificates.
• Ethereum L1 receives the relevant batch information and provides the settlement layer.

This structure allows Mandala to retain the broader security and settlement framework of an Arbitrum-based Ethereum Layer 2 while moving most transaction-data storage away from Ethereum calldata.

Why AnyTrust Can Reduce Data-Posting Costs

A major architectural reason for using AnyTrust is that less transaction data needs to be posted directly to Ethereum. Ethereum does not receive the complete transaction payload for every batch in the same way that a full-data rollup would. Instead, the L1 receives the batch header and the information needed to establish that the associated data has been made available through the DAC.

Because Ethereum data posting can represent a significant component of Layer 2 operating costs, shifting bulk data storage to a DAC can substantially reduce the amount of L1 data that must be published. Mandala’s documentation describes this as roughly an order-of-magnitude cost difference compared with rollup-mode chains that post full transaction data to Ethereum. This should be understood as an architectural comparison, rather than a guarantee that individual Mandala transactions will always have a particular cost. Actual fees can vary according to network conditions and other factors.

The Trust Assumption Behind AnyTrust

The cost and data-availability benefits of AnyTrust come with a specific trust assumption. Mandala’s current documentation states that at least two DAC members must remain honest and online for transaction data to remain retrievable. If fewer than two members can provide the required data, the system is designed to stop advancing state until the data becomes available again.

This means the DAC is an important part of Mandala’s operational trust model. The committee cannot sign transactions on behalf of users or move user funds. However, if insufficient members remain available to serve transaction data, the chain’s progress can halt until the availability problem is resolved.

A Different Data-Availability Trade-Off

AnyTrust therefore represents a deliberate architectural trade-off. Mandala reduces its reliance on Ethereum for storing the full transaction-data payload by relying on a DAC, while Ethereum continues to provide the Layer 1 settlement environment. The model can make data posting more efficient, but it introduces a committee-based availability assumption that developers and users should understand.

AnyTrust is not simply a cost-saving feature. It is a fundamental part of how the network separates transaction execution, data availability, and Ethereum settlement, giving the chain its particular balance between infrastructure efficiency and trust assumptions.

Mandala KPG occupies a fundamental position within Mandala Chain as the network’s native gas token. Built around an Ethereum Layer 2 using Arbitrum Orbit and AnyTrust, Mandala provides an EVM-equivalent environment while using KPG rather than ETH to pay transaction fees. The token also carries the cultural identity of the traditional Balinese kepeng, linking the project’s Indonesian roots with its blockchain infrastructure.

Navigating the complexities of blockchain can be daunting, especially with fluctuating gas fees and intricate user interfaces. LightLink emerges as a beacon of simplicity in this landscape. As an Ethereum Layer 2 solution, LightLink offers instant, gasless transactions, eliminating the traditional barriers that deter many from embracing decentralized applications.

Beyond gas, Mandala’s broader ecosystem focuses on sovereign blockchain infrastructure, digital identity, AI-ready applications, interoperability, enterprise solutions, and real-world use cases. Governance, staking, and other token functions have been discussed by the project, but the current documentation identifies gas as KPG’s primary utility today. Understanding that distinction provides a clearer view of where KPG fits within Mandala Chain and how its role may expand alongside the network’s development.