泉链对比 FISCO BCOS —— 技术评估

This document compares Triquan Chain (泉链) — a gasless, permissioned Hyperledger Besu chain with national-cryptography (SM2/3/4) support — with FISCO BCOS, China's leading domestic consortium blockchain, framing Triquan as a compliance-first modernization of enterprise blockchain.

Key takeaway: FISCO BCOS represents enterprise blockchain "1.0" — a monolithic system on a deprecated Oracle JDK 1.8 toolchain (end-of-life since 2019). Triquan runs the modern Ethereum stack (Besu 26.6.1 on JDK 25, Prague EVM) with a gasless UX and national cryptography — better suited to regulated, user-facing applications while fully meeting Chinese regulatory requirements.

01 Platform Overview

02 Detailed Technical Comparison

2.1 Architecture & Design

2.2 Consensus

2.3 Smart Contracts & Development

2.4 Cryptography & Compliance

2.5 Java / JDK Dependency

2.6 Deployment & OS

2.7 Gas Model & UX

2.8 Efficiency — On-Demand Blocks

Unlike most chains that mint a block every few seconds regardless of activity, Triquan produces blocks on demand — fast under load, quiet when idle — suppressing empty blocks and cutting idle-period data by roughly 95%, on commodity hardware.

03 Summary Comparison

04 Regulatory Positioning

"A modern, EVM-compatible trusted-record platform with a gasless UX and national cryptography — the compliance-friendly evolution of enterprise blockchain, avoiding the legacy JDK and OS constraints of older consortium chains, operated by Zhejiang Weihan Technology Co., Ltd."

05 Conclusion

Do not position Triquan as a "competitor" to FISCO BCOS — position it as the next generation, solving the UX, developer-experience and legacy-technology problems its 2017-era architecture cannot. For regulated-record use cases, Triquan's gasless model and modern stack make it a superior choice, fully compliant with Chinese regulations.

泉链（Triquan Chain）是一条由浙江玮瀚科技有限公司运营的完全许可制、零手续费企业级区块链，面向受监管记录——溯源、存证、交易报送、数字身份与资产数字化，运营方保有完全管控权并可为主管机关提供监督节点。

01 网络参数

02 技术架构

2.1 执行与运行时

执行客户端 Hyperledger Besu 26.6.1（Apache 2.0，Linux 基金会去中心化信任），与摩根大通 Onyx、ConsenSys Quorum 同属一系。运行时 OpenJDK 25，当前版本、持续安全打补丁。虚拟机为标准以太坊 EVM（Prague 代），完整兼容全球以太坊工具链。

2.2 共识与最终性

算法为 QBFT（IBFT 2.0 的现代后继者），可容忍至多 ⌊(n−1)/3⌋ 个故障/恶意验证节点，具备安全性与即时最终性。验证节点经链上投票增删（无需重启、不分叉）。当前为单一运营方验证节点，可扩展为多验证节点联盟。

2.3 准入控制（许可制）

泉链在节点层实施双层许可（基于配置、运营方管控）：账户白名单——仅经批准账户可发起交易，其余在交易池与出块环节被拒绝；节点白名单——仅经批准节点（enode）可互联。由此形成封闭、准入受控的网络：无匿名参与、无开放写入；公开 RPC 仅暴露只读方法，写入端口对公网防火墙隔离。

2.4 密码学

2.5 存储与数据治理

存储引擎 RocksDB，采用默克尔帕特里夏树世界状态。数据本地化——全部节点与数据托管于运营方管控、位于其属地的基础设施。查询经区块浏览器链下索引（与账本解耦）。账本仅追加、具密码学链接，记录不可事后更改。

03 高效——按需出块

泉链按需出块：有负载时加速、空闲时安静。空闲期抑制空块并将网络产生的数据削减约 95%，在普通商用硬件上稳定运行——同时降低成本与存储占用。

04 监管监督

• 监督节点——运营方可为主管机关配置专门的只读 / 监管节点，在不授予写入权限的前提下，对全部链上记录提供实时、防篡改的可见性。
• 可审计性——每笔交易与记录均被永久且可验证地记录；任何记录均可通过重算其密码学哈希并与链上取值比对而独立验证。
• 运营方问责——浙江玮瀚科技有限公司为网络、参与方及内容管理义务的唯一责任主体。

05 公开端点与安全

所有公开端点启用 TLS；写入/共识/管理端口对公网防火墙隔离；账户与节点双层许可；确定性最终性（无回滚风险）；无代币经济（消除投机与金融工具风险）。

06 合规定位

07 预期应用场景

• 溯源——防篡改账本上的端到端来源与供应链追踪。
• 存证——对文件、合同与事件的防篡改时间戳固化，具证据效力。
• 交易报送——可审计、面向监管的交易与披露记录，多方共享单一可信源。
• 数字身份——面向企业与跨境的、用户自主掌控的国密化身份与凭证。
• 资产数字化——在合规许可账本上登记与结算受监管资产。

Triquan Chain (泉链) is a fully permissioned, gasless, enterprise-grade blockchain operated by Zhejiang Weihan Technology Co., Ltd., built for regulated records — traceability, notarization, transaction reporting, digital identity and asset digitization — where the operator retains full control and can provide a supervisory node to the competent authorities.

01 Network Parameters

02 Technical Architecture

2.1 Execution & Runtime

Execution client Hyperledger Besu 26.6.1 (Apache 2.0, Linux Foundation Decentralized Trust) — the same client family as JPMorgan Onyx and ConsenSys Quorum. Runtime OpenJDK 25, current and actively security-patched. Virtual machine is the standard Ethereum EVM (Prague), fully compatible with the global Ethereum toolchain.

2.2 Consensus & Finality

Algorithm QBFT (the modern successor to IBFT 2.0), tolerating up to ⌊(n−1)/3⌋ faulty validators with safety and immediate finality. Validators are added/removed by on-chain vote (no restart, no fork). Currently a single operator validator, expandable to a multi-validator consortium.

2.3 Access Control (Permissioning)

Triquan enforces two layers of operator-controlled permissioning: an account allowlist — only approved accounts may transact, all others rejected at the pool and at block construction; and a node allowlist — only approved node identities (enodes) may peer. This makes it a closed, admission-controlled network: no anonymous participation, no open write access. The public RPC exposes read-only methods only; write ports are firewalled off the public internet.

2.4 Cryptography

2.5 Storage & Data Governance

Storage engine RocksDB with a Merkle Patricia Trie world state. Data localization — all nodes and data hosted on operator-controlled infrastructure within the operator's jurisdiction. Querying via off-chain indexing (block explorer), decoupled from the ledger. Append-only, cryptographically linked ledger; records cannot be altered retroactively.

03 Efficiency — On-Demand Blocks

Triquan produces blocks on demand — fast under load, quiet when idle. During idle periods it suppresses empty blocks and reduces network-generated data by roughly 95%, running comfortably on commodity hardware and lowering both cost and storage footprint.

04 Regulatory Supervision

• Supervisory node — a dedicated read-only / monitoring node can be provisioned for the competent authorities, giving real-time, tamper-evident visibility into all on-chain records without write access.
• Auditability — every transaction and record is permanently and verifiably logged; any record can be independently verified by recomputing its cryptographic hash against the on-chain value.
• Operator accountability — Zhejiang Weihan Technology Co., Ltd. is the single accountable entity for the network, its participants and content-moderation obligations.

05 Endpoints & Security

TLS on all public endpoints; write/consensus/admin ports firewalled from the public internet; account- and node-level permissioning; deterministic finality (no reorg risk); no token economy (removes speculation and financial-instrument risk).

06 Compliance Positioning

07 Intended Use Cases

• Traceability — end-to-end provenance and supply-chain tracking on a tamper-evident ledger.
• Notarization / attestation — tamper-proof timestamping of documents, contracts and events with evidentiary weight.
• Transaction reporting — auditable, regulator-facing records with a single shared source of truth.
• Digital identity — self-controlled, nationally-cryptographic identity and credentials for enterprise and cross-border scenarios.
• Asset digitization — registration and settlement of regulated assets on a compliant, permissioned ledger.