# yeasy/blockchain_guide: A Chinese-Language Blockchain Book You Read From Git, Not From a Publisher

> The repository is the source of an open book that moves from distributed-ledger theory to Bitcoin, Ethereum and Hyperledger Fabric, with a PDF release and a GitBook edition. It is a teaching text with build tooling attached, and the licence says so.

**yeasy/blockchain_guide** — Introduce technologies on blockchain and distributed ledger, from theory to practice with bitcoin, ethereum and hyperledger.

- Repository: https://github.com/yeasy/blockchain_guide
- Website: https://yeasy.gitbook.io/blockchain_guide/
- Stars: 7,077 · Forks: 1,941
- Language: Python
- License: not declared
- Published: 2026-09-22 · Updated: 2026-09-22 · Language: en
- Canonical page: https://hysenlabs.com/projects/yeasy-blockchain-guide

## What the Repository Actually Contains

This is a book, not a library. The top level of the repository is a sequence of numbered chapter directories running from 01_history through 15_frontiers, plus SUMMARY.md, which is the table of contents the GitBook build consumes. There is no package to import and no service to start. The Python files that give the repository its primary-language label are check_emphasis.py and check_project_rules.py, sitting next to a tools directory and a tests directory. Those are editorial checks on the manuscript, not runtime code for a blockchain.

The intended reader is stated plainly in the README: beginners who want the concepts in order, Ethereum developers who want smart contracts and DeFi, enterprise engineers who need to design and deploy a Hyperledger solution, and architects who need to reason about availability and throughput. That is four audiences in one text, and the README answers the obvious objection with a learning-path table that assigns different chapter sequences to each role. A beginner takes chapters 1 through 3 and then chapter 6 on Bitcoin. An architect starts with chapters 1 through 5 and then jumps to 13 through 15 on Fabric design and the frontier material.

The scope claim is narrower than the title suggests. The README describes the book as an objective account of where the concept came from and how the key mechanisms work, with Hyperledger used as the worked example because the author developed on it and designed enterprise solutions with it. Ethereum gets a chapter and a Web3/DeFi chapter. Bitcoin gets a chapter. Everything from 08_hyperledger onward is Fabric: deployment, operations, application development, architectural design, and a BaaS chapter. If your interest is a public chain other than Bitcoin or Ethereum, the directory listing does not show a home for it.

## The Chapter Order Is the Argument

Most blockchain introductions start with a coin. This one starts with distributed systems and cryptography. Directories 04_distributed_system and 05_crypto sit before 06_bitcoin, which means consistency, consensus and cryptographic primitives are treated as prerequisites rather than as asides inside a Bitcoin chapter. That ordering is the book's main editorial decision, and it is why the architect learning path in the README begins with chapters 1 through 5.

The second half is where the author's stated experience shows. Chapters 8 through 11 cover Fabric permissions, channels, endorsement and chaincode development; chapter 13 is Fabric architecture design; chapter 14 covers blockchain-as-a-service platforms; chapter 15 covers frontiers. A reader who finishes the architecture path has been walked from why a distributed ledger is hard, through how Bitcoin and Ethereum answer it, to how a permissioned network with named organizations and endorsement policies answers it differently.

The README also claims chapter 3 includes failure cases alongside the financial, traceability and government deployment scenarios. That is worth noting because scenario chapters in this genre usually list successes. A chapter that documents where a deployment model did not work is more useful to someone writing an internal proposal than a list of pilot announcements, and it is the kind of content that dates fastest.

## Reading It Locally with mdPress

The README gives two ways to read. The online edition is hosted at yeasy.gitbook.io/blockchain_guide. For a local build, the README points at a separate tool, mdPress, by the same author, and gives these commands:

```bash
brew tap yeasy/tap && brew install mdpress
mdpress serve
```

The first line adds the author's Homebrew tap and installs mdpress. The second starts a local server from the repository root so the chapters are rendered in a browser. The README does not document which port mdpress serves on, so read the mdPress project for that detail. Run the serve command from the directory that contains SUMMARY.md, since that file is what defines the chapter order.

If you only want a file to read offline, the README points to the Releases page for the latest PDF, and separately offers a preview build at releases/download/preview-pdf/blockchain_guide.pdf. The README is explicit that the preview file is overwritten as the main line moves and does not represent a formal release. That distinction matters if you are citing a page number in a document: cite a tagged release, not the preview.

## The Fabric Version Problem, Stated by the Book Itself

The strongest limitation is one the README raises against itself. The companion print book, Blockchain: Principles, Design and Applications, 2nd edition, was written around Hyperledger Fabric 2.x. The README then notes that as of 2026 the Fabric community maintains both a 2.5 LTS line and a 3.x line, and tells readers to confirm the current version against official documentation when they practise.

That is an honest warning, and it is also the practical risk. A repository whose last push is 2026-09-17 can keep prose current, but it cannot make a printed second edition describe a 3.x release line that arrived afterwards. Any chapter that walks through Fabric deployment, channel configuration or chaincode lifecycle may describe commands and configuration that differ from what you will run. Treat chapters 9 through 11 and 13 as conceptual guidance and verify every command against the Fabric release you actually installed.

The second limitation is language and licence together. The text is Chinese, and the licence is CC BY-NC-SA 4.0: share and adapt with attribution, non-commercial use only, and derivatives under the same terms. That rules out the common enterprise move of excerpting chapters into paid internal training material. A company that wants to reuse the Fabric architecture chapter in a commercial course needs a different arrangement, and the README points to the author for contact about translations rather than granting that permission outright. Nothing here is legal advice; read the licence text itself.

## Where a Documentation Site Beats It

The obvious alternative is the official Hyperledger Fabric documentation. The difference is not quality, it is purpose. Fabric's documentation is versioned with the software, so a page for a 2.5 LTS release describes that release, and it is written in English. This book gives you a single narrative thread that starts before any specific chain and explains why permissioned ledgers exist at all, which is the thing a versioned reference does not attempt.

A second alternative is a general English-language blockchain textbook. That trades the Fabric depth for broader coverage and a language most teams share. The trade is real: this repository's second half is unusually specific to one permissioned platform, including operations and BaaS chapters, and a general text will not walk you through endorsement policy design at that level of detail.

For a reader who wants to read before installing anything, the GitBook edition is the lower-friction path, and the PDF release is lower still. The local mdPress build only pays off if you intend to edit the manuscript or work offline for long stretches.

## Maintenance, Releases and What to Verify

The repository is not archived, and the last push was on 2026-09-17, five days before this writing, so the manuscript is being touched. The release list shows v2.4.0 on 2026-06-16, v2.3.1 on 2026-05-18, and a preview-pdf artifact dated 2026-03-29. The README does not document a deprecation policy, a support window for older releases, or a rollback procedure, so if you pin a release for citation purposes you are choosing that pin yourself.

Upgrade cost is low in the ordinary sense, because there is nothing to upgrade in a deployment. If you build the PDF or the GitBook output yourself, your cost is rerunning the build and rechecking any chapter you cite. If you maintain a translation or a derivative, the share-alike term means your derivative stays under CC BY-NC-SA 4.0, and the non-commercial term constrains what you can do with it regardless of how much you changed.

The two scripts worth knowing about are check_emphasis.py and check_project_rules.py, which sit at the repository root with a tools directory and a tests directory. Their names indicate manuscript linting, and the README does not describe what rules they enforce. A contributor should read those files before submitting a pull request rather than guessing at the house style.

## Conclusion

Adopt it if you read Chinese and want one ordered path from distributed-systems basics to Fabric channel and endorsement design, and if a non-commercial licence suits how you will use the text. Do not adopt it as an English-language reference, as a code library, or as your only source for Fabric versions, because the README itself tells readers to confirm the current release line against official documentation. Before relying on any chapter, open the release you intend to cite and check that its date matches the Fabric or Ethereum behaviour you plan to describe.

## FAQ

### Is yeasy/blockchain_guide still relevant in 2026?

The repository is not archived and the last push was on 2026-09-17, with v2.4.0 released on 2026-06-16. The README itself warns that the Fabric material was written around 2.x while the community now maintains 2.5 LTS and 3.x, so the concepts hold but version-specific commands need checking.

### Is blockchain easy to learn with yeasy/blockchain_guide?

The README positions the book for readers with some fintech background and says readers without a technical background can still follow the current state of the technology. It also splits the chapters into four learning paths, so a beginner starts with chapters 1 through 3 and then chapter 6 on Bitcoin rather than reading straight through.

### How can I get started with blockchain as a beginner using yeasy/blockchain_guide?

The README's five-minute path starts with chapters 1 and 2 for the origin and definition of blockchain, then chapter 3 for application scenarios, then chapters 4 and 5 for consistency, consensus and cryptography. The beginner learning path then goes to chapter 6 on Bitcoin.

## Sources

- [Issues](https://github.com/yeasy/blockchain_guide/issues)
- [Project website](https://yeasy.gitbook.io/blockchain_guide/)
- [README](https://github.com/yeasy/blockchain_guide/blob/master/README.md)
- [Releases](https://github.com/yeasy/blockchain_guide/releases)
- [yeasy/blockchain_guide on GitHub](https://github.com/yeasy/blockchain_guide)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/yeasy-blockchain-guide