This article compares consortium (alliance) chains with public chains, explains why consortium chains are favored in enterprise scenarios, and details Hyperledger Fabric's admission mechanism, including MSP identity, channel architecture, and member management, supported by diagrams and practical examples.
This article explains the key differences between consortium (permissioned) and public blockchains, details Hyperledger Fabric’s architecture—including MSP, channels, and ordering services—and describes how Fabric implements an admission mechanism to control network membership.
This article explains how to augment Hyperledger Fabric's orderer service by integrating Tendermint's ABCI to implement a PBFT consensus mechanism, detailing the limitations of solo and Kafka ordering, the motivation for decentralized ordering, and the step‑by‑step implementation approach.
The article presents Ctrip’s Blockchain Service Platform (CBaaS), detailing its motivation, architecture, and the advantages of using Hyperledger Fabric’s modular design—including contract execution, consensus, permission control, and multi‑chain capabilities—to simplify enterprise blockchain adoption and enable secure, data‑rich on‑chain applications.
The article analyzes the shortcomings of current seller‑driven financial risk data sharing, proposes a blockchain consortium architecture using Hyperledger Fabric, compares a 1.0 token‑based design with an improved 2.0 version that adds a service layer, secure multi‑party computation, and regulatory oversight to achieve fair pricing, data quality, security, and efficient transaction processing.
This article details the end‑to‑end evolution of 58BaaS, covering blockchain fundamentals, the three‑stage Hyperledger Fabric network deployment, Kubernetes‑based chaincode container management, a simplified client API with configuration files, performance and robustness enhancements, debugging tools, and a Prometheus‑Grafana monitoring solution.
The article describes the business scenario of financial risk data sharing, identifies pain points of current query‑based pricing models, and proposes two blockchain consortium designs—Version 1.0 and an improved Version 2.0—detailing token‑based pricing, smart‑contract accounting, service‑layer architecture, and deployment on Hyperledger Fabric.
The article analyses the shortcomings of traditional seller‑driven financial risk data queries and proposes a blockchain consortium that uses distributed ledger, consensus, smart contracts and token‑based pricing to enable fair, secure, and efficient data sharing and settlement among financial institutions.
This guide walks you through every step of learning Hyperledger Fabric—from setting up the environment and deploying single‑ and multi‑node networks to developing, installing, and testing chaincode with Java SDK—providing a hands‑on roadmap for blockchain developers.
Hyperledger Fabric, an open‑source blockchain framework from the Linux Foundation, provides immutable ledgers, consensus mechanisms, and identity management to address trust challenges in scenarios like inter‑bank settlement and supply‑chain finance, detailing its data structures, modules, transaction flow, and core services.
This article presents a side‑by‑side comparison of three major blockchain platforms—Bitcoin, Ethereum, and Hyperledger Fabric—detailing their required cryptocurrencies, network types, permission models, consensus algorithms, smart‑contract support, and primary programming languages, and typical use cases.
This article provides a comprehensive overview of Hyperledger Fabric’s architecture, detailing its three core components, key terminology, protobuf definitions for transactions, blocks and messages, chaincode development in Go, and proposed role‑based redesign for improved scalability.
This article presents a series of Hyperledger Fabric chaincode examples written in Go, covering information notarization, asset trading, digital currency issuance, diploma verification, community energy sharing, and logistics supply chain, each with functional descriptions, key functions, data models, and REST‑API interaction details.
