Klaytn is the Layer 1 blockchain platform with low latency, high TPS and immediate finality. It is the optimal blockchain for building games and realizing the metaverse.
Klaytn 2.0 marks Klaytn’s transition to focus on the metaverse, supporting Ethereum Equivalence and the comprehensive Metaverse Package to facilitate blockchain building experience. To better understand Klaytn 2.0, please refer to our Light Paper.
Klaytn is EVM compatible, and supports all Ethereum London EVM features. Our
ethnamespace has been amended to be compatible with Ethereum’s. Ethereum toolings can be used seamlessly, and migration of Ethereum dApps have also become possible with minimal effort. Transaction types and fields are also equivalent to Ethereum’s.
Klaytn transitioned from a fixed gas fee policy to adopt a dynamic gas fee mechanism in order to combat arbitrage bots. Please refer to this article for more information.
To provide maximum convenience for dApp developers, Klaytn has devised a way to decouple private keys from addresses. As a result, you can easily implement multisig, whereby you create multiple private keys for a single account, with each key having different weights. Each key can be assigned with different roles as well.
Whether you are migrating from Ethereum, or building on Klaytn from scratch, we support all the necessary tools and infrastructure. You can test your smart contracts on Remix IDE using Klaytn Plugin or connect to MetaMask wallet and Kaikas. Klaytn’s sdk
caveris available as caver-js You can refer to our tutorials to try building a dApp on Klaytn.
Klaytn is most certainly open source! Take a look at our Github Organisation and you can start contributing to our Klaytn Documentation. Read more about our open-source policies here.
You may purchase KLAY on the exchange. The list of available exchanges can be found here: Coinmarketcap or Coingecko
Since we cannot guarantee uptime and stability of the endpoints, you can always check for node provider status here.
Klaytn is supported by the cold wallet D’cent, as well as a host of hot wallets like Kaikas, MetaMask and more. Please refer to the list here.
Cypress is the Klaytn mainnet, Baobab is a testnet. Below is information relating to each network.
- Klaytnscope : https://scope.klaytn.com
- Klaytn Wallet : https://wallet.klaytn.com
- Klaytnscope : https://baobab.scope.klaytn.com
- Klaytn Wallet : https://baobab.wallet.klaytn.foundation
- Baobab Faucet : https://baobab.wallet.klaytn.foundation/faucet
Also, check the porting guidelines from web3.js and from web3j. Because the syntactic of caver-js and caver-java are very similar to web3.js and web3j, porting should be minimal and very straightforward. But, no, you can not use web3.js or web3j to make a request against Klaytn.
Yes and No. Endpoint node validates the blocks and exposes RPC APIs to the outer world. EN is always needed for your application to interact with the Klaytn network. For those who simply want to try Klaytn APIs, you can try KAS (Klaytn API Service). KAS provides Klaytn Node API service that exposes RPC APIs of Klaytn networks (both Baobab and Cypress) as well as other useful API services. Note that KAS serves free API requests after user registration. For pricing plans, please refer to KAS pricing page.
Check the fast sync. Klaytn publishes the chain data every day. Chain data is a database snapshot that stores all blocks generated since the genesis. Download the latest chain data for the fast sync.
Further Klaytn-specific token standards can be defined. Follow the KIP (Klaytn Improvement Proposal) and join the discussion.
Yes. Truffle can be used in developing smart contracts on Klaytn with truffle-hdwallet-provider-klaytn. See Truffle and follow the configuration guideline.
If you are new to Truffle, see Testing Guide and Deployment Guide to get a rough idea on what you can do with Truffle.
Klaytn's web brower extension wallet Kaikas. Kaikas is a non-custodial wallet with which you can make KLAY transactions and create accounts.
Common use cases are as follows.
- The account owner wants to change the key for security reasons.
- The account has a weighted-multisig or a role-based key that allows having multiple key pairs to control the account.
Fee-payer accounts usually have a role-based key. In most cases, the account address is not derived from the RoleFeePayer key.
Sending a transaction with multiple signer gives a good explanation about two different ways of collecting signatures. Relevant caver-js APIs are as follows. Take a look at the code examples in the API description.