Blockchain Technology Guide (Chinese Edition): Summary & Key Insights

Most digital systems still depend on trusted middlemen, and that dependence creates both efficiency and fragility. Blockchain’s radical promise is that trust does not always need to come from a central institution; it can emerge from code, cryptography, and shared rules. Li Qilei uses this idea to frame the entire subject: blockchain is not merely a database innovation, but a new way to coordinate economic and social activity when participants may not fully know or trust one another.

At its core, a blockchain is a distributed ledger maintained by multiple nodes. Transactions are grouped into blocks, validated through consensus mechanisms, and linked cryptographically so that past records become extremely difficult to alter. Instead of one administrator deciding what counts as true, a network of participants follows transparent protocols to agree on a shared version of history. This changes the architecture of trust from institutional authority to verifiable process.

The concept becomes especially powerful in situations where multiple organizations must collaborate but have conflicting incentives. Consider international trade: exporters, shipping companies, customs agencies, insurers, and banks all maintain separate records. A shared blockchain ledger can reduce disputes, speed reconciliation, and provide a common source of truth. Similar logic applies to food traceability, digital identity, and cross-border payments.

Li also emphasizes that blockchain does not eliminate trust entirely; it redistributes it. Users still trust the software design, governance model, and implementation quality. That is why successful adoption depends not only on technology, but on careful system design and stakeholder alignment.

Actionable takeaway: when evaluating a blockchain use case, ask a simple question first: where does trust currently break down, and can a shared, tamper-resistant ledger solve that better than a centralized system?

People often talk about decentralization as if it were automatically superior, but Li Qilei makes a more mature point: decentralization is a strategic design decision, not a religion. Blockchain matters because it offers alternatives to centralized control, yet not every problem requires maximum decentralization. The real challenge is to understand where decentralization adds resilience, transparency, and fairness—and where it may introduce complexity, cost, or slower performance.

In a centralized system, one entity controls the database, sets permissions, processes updates, and often captures most of the value. This can be efficient, but it also creates single points of failure. If the central authority is compromised, censored, corrupted, or simply unavailable, the whole system suffers. Decentralized architectures distribute control across many participants, reducing dependence on any one actor and making the network more resistant to manipulation.

However, decentralization comes in degrees. Public blockchains such as Bitcoin and Ethereum allow broad participation and high openness. Private or consortium blockchains restrict access to approved entities, making them more suitable for enterprise environments where compliance, privacy, and speed matter. A hospital network, for example, may want shared records across institutions without exposing data to the open internet. A public cryptocurrency network, by contrast, may prioritize openness and censorship resistance.

Li’s contribution is to push readers beyond slogans. He encourages them to compare governance needs, transaction volume, data sensitivity, and incentives before choosing an architecture. The goal is not to decentralize everything, but to decentralize what benefits from shared control.

Actionable takeaway: map your system’s pain points—single-point failure, weak transparency, audit friction, or overreliance on intermediaries—before deciding how much decentralization is actually useful.

A ledger is only as trustworthy as the process that updates it. That is why consensus sits at the heart of blockchain systems. Li Qilei explains consensus not as an abstract technical detail, but as the mechanism that allows decentralized networks to agree on valid transactions without needing a central bookkeeper. In other words, consensus is the engine that converts distributed participation into a shared, reliable record.

Different blockchains use different methods to achieve this agreement. Proof of Work, used famously by Bitcoin, requires participants to expend computational effort to validate new blocks, making attacks costly but also consuming significant energy. Proof of Stake uses economic commitment instead of raw computation, selecting validators based on staked assets and generally improving efficiency. Consortium or enterprise chains may rely on lighter mechanisms among preapproved participants, since identity and permissions are already known.

The book highlights a crucial trade-off: stronger decentralization often comes with lower throughput, while higher speed may require more controlled participation. For example, a public blockchain designed for global monetary transfers may prioritize security and immutability over transaction speed. A supply-chain blockchain among known firms may choose faster consensus because trust is partially anchored in business relationships and legal agreements.

Li encourages readers to see consensus as a business issue as much as a technical one. It determines cost, scalability, security assumptions, and governance behavior. Choosing the wrong consensus model can make a project unusable or vulnerable.

Actionable takeaway: whenever you assess a blockchain platform, do not ask only what it can do—ask how it reaches agreement, who validates transactions, what incentives they have, and what trade-offs that model creates.

When records can be quietly edited, accountability becomes negotiable. Blockchain introduces a different standard: once validated and added to the chain, data becomes extremely difficult to change without leaving evidence. Li Qilei presents immutability as one of blockchain’s most transformative features because it changes how organizations think about auditing, compliance, and operational integrity.

This does not mean blockchains store truth automatically. False information entered at the source can still remain false forever. What immutability provides is an auditable history of what was recorded, when it was recorded, and by whom under defined system rules. That is a major improvement over fragmented databases where unauthorized edits may be hard to detect.

The practical applications are broad. In supply chains, immutable records can help trace contaminated food back to a specific farm or shipment. In finance, transaction histories become easier to audit and reconcile across institutions. In public administration, document notarization and land records may become more transparent and harder to tamper with. In healthcare, immutable logs can strengthen data governance by showing exactly when records were accessed or modified, even if sensitive content itself is kept off-chain.

Li also notes that immutability requires disciplined data architecture. Because on-chain data is hard to remove, organizations must think carefully about privacy, legal compliance, and what should be stored directly versus referenced through hashes. The feature is powerful, but careless implementation can create long-term risk.

Actionable takeaway: treat blockchain immutability as a tool for auditability, not as a dumping ground for raw data—store only what truly benefits from permanent, verifiable history.

The real leap in blockchain comes when ledgers stop being passive records and start executing rules. Li Qilei explains smart contracts as self-executing programs that run on blockchain networks when predefined conditions are met. They allow agreements to move from paper-based promises and manual enforcement into automated digital logic.

A smart contract does not replace all legal contracts, but it can encode specific operational terms. For example, an insurance payout could be triggered automatically when trusted weather data shows rainfall below a certain threshold. A supplier could receive payment the moment goods are verified at delivery. Loyalty points, digital assets, royalty splits, and escrow arrangements can all be managed through transparent code rather than back-office processing.

The appeal is clear: fewer intermediaries, lower administrative cost, faster execution, and less room for disputes over agreed rules. In industries burdened by reconciliation delays and manual approvals, smart contracts can significantly improve efficiency. Decentralized finance is a high-profile example, where borrowing, lending, trading, and collateral management are executed through smart contracts rather than traditional financial institutions.

Yet Li is careful not to romanticize the concept. Bad code can create serious risks, and rigid automation may fail in messy real-world situations. Smart contracts depend on reliable input data, secure development practices, and governance mechanisms for handling exceptions. The phrase “code is law” is not enough when legal, commercial, and human realities remain complex.

Actionable takeaway: use smart contracts first for narrow, high-frequency processes with clear rules and measurable triggers, then expand only after testing security, edge cases, and operational governance.

If blockchain is reduced to coin prices, its deeper significance disappears. Li Qilei works hard to separate the underlying technology from the speculative cycles that often dominate public conversation. Cryptocurrencies may be the most visible blockchain application, but they are only one branch of a much larger ecosystem involving digital identity, asset tokenization, logistics, intellectual property, and trusted data sharing.

The book likely helps readers understand that blockchain’s central value lies in enabling secure, verifiable coordination across organizational boundaries. In supply chains, it can improve provenance and anti-counterfeiting measures. In energy markets, peer-to-peer trading systems can record generation and consumption transparently. In education, credentials can be issued and verified digitally. In real estate, tokenization may make ownership transfer more efficient and potentially broaden access to investment. In government services, tamper-resistant records can improve transparency and reduce administrative friction.

What ties these examples together is not hype but a recurring problem: multiple parties need a common record, but existing systems are siloed, inefficient, or overly dependent on intermediaries. Blockchain can help when shared trust is expensive to maintain.

Li’s perspective is especially useful for business readers tempted either to dismiss blockchain entirely or to adopt it indiscriminately. The technology is neither magic nor meaningless. Its value depends on context, process design, and ecosystem readiness.

Actionable takeaway: look past market noise and identify one concrete workflow in your industry where verification, reconciliation, or provenance is slow, expensive, or disputed—that is where blockchain may have real strategic value.

Technology projects often fail not because the software is weak, but because the institutions around it are poorly designed. Li Qilei stresses that blockchain adoption in business settings is as much a governance challenge as a technical one. When multiple organizations share infrastructure, the critical questions are no longer only about code, but about authority, incentives, standards, accountability, and decision-making.

In a consortium blockchain, for example, members must agree on who can join the network, who can validate transactions, how software upgrades are approved, how disputes are resolved, and what happens if a participant behaves dishonestly or leaves the system. Without clear governance, even a technically sophisticated platform can stall due to mistrust, politics, or conflicting interests.

This becomes especially important in sectors such as trade finance, logistics, healthcare, and public administration, where participants have unequal power, different compliance obligations, and varied digital maturity. A blockchain may promise shared trust, but organizations still need legal frameworks, data standards, operating procedures, and incentive alignment. If one company captures too much influence, others may be reluctant to participate. If benefits are distributed unevenly, the network may not scale.

Li’s guidance helps readers avoid a common mistake: assuming that blockchain automatically creates collaboration. In reality, it exposes the need for stronger collaboration design. Successful enterprise blockchain initiatives typically begin with a narrow use case, committed stakeholders, interoperable standards, and a governance model that fits the business context.

Actionable takeaway: before launching any blockchain initiative, define governance in writing—membership, validation rights, upgrade processes, data ownership, dispute resolution, and incentive structure—before you write significant code.

Every powerful technology comes with constraints, and blockchain is no exception. Li Qilei addresses the practical limitations that separate serious understanding from promotional enthusiasm. Blockchain systems must balance decentralization, security, and scalability, and improvements in one area often create pressure in another. This is one of the most important realities for anyone considering implementation.

Public blockchains can offer high resilience and openness, but they may process transactions more slowly than centralized databases. Storing large amounts of data directly on-chain can become expensive and inefficient. Complex smart contracts increase functionality but also expand the attack surface. Privacy is another challenge: transparent ledgers can conflict with commercial confidentiality or personal data protections if not designed carefully.

These trade-offs matter in real-world deployment. A consumer payments network needs speed and low fees. A land registry may prioritize permanence and tamper resistance. A medical data system requires strict privacy controls, making hybrid architectures more appropriate, with sensitive information stored off-chain and blockchain used only for access logs or verification hashes. Layer-2 systems, sidechains, permissioned networks, and off-chain computation can help address some constraints, but each introduces additional design complexity.

Li’s practical strength is that he does not treat these limits as reasons to reject blockchain. Instead, he frames them as engineering realities that force sharper problem definition. The right question is not whether blockchain is perfect, but whether its trade-offs are acceptable for a specific use case.

Actionable takeaway: define success metrics early—speed, cost, privacy, transparency, security, and interoperability—then evaluate whether blockchain meets those priorities better than conventional alternatives.

No technology transforms society in isolation. Li Qilei positions blockchain as part of a broader digital shift that includes cloud computing, the Internet of Things, artificial intelligence, and advanced cybersecurity. Blockchain becomes more powerful when combined with these systems, because its real role is often to anchor trust in data flows generated elsewhere.

Consider logistics. IoT sensors can monitor temperature, location, and handling conditions for goods in transit. Blockchain can then record key events in a tamper-resistant ledger, allowing manufacturers, distributors, regulators, and retailers to verify product history. In finance, AI can detect suspicious behavior while blockchain provides transparent transaction trails. In digital identity, biometric verification may authenticate users while blockchain manages credentials and permissioned sharing. In carbon accounting, sensor data and enterprise reports can be linked to a blockchain-based audit trail to improve confidence in emissions claims.

The book suggests that blockchain’s future will depend less on standalone enthusiasm and more on ecosystem integration, standards, and practical interoperability. Systems must communicate across platforms, sectors, and jurisdictions. Regulators, developers, and enterprises all shape the pace of adoption. The technology succeeds when it fits into broader workflows instead of demanding that the entire world rebuild itself around a single protocol.

This systems perspective is valuable because it tempers both hype and cynicism. Blockchain is neither a universal cure nor a passing fad. It is a trust layer that gains importance when integrated thoughtfully into digital infrastructure.

Actionable takeaway: do not evaluate blockchain as a siloed product—assess how it could work with your existing data systems, sensors, analytics tools, and compliance processes to create end-to-end trust.