LogoLogo
Getting StartedSmart ContractNodeBApp Developers
  • Welcome
  • Klaytn Overview
    • Why Klaytn
    • Klaytn Design
      • Consensus Mechanism
      • Accounts
      • Transactions
        • Basic
        • Fee Delegation
        • Partial Fee Delegation
      • Computation
        • Klaytn Smart Contract
        • Execution Model
        • Computation Cost
        • Klaytn Virtual Machine
      • Storage
      • Transaction Fees
      • Klaytn native coin - KLAY
      • Token Economy
      • Governance
      • Multi-Channel
      • KNI
    • Scaling Solutions
  • Getting Started
    • Quick Start
      • Launch an Endpoint Node
      • Top up your Account
      • Install Development Tools
      • Deploy a Smart Contract
      • Check the Deployment
    • Account Management
      • Creating Accounts
      • Managing Accounts
    • Development Environment
    • Getting KLAY
  • Smart Contract
    • Solidity - Smart Contract Language
    • Precompiled Contracts
    • IDE and Tools
      • Klaytn IDE
      • Truffle
    • Sample Contracts
      • KlaytnGreeter
      • ERC-20
        • 1. Writing ERC-20 Smart Contract
        • 2. Deploying Smart Contract
        • 3. Interacting with ERC-20 token from Klaytn Wallet
      • ERC-721
        • 1. Writing ERC-721 Smart Contract
        • 2. Deploying Smart Contract
    • Testing Guide
    • Deployment Guide
    • Klaytn Compatible Tokens
    • Porting Ethereum Contract
  • Installation & Operation
    • Endpoint Node
      • System Requirements
      • Installation Guide
        • Download
        • Installation Guide
        • Configuration
        • Startup the EN
        • Testing the Installation
      • Operation Guide
        • Starting/Stopping EN
        • Configuration
        • Errors & Troubleshooting
      • ken CLI commands
      • JSON-RPC APIs
    • Core Cell
      • System Requirements
      • Network Configuration
      • Installation Guide
        • Download
        • Before You Install
        • Consensus Node Setup
          • Installation Guide
          • Configuration
          • Startup the CN
        • Proxy Node Setup
          • Installation Guide
          • Configuration
          • Startup the PN
        • Testing the Core Cell
      • Operation Guide
        • Starting/Stopping Core Cell
        • Configuration
        • Errors & Troubleshooting
      • Monitoring Setup
      • H/A Setup
    • Service Chain
      • Getting Started
        • Setting up a 4-node Service Chain
        • Connecting to Baobab
        • Cross-Chain Value Transfer
      • Reference Manuals
        • System Requirements
        • Download
        • SCN User Guide
          • Installation
          • Configuration
          • Starting/Stopping SCN
          • Checking Node Status
          • kscn commands
          • homi commands
        • SPN/SEN User Guide
          • Installation
          • Configuration
          • Starting/Stopping Node
          • Checking Node Status
        • Bridge Configuration
        • Anchoring
        • KAS Anchoring
        • Value Transfer
        • Configuration Files
        • Log Files
        • Genesis JSON
      • How-To Guides
    • Errors & Troubleshooting
    • Download
      • v1.7.0
      • v1.6.4
      • v1.6.3
      • v1.6.2
      • v1.6.1
      • v1.6.0
      • v1.5.3
      • v1.5.2
      • v1.5.1
      • v1.5.0
      • v1.4.2
      • v1.4.1
      • v1.4.0
      • v1.3.0
      • v1.2.0
      • v1.1.1
      • v1.0.0
      • v0.9.6
      • v0.8.2
  • BApp Developers
    • JSON-RPC APIs
      • API references
        • klay
          • Account
          • Block
          • Transaction
            • Working with Klaytn Transaction Types
          • Configuration
          • Filter
          • Miscellaneous
        • net
        • debug
          • Logging
          • Profiling
          • Runtime Tracing
          • Runtime Debugging
          • VM Tracing
          • VM Standard Tracing
          • Blockchain Inspection
        • admin
        • personal
        • txpool
        • governance
      • Service Chain API references
        • mainbridge
        • subbridge
      • Transaction Error Codes
    • Klaytn SDKs
      • caver-js
        • Getting Started
        • API references
          • caver.account
          • caver.wallet
            • caver.wallet.keyring
          • caver.transaction
            • Basic
            • Fee Delegation
            • Partial Fee Delegation
          • caver.rpc
            • caver.rpc.klay
            • caver.rpc.net
            • caver.rpc.governance
          • caver.contract
          • caver.abi
          • caver.kct
            • caver.kct.kip7
            • caver.kct.kip17
            • caver.kct.kip37
          • caver.validator
          • caver.utils
          • caver.ipfs
        • caver-js ~v1.4.1
          • Getting Started (~v1.4.1)
          • API references
            • caver.klay
              • Account
              • Block
              • Transaction
                • Legacy
                • Value Transfer
                • Value Transfer Memo
                • Account Update
                • Smart Contract Deploy
                • Smart Contract Execution
                • Cancel
              • Configuration
              • Filter
              • Miscellaneous
            • caver.klay.net
            • caver.klay.accounts
            • caver.klay.Contract
            • caver.klay.KIP7
            • caver.klay.KIP17
            • caver.klay.abi
            • caver.utils (~v1.4.1)
          • Porting from web3.js
      • caver-java
        • Getting Started
        • API references
        • caver-java ~v1.4.0
          • Getting Started (~v1.4.0)
          • Porting from web3j
    • Tutorials
      • Fee Delegation Example
      • BApp on Baobab (Video Lecture)
        • 1. Introduction
        • 2. Weakness of Blockchain Platform
        • 3. Understanding Klaytn
        • 4. Developing an Addition Game with Klaytn Tools
        • 5. Front-end for Klaytn Addition Game Development
        • 6. Summary
      • Count BApp
        • 1. Environment Setup
        • 2. Clone Count BApp
        • 3. Directory Structure
        • 4. Write Smart Contract
        • 5. Frontend Code Overview
          • 5-1. Blocknumber Component
          • 5-2. Auth Component
          • 5-3. Count Component
        • 6. Deploy Contract
        • 7. Run App
      • Klaystagram
        • 1. Environment Setup
        • 2. Clone Klaystagram BApp
        • 3. Directory Structure
        • 4. Write Klaystagram Smart Contract
        • 5. Deploy Contract
        • 6. Frontend Code Overview
        • 7. FeedPage
          • 7-1. Connect Contract to Frontend
          • 7-2. UploadPhoto Component
          • 7-3. Feed Component
          • 7-4. TransferOwnership Component
        • 8. Run App
      • Migrating Ethereum App to Klaytn
      • Connecting MetaMask
      • Connecting Remix
    • Developer Tools
      • Kaikas
      • Klaytn Wallet
      • Klaytnscope
  • ---
    • Vision
      • Klaytn BApp (Blockchain App)
      • Value Proposition
      • Open Source
    • FAQ
    • Glossary
    • Terms of Use
    • Languages
Powered by GitBook
On this page
  • Klaytn is aiming at Mass-adoption of Blockchain
  • High Performance
  • Low Cost
  • Usability in User Account Management
  • Usability in Transaction
  • Rapid Development
  • Service-specific Private Chains with Data Anchoring
  • Contribution Reward
  • Transparency, Security and Decentralization
  • Governance by Trusted Entities

Was this helpful?

  1. Klaytn Overview

Why Klaytn

This document explains the key design principles of Klaytn and illustrates how Klaytn differentiates itself from others.

PreviousKlaytn OverviewNextKlaytn Design

Last updated 3 years ago

Was this helpful?

Ever since the first bitcoin transaction in 2009, numerous blockchain applications have been developed, but few of them gain meaningful traction in the market. The major roadblocks to blockchain adoption are;

  • Difficulty of use: Blockchain applications force end-users to understand cryptographic terms and the inner workings of the system. There are too many steps in making transactions, and hex-strings pop up all over.

  • Poor user experience: The burden of technical immaturity is simply passed to the users. In many blockchain systems, a transaction is not confirmed until significant time passes. Use of application often requires password inputs repeatedly (while there are no password recoveries), and charges a fee for each interaction (where the amount of fee can be highly fluctuating each time).

  • Uncertain sustainability: Lack of long-term sustainable business models for public blockchains slows down enterprise adoption. The operation heavily relies on the token economy that incentivizes the stakeholders to act in a sustainable manner, but the model is not proven in commercial areas yet.

Klaytn is aiming at Mass-adoption of Blockchain

The goal of Klaytn is blockchain mass adoption. The foremost design principle is;

Giving the same user experience that matches the expectation set on the web/mobile applications, eventually making the technology invisible to the users.

As per this principle, Klaytn has been designed to meet the following requirements.

High Performance

  • Main chain should handle at least 4,000 TPS.

  • Main chain should guarantee immediate transaction finality with one-second block generation time.

  • See .

Low Cost

  • End-users should not be burdened with any higher transaction fee that is beyond the cost that the traditional systems require.

  • Transaction fee should be stable and be determined by the transaction complexity itself, not by surrounding factors.

  • See and . At the time of writing, sending KLAY requires a fixed fee of 0.000625 KLAY.

Usability in User Account Management

  • User should be able to choose own account address in a human-readable format.

  • User can change the private key of an account without changing the address.

Usability in Transaction

  • Ability to delegate the user's transaction fee to the application operator.

Removing usability hurdles in the platform layer is not enough to drive the mass-adoption. To find attractive blockchain applications, fostering global developer communities along the strategic partnership with business owners is a crucial step.

Making a business-friendly environment to encourage the birth of compelling applications.

This entails the following requirements to support application development.

Rapid Development

  • The development of application on Klaytn must be straightforward, and the technologies used must follow the open standard to reduce the learning curve.

Service-specific Private Chains with Data Anchoring

  • Klaytn should provide a dedicated solution for private blockchain. The private chain can have its own governance and connect to the Klaytn main chain for data anchoring and asset transfer.

Contribution Reward

  • Applications that contribute to growing Klaytn ecosystem should be fairly rewarded.

Lastly, the grounding rules,

Klaytn does not sacrifice blockchain’s core characteristics to achieve the above-mentioned enhancement, and the platform stays stable with strongly committed stakeholders.

Transparency, Security and Decentralization

  • Everyone can request transactions and retrieve and validate every transaction execution result on the blockchain.

  • Klaytn is a decentralized network and no single malicious node breaks the data integrity.

Governance by Trusted Entities

  • At its initial phase, trusted entities, global listed enterprises that manage the business of hundreds of thousands to billions of dollars, operate Klaytn node and participate in decision making for the development of Klaytn.

See and .

See . Application operator can decide the amount of subsidy for each transaction and can implement more flexible business models such as freemium or subscription. Fee delegation can effectively lower the user acquisition barrier.

See , , and . As Klaytn Virtual Machine (KLVM) supports Ethereum’s Solidity contract, it becomes much easier to port PoC product on Ethereum to Klaytn for commercial use. It is much easier as well to find development tools and to get some help from the well-established developer community.

See . Enterprises often want to have their own dedicated execution environment to meet the SLA. With the service chain, an enterprise can maintain an isolated high-performing execution environment that is not affected by other blockchain applications, and also keep their business-sensitive data private.

See .

Solidity-Smart Contract Language
Truffle
Migrating Ethereum App to Klaytn
Incentive Program
Consensus Mechanism
Transaction Fees
Service Chain
Fee Delegation
Affordable Smart Contract Execution Cost
Human-Readable Address
Decoupling of Key Pairs from Addresses