The chain underneath transactions that move.
MakaChain is an EVM-native Layer 1 with Proof of Authority consensus, tuned for one thing: settling payments in one block, at a predictable cost, with finality you can build a business on.
- ~4,500 TPS
- 1-block finality
- $0.10 per transaction
- Chain ID 777178
Familiar to build on. Different where it counts.
MakaChain runs a Proof of Authority consensus on a battle-tested PoA core, with a fully EVM-native execution layer on top. Builders keep every tool they know; the chain itself is rebuilt around settlement instead of speculation.
- Layer 01
Settlement field
The shared ledger every transaction lands on, final and spendable, behind both the merchant and the wallet.
- Layer 02
Proof of Authority consensus
A battle-tested PoA core where a known set of validators produces and confirms blocks. The result is deterministic, one-block finality instead of probabilistic waiting.
- Layer 03
EVM execution
Solidity contracts, the same opcodes, the same tooling. ethers, viem, Hardhat, and Foundry all point at MakaChain unchanged.
- Layer 04
Applications
MakaPay merchant settlement, the MakaWallet consumer app, stablecoin issuers, and any contract you deploy.
EVM-native, not EVM-adjacent
There is no translation layer and no custom VM to learn. The bytecode you ship to Ethereum runs on MakaChain as-is, so day-one deployment is the normal case, not a porting project.
Proof of Authority for predictable cost
A known validator set removes the auction dynamics that make general-purpose chains volatile to price. That is how MakaChain holds fees flat and predictable, whatever the amount you move.
Battle-tested PoA core, retuned for payments
We started from a battle-tested consensus engine and tuned it for one workload: high-volume value transfer that has to settle now, not eventually.
One-block finality
Deterministic settlement you can build a business on, with no probabilistic waiting.
The numbers settlement needs.
Throughput, finality, and cost are the only metrics a payment rail is judged on. Here is where MakaChain stands.
- Throughput~4,500 TPSSustained, not a peak benchmark figure.
- Finality1 blockDeterministic. No confirmations to wait on, no probabilistic settling.
- Transaction fee$0.10Flat across transaction size, by design of the PoA fee model.
- ExecutionEVM‑nativeFull Solidity and EVM-tooling compatibility, no shims.
- ConsensusProof of AuthorityBattle-tested PoA core, validator-secured.
- Chain ID777178Add MakaChain to any EVM wallet or client.
Performance figures are client representations and are editable as the network evolves. Chain, bridge, and smart contracts audited by Hacken and Halborn.
Audited, validator-secured, and built to be checked.
Payment rails are only as good as their security posture. MakaChain's chain, bridge, and smart contracts have been audited by Hacken and Halborn, and the network is secured by a known validator set that produces and confirms every block.
Hacken and Halborn, chain, bridge, and smart contracts
Hacken and Halborn reviewed the MakaChain chain, bridge, and smart contracts. The full Hacken report is published for anyone who wants to read the findings firsthand.
Read the Hacken reportValidator-secured
Blocks are produced and confirmed by a known set of validators rather than anonymous miners, which is what makes one-block finality safe to rely on.
Deterministic finality
Once a block confirms, it is final. There are no reorgs to plan around and no settlement that can be quietly unwound.
Audited scope
The chain, the cross-chain bridge, and the smart contracts were reviewed in the same Hacken and Halborn engagement, so every boundary where value moves was checked together.
Open to inspection
Specs, RPC reference, and node software are documented so integrators can verify behaviour instead of taking claims on trust.
The life of a transaction.
The homepage shows you that a payment settles. Here is the path it actually takes through the network, from a signed request to final, spendable funds.
- 01
Submit
A user signs a transaction in MakaWallet, or a customer pays a MakaPay merchant. It is broadcast to a MakaChain RPC endpoint.
- 02
Propagate
The transaction enters the mempool and is gossiped across the validator set so every block producer sees the same pending state.
- 03
Validate
A validator includes it in the next block and the Proof of Authority set confirms it, executing the EVM state change.
- 04
Finalize
The block reaches deterministic finality in a single block. There is no confirmation count to wait through and no reorg risk.
- 05Final
Settle
Funds land final and spendable on the settlement field. No holds, no chargebacks.
Like a card network authorizing and clearing a payment, except authorization and clearing are the same step and it finishes in one block instead of two days.
$MAKA and MFUEL, kept straight.
Two names show up when you read deep enough into the network, and they are not the same thing. $MAKA is the network's public token. MFUEL is the gas unit transactions are metered in at the protocol and developer layer.
$MAKA is the single public token of the MakaChain network, the asset you hold, send, and see referenced everywhere across the ecosystem and exchanges.
MFUEL is the unit gas is denominated in when you read the protocol or the developer docs. It meters computation and fees under the hood; it is not a separate token you buy or trade.
- Role
- $MAKA: The network's public token and ticker.
- MFUEL: The gas unit that meters execution and fees.
- Where you see it
- $MAKA: Marketing, ecosystem, wallets, exchanges.
- MFUEL: The protocol layer and developer documentation.
- Who handles it
- $MAKA: Anyone holding or moving value on MakaChain.
- MFUEL: Builders reading specs and estimating transaction cost.
- Buy or trade it?
- $MAKA: Yes, it is the public token.
- MFUEL: No, it is an accounting unit for gas, not an asset.
If you are building on MakaChain, you will meet MFUEL the moment you read the gas section of the docs. If you are using the network, $MAKA is the only token you need to think about.
Technical questions, answered directly
The specifics developers and integrators ask about most — fees, consensus, finality, and network parameters.
Last updated August 28, 2026
MakaChain charges a flat fee of $0.10 USD-equivalent per transaction. The fee is the same regardless of which token you send, how much you send, or how busy the network is. It is deducted from the asset you are transferring rather than requiring a separate gas token.
Because the fee is fixed rather than variable, cost per transaction is predictable at any volume — there is no fee spike during periods of high network activity.
No. MakaChain lets you pay transaction fees in the token you are transferring. If you send USDT or USDC, the $0.10 fee is deducted from that same amount. You do not need to hold MAKA in your wallet in order to transact.
Validators are compensated through a minting process equivalent to the fees generated, rather than by direct conversion of every fee. A portion of collected fees is used for burn and liquidity reinforcement.
MakaChain uses Proof of Authority (PoA) consensus, in which a permissioned set of validators produces blocks. This provides deterministic finality and predictable throughput. Validators are selected and hosted by established infrastructure providers across multiple countries and continents.
PoA means the validator set is permissioned rather than open. This is a deliberate design choice for a payment settlement network, where deterministic finality and predictable performance matter more than permissionless validation.
MakaChain achieves finality in a single block. A transaction is final once it is included in a block — there is no probabilistic confirmation period and no waiting for additional confirmations. Network throughput is approximately 4,500 transactions per second.
Single-block deterministic finality means a payment can be treated as settled as soon as it is included, which is the relevant property for merchant settlement.
MakaChain mainnet uses chain ID 777178, with the public RPC endpoint at https://rpc.makachain.io. Full mainnet and testnet network parameters are published in the developer documentation at makachain.io/developers.
- Chain ID
- 777178
- RPC URL
- https://rpc.makachain.io
- Explorer
- https://explorer.makachain.io
Yes. MakaChain has been audited twice by Hacken — once for the blockchain itself and once for bridging. Both reports are published in full. All security findings were resolved and approved by Hacken. MakaPay and MakaWallet have separately been audited by Halborn, with those reports pending publication.
Some observations in the reports were accepted rather than changed. These relate to intentional architectural decisions specific to how MakaChain operates as a permissioned payment network, not to unresolved defects.
MakaChain is EVM-compatible, so existing Ethereum tooling works without modification — Solidity, Hardhat, Foundry, ethers.js, viem and web3.js all work as they would on any EVM chain. Add the network using chain ID 777178 and the RPC endpoint, then deploy as normal. Note that deploying contracts on MakaChain requires your wallet to be whitelisted first.
To request deployment access, contact contact@makachain.io with your wallet address. This is a requirement of MakaChain's permissioned architecture. Full setup instructions, network parameters and testnet details are at makachain.io/developers.
You have seen how it works. Now ship on it.
Bring your contracts and your wallet, point them at MakaChain, and deploy. The execution layer is standard EVM, so there is nothing new to learn before your first transaction settles.