FAQ
- What is Kaia?
- How does Kaia support Ethereum equivalence?
- What is Kaia’s gas policy?
- What is special about Kaia’s account structure?
- Where can I start dApp development with Kaia?
- Is Kaia Open Source?
- How can I initially fund my account?
- Any Kaia’s Public Node Providers for testing and development?
- Are there faucets to get test KAIA?
- How do I check for Public RPC endpoint status?
- Which wallets support Kaia?
- What is Mainnet, what is Kairos?
- Are there any Kaia SDKs? In what languages?
- Must I install and run an EN (Endpoint Node) to use Kaia?
- I am running an EN, and node data sync is too slow.
- Can I use ERC-20 and ERC-721 contracts on Kaia?
- Where can I get a browser extension wallet like Metamask?
- Why is my fee-payer account address not derived from the key provided?
- Where can I find complete working samples of fee-delegation?
What is Kaia?
Kaia is a high-performance Layer 1 blockchain designed for the mass adoption of Web3, particularly in Asia. It offers over 4,000 TPS, immediate finality, and one-second block times. Fully compatible with Ethereum, Kaia enables seamless dApp migration and provides a robust ecosystem with developer-friendly tools, low fees, and strong liquidity from an ecosystem fund. It prioritizes Web2 user accessibility through integrations with major messaging platform like Kakao and LINE. For details, see our White Paper.
How does Kaia support Ethereum equivalence?
Kaia is EVM-compatible and supports all Ethereum Cancun EVM features except EIP-4844 blob transactions. It provides the eth
namespace RPC API, allowing seamless use of Ethereum SDKs and tools. Kaia-specific transaction types are represented as Type 0 legacy transactions within the eth namespace APIs, so Ethereum SDKs do not need to be aware of them.
What is Kaia’s gas policy?
Kaia uses a dynamic gas fee model that maintains low fees during normal network conditions but adjusts fees based on network congestion. The gas fee can change within a limited range per block, helping prevent network spam while keeping fees predictable. A portion of every transaction fee is automatically burned. The model prioritizes user experience and enterprise-friendliness while maintaining network stability.