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.
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.
Cypress is the Klaytn mainnet, Baobab is a testnet. Below is information relating to each network.
- Klaytnscope : https://baobab.scope.klaytn.com
- Klaytn Wallet : https://baobab.wallet.klaytn.foundation
- Baobab Faucet : https://baobab.wallet.klaytn.foundation/faucet
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.
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.
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.