Blockchain Service overview
- Print
- PDF
Blockchain Service overview
- Print
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
Available in VPC
NAVER Cloud Platform's Blockchain Service is a Blockchain as a Service (BaaS) that can configure private and consortium-type blockchain networks using Hyperledger Fabric.
It simplifies complex processes, including preparing infrastructure, installing blockchain frameworks, deploying nodes, and configuring networks to configure a blockchain network, providing operational convenience.
Note
Hyperledger is an open-source project to develop blockchain and related tools led by the Linux Foundation in 2015. Its goal is to develop a blockchain and distributed ledger to provide systems with performance and reliability where global business transactions can be made. Among them, Hyperledger Fabric is a blockchain framework contributed by IBM and Digital Asset. It is a module architecture platform providing nodes that consist of blockchains, smart contract running, agreement between members, and membership service.
Please refer to the following page for more information.
- Hyperledger: https://www.hyperledger.org
- Hyperledger Fabric: https://www.hyperledger.org/use/fabric
- Blockchain network: https://hyperledger-fabric.readthedocs.io/en/release-1.4/network/network.html
A variety of features Blockchain Service offers
Validated blockchain framework
- Users can create a blockchain network based on Hyperledger Fabric, an open-source blockchain framework that is optimized for and widely used in corporate deployments.
- Hyperledger Fabric provides enterprise-level platform features, enabling users to securely configure consortium-type blockchains in which multiple members participate.
- Blockchain Service supports Hyperledger Fabric v2.2.3.
Easy blockchain configuration and expansion
- Configuring a blockchain network does not require complex infrastructures or coding.
- Users can simply and easily configure a blockchain network with just a few clicks on the web-based console, and they can scale quickly if members increase and the network grows.
Reasonable cost
- From Proof of Concept (PoC) to an operating environment, users can configure a blockchain of the desired size at reasonable costs.
- Users can manage resources flexibly according to the number of members and their usage. Since they only pay for how much they use, they can manage their network in a more cost effective manner.
Web-based node configuration and management
- Users can quickly create various components for configuring a blockchain network using Hyperledger Fabric, such as infrastructure, nodes, certificates, and MSP, with a few clicks and without coding.
- They can easily and conveniently perform a wide range of tasks, from creating a blockchain network to modifying and deleting resources. They can also check the blockchain network, organization, and nodes they created, all from the intuitively designed and web-based console.
Full standard SDK support
- It provides information for accessing individual nodes, which is required for developing blockchain apps, and fully supports Hyperledger Fabric's native SDK.
- Users can deploy chaincodes and create ledgers through applications using Fabric SDK.
Strong security
- Through the Sub Account service that enables configuring user-specific permissions in detail, multiple personnel including blockchain network administrators and smart contract developers can work safely within the scope of the permissions granted to them.
- Support for Hardware Secure Module (HSM) and Private CA enables stronger Hyperledger Fabric authentication and security (This will be linked with HSM and Private CA.)
Blockchain Service guide information
- Blockchain Service overview: Introduction to Blockchain Service, advantages, helpful guides for Blockchain Service users, related resources, FAQs
- Blockchain Service scenario: Guide to overall Blockchain Service usage scenarios
- Prerequisites for using Blockchain Service: Guide to supported specifications in order to use Blockchain Service
- Getting started with Blockchain Service: Guide to how to create Blockchain Service on the NAVER Cloud Platform's console
- Using Blockchain Service: Guide to how to use Blockchain Service
- Dashboard: Usage status of Blockchain Service
- Networks: Guide to how to use networks
- Organizations: Guide to how to use organizations (MSP)
- Nodes: Guide to how to use nodes (Orderer, Peer, CA)
- Smart Contracts: Guide to how to use smart contracts (channel, chaincode) and develop applications
- Managing Blockchain Service permissions: Guide to how to manage permissions for Blockchain Service and policies
- Blockchain Service release notes: Update history of Blockchain Service guides
Blockchain Service related resources
NAVER Cloud Platform provides a variety of related resources as well as guides to help customers better understand Blockchain Service. If you're a developer or marketer in need of detailed information while you're considering adopting Blockchain Service for your company or establishing data related policies, then please make good use of the resources below.
- Sub Account Guide: Sub Account manual that can be used when you need the admin accounts with various permission levels to manage Blockchain Service
- Ncloud use environment guide: A manual on VPC environments and support options
- Portal and console guide: Questions answered on how to request subscription and manage Blockchain Service, and how to use the portal and console at a basic level
- Pricing introduction, characteristics, detailed features
- Latest service news: Latest news related to Blockchain Service
- FAQ : Frequently asked questions by Blockchain Service users
- Contact us : Send direct inquiries in case of any unresolved questions that aren't answered by the guides
Please check FAQs first.
Q. What is a blockchain?
A. A block is a set of transactions. Each block is created by including previous transaction information and current transactions. A blockchain refers to a ledger that connects each of the blocks that are created. It is a kind of a database.
Q. What are the components of Hyperledger Fabric?
A. Components of Hyperledger Fabric are as follows.
- Certificate Authority (CA): Issues and manages certificates (MSP) for certificates of organizations and users and safe communication between nodes (TLS)
- Organization: An organization permitted to participate in the network. Defined by Membership Service Provider (MSP)
- Consortium: A set of organizations participating in the network. Transaction history is shared within the consortium
- Membership Service Provider (MSP): A management system for users' permissions and authorization. Roles and permissions of nodes within the network are defined
- Orderer: Manages the configuration information for channels within the network. Defines the order of transactions coming from the client, and makes the final block to send it to the connected nodes.
- Channel: A sub-network for processing transactions of a specific group (a set of MSPs) within the consortium
- Peer: A node participating in the network. Stores the ledger physically and runs the chaincode. Classified as endorsing peer, committing peer, anchor peer, or leader peer depending on the role
- Client: Creates transactions and checks transaction history
- Chaincode: Refers to the Hyperledger Fabric's smart contracts. Contains the ledger's storing format and transaction conditions
- Ledger: Stores all transactions that occur in the data of an unmodifiable state and chaincode
Note
For more information about Hyperledger Fabric terms, please refer to the following.
Q. What should I pay attention to when configuring a blockchain node?
A. Blockchain Service deploys and sets Hyperledger Fabric nodes to the Kubernetes cluster created by Ncloud Kubernetes Service. It defines the default resource size by node type as follows. If you lack resources for Kubernetes clusters and worker nodes when creating Hyperledger Fabric nodes, creating Hyperledger Fabric nodes is limited.
| Node type | vCPU(Core) | Memory(MiB) | Storage(GiB) |
|---|---|---|---|
| Orderer | 0.35 | 700 | 100 |
| Peer (LevelDB) | 1.1 | 2,800 | 200 |
| Peer (CouchDB) | 1.1 | 2,800 | 100 |
| CouchDB | 1.0 | 2,000 | 100 |
| CA | 0.1 | 200 | 20 |
Note
- If you create a blockchain network of 1 orderer, 2 peers (LevelDB), and 2 CAs, the Kubernetes cluster's worker node requires a volume of 2.75 vCPU cores, 6,700 MiB of memory, and 540 GiB of storage or more. If the Kubernetes cluster is made up of multiple worker nodes, then you should check the availability of worker nodes where Hyperledger Fabric nodes are deployed.
- For example, in the case of a CouchDB-type peer, the same worker node should be deployed to reduce the network communication load of the peer and CouchDB. In order to configure 2 containers, peer and CouchDB, a worker node requires 2.1 vCPU cores and 4800 MiB of memory. If the worker node's availability is not enough, you can't create a peer.
Was this article helpful?