技术评估与规格说明 · 供主管机关审阅
Technical Assessment & Specification · For Regulatory Review
泉链对比 FISCO BCOS —— 技术评估
- 运营方
- Operator
- 浙江玮瀚科技有限公司 · Zhejiang Weihan Technology Co., Ltd.
- 链 ID
- Chain ID
- 2869
- 技术栈
- Stack
- Hyperledger Besu 26.6.1 · OpenJDK 25 · Prague EVM · QBFT
- 日期
- Date
- 2026-07 · Final
本文对 泉链(Triquan Chain)——一条基于 Hyperledger Besu、零手续费、许可制、并支持国密(SM2/SM3/SM4)的企业级区块链——与中国领先的自主联盟链平台 FISCO BCOS 进行技术对比,将泉链定位为企业级区块链面向合规的现代化演进。
核心结论:FISCO BCOS 代表企业区块链"1.0"——构建于已停止维护的 Oracle JDK 1.8(2019 年即终止支持)之上的单体式许可系统。泉链则运行现代以太坊技术栈(Besu 26.6.1 + JDK 25,Prague 代 EVM),具备零手续费体验与国密支持,更适合承载受监管、面向终端用户的应用,同时全面满足中国监管要求。
01 平台概览
| 属性 | FISCO BCOS | 泉链 Triquan |
| 发布年份 | 2017 | 2026(已上线出块) |
| 发起 / 运营 | 金链盟(微众银行、腾讯、华为、深交所) | 浙江玮瀚科技有限公司 |
| 引擎 / 运行时 | C++ / Java(Oracle JDK 1.8) | Hyperledger Besu 26.6.1 / OpenJDK 25 |
| 架构 | 单体式许可联盟链 | 兼容 EVM、许可制、零手续费 |
| 生态 | 5,000+ 机构、100,000+ 成员 | 继承全球以太坊生态 |
02 详细技术对比
2.1 架构与设计理念
| 维度 | FISCO BCOS | 泉链 |
| 虚拟机 | 定制 EVM 实现 | 标准以太坊 EVM(Prague 代) |
| 工具链 | 专有工具,需再培训 | Solidity / Hardhat / Foundry / Remix / ethers.js |
| 升级路径 | 依赖平台自身发布 | 跟随以太坊路线图(EIP) |
| 互操作 | 有限(WeCross) | 原生以太坊互操作 |
FISCO BCOS 采用定制 EVM,与标准以太坊工具链并不完全兼容;泉链采用标准 Besu,直接继承整个以太坊开发者生态——数百万开发者早已熟悉 Solidity 与相关工具,无需再培训。
2.2 共识机制
| 维度 | FISCO BCOS | 泉链 |
| 算法 | PBFT、Raft(2017 年代) | QBFT(IBFT 2.0 后继者) |
| 最终性 | 即时最终性 | 即时最终性 |
| 验证节点治理 | 视图切换 | 链上投票增删(无需重启) |
两者均具备即时最终性的 BFT 共识。Besu 的 QBFT 应用广泛、文档完善,并支持在线验证节点治理:联盟伙伴可经投票加入为验证节点,无需重启网络。
2.3 智能合约与开发
| 维度 | FISCO BCOS | 泉链 |
| 合约语言 | Solidity、C++、WBC-Liquid | Solidity、Vyper |
| EVM 兼容性 | 部分(含定制扩展) | 完整(标准以太坊) |
| 开发工具 | 专有 Java SDK、Console | Hardhat、Foundry、Remix |
关键差异。FISCO BCOS 要求掌握绑定 Oracle JDK 1.8 的 Java SDK 与专有部署流程;泉链兼容 EVM,任何以太坊开发者均可即刻开发,无需再培训。
2.4 密码学与合规
| 能力 | FISCO BCOS | 泉链 |
| 国密 SM2/3/4 | 支持 | 原生支持(封装) |
| ECDSA / 哈希 | secp256k1 / Keccak256、SM3 | secp256k1 / Keccak256、SM3 |
| 传输安全 | 标准 + 国密 SSL | 标准 + 国密 SSL |
两者均支持国密(SM2/SM3/SM4)——国内合规硬性要求。泉链的优势在于国密为原生封装、集成更清晰,同时执行层保持全球互操作。
2.5 Java / JDK 依赖
| 维度 | FISCO BCOS | 泉链 |
| JDK 要求 | Oracle JDK 1.8(严格) | OpenJDK 25(当前) |
| 状态 | 2019 年 4 月已终止支持 | 当前版本,持续安全维护 |
FISCO BCOS 最致命的技术局限。要求 Oracle JDK 1.8(2019 年终止支持)带来安全、合规、人才与运维四重风险;泉链运行 OpenJDK 25 从根本上规避。
2.6 部署与操作系统
| 维度 | FISCO BCOS | 泉链 |
| 操作系统 | 仅 CentOS 7.2+ / Ubuntu 16.04+(均已停止支持) | 任意现代 Linux(Ubuntu 24.04、RHEL 9) |
| 容器支持 | 有限 | 完整 Docker / Kubernetes |
2.7 手续费与用户体验
| 维度 | FISCO BCOS | 泉链 |
| 手续费模型 | 计量收费 | 零手续费 |
| B2B2C 可行性 | 差——用户排斥手续费 | 优秀——体验无缝 |
泉链最显著的体验优势。对 B2B2C(机构为个人签发凭证 / 存证)而言,计量式手续费是致命障碍;泉链由机构承担极低基础设施成本,终端用户零摩擦。
2.8 高效——按需出块
不同于多数区块链每隔数秒出块并永久存储海量空数据,泉链按需出块:有负载时加速、空闲时安静,空闲期抑制空块并将网络产生的数据削减约 95%,普通商用硬件即可运行。
03 对比汇总
| 维度 | FISCO BCOS | 泉链 | 优势方 |
| 架构 | 单体、专有 | 模块化、标准 EVM | 泉链 |
| 共识 | PBFT/Raft(2017) | QBFT(现代) | 泉链 |
| 性能 | 2 万–20 万 TPS | 待定 | FISCO BCOS |
| EVM 兼容 | 部分 | 完整(Prague) | 泉链 |
| JDK | Oracle 1.8(停止支持) | OpenJDK 25 | 泉链 |
| 操作系统 | 已停止支持 | 任意现代 Linux | 泉链 |
| 国密 | 支持(附加) | 原生(封装) | 泉链 |
| 手续费 | 计量收费 | 零手续费 | 泉链 |
| 高效性 | 固定间隔 | 按需(空闲削减约 95%) | 泉链 |
| 生态成熟度 | 丰富(中国) | 起步(全球) | FISCO BCOS |
| 生产规模 | 300+ 部署 | 有限 | FISCO BCOS |
04 监管与合规定位
| 备案 | FISCO BCOS | 泉链 |
| ICP 备案 | 符合 | 已备案(浙ICP备2025202213号-10) |
| 公安联网备案 | 符合 | 符合 |
| 网信办区块链信息服务备案 | 该联盟链已备案 | 备案中 |
注:表中「该联盟链已备案」指 FISCO BCOS 本身已通过网信办区块链信息服务备案;本平台(泉链)的区块链备案正在办理中,尚未取得备案号。
"一条兼容 EVM、具备零手续费体验与国密支持的现代可信记录平台——企业区块链面向合规的演进版本,规避了老一代联盟链的遗留 JDK 与操作系统约束,由浙江玮瀚科技有限公司运营。"
05 结论
不将泉链定位为 FISCO BCOS 的"竞争者",而定位为"下一代"——解决其因 2017 年代架构而无法解决的体验、开发者体验与遗留技术问题。对于受监管记录场景,泉链的零手续费模型与现代技术栈使其成为更优选择,且全面符合中国监管要求。
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
| Attribute | FISCO BCOS | Triquan Chain |
| Launch year | 2017 | 2026 (live, producing blocks) |
| Initiator / operator | Jinlianmeng (WeBank, Tencent, Huawei, SZSE) | Zhejiang Weihan Technology Co., Ltd. |
| Engine / runtime | C++ / Java (Oracle JDK 1.8) | Hyperledger Besu 26.6.1 / OpenJDK 25 |
| Architecture | Monolithic permissioned consortium chain | EVM-compatible, permissioned, gasless |
| Ecosystem | 5,000+ institutions, 100,000+ members | Inherits the global Ethereum ecosystem |
02 Detailed Technical Comparison
2.1 Architecture & Design
| Aspect | FISCO BCOS | Triquan |
| Virtual machine | Custom EVM implementation | Standard Ethereum EVM (Prague) |
| Tooling | Proprietary, requires retraining | Solidity / Hardhat / Foundry / Remix / ethers.js |
| Upgrade path | Platform-dependent releases | Follows the Ethereum roadmap (EIPs) |
| Interoperability | Limited (WeCross) | Native Ethereum interoperability |
FISCO BCOS's custom EVM is not fully compatible with standard Ethereum tooling; Triquan inherits the entire Ethereum developer ecosystem — millions already know Solidity and its tools, with no retraining.
2.2 Consensus
| Aspect | FISCO BCOS | Triquan |
| Algorithms | PBFT, Raft (2017-era) | QBFT (IBFT 2.0 successor) |
| Finality | Immediate | Immediate |
| Validator governance | View-change | On-chain voting, no restart |
Both offer BFT consensus with immediate finality. Besu's QBFT is widely adopted, well documented, and supports live validator governance — partners can be voted in without a restart.
2.3 Smart Contracts & Development
| Aspect | FISCO BCOS | Triquan |
| Contract languages | Solidity, C++, WBC-Liquid | Solidity, Vyper |
| EVM compatibility | Partial (custom extensions) | Full (standard Ethereum) |
| Development tools | Proprietary Java SDK, Console | Hardhat, Foundry, Remix |
A critical differentiator. FISCO BCOS ties developers to a Java SDK on Oracle JDK 1.8 and proprietary workflows; any Ethereum developer can build on Triquan immediately, no retraining required.
2.4 Cryptography & Compliance
| Capability | FISCO BCOS | Triquan |
| National crypto SM2/3/4 | Supported | Native support (wrapped) |
| ECDSA / hashing | secp256k1 / Keccak256, SM3 | secp256k1 / Keccak256, SM3 |
| Transport security | Standard + national SSL | Standard + national SSL |
Both support China's SM2/SM3/SM4 — a hard domestic requirement. Triquan's advantage is native wrapping and cleaner integration while the execution layer stays globally interoperable.
2.5 Java / JDK Dependency
| Aspect | FISCO BCOS | Triquan |
| JDK requirement | Oracle JDK 1.8 (strict) | OpenJDK 25 (current) |
| Status | End-of-life since April 2019 | Current, actively security-patched |
FISCO BCOS's most damning limitation. Oracle JDK 1.8 (EOL 2019) brings security, compliance, recruitment and operational risk; Triquan's OpenJDK 25 avoids all of it.
2.6 Deployment & OS
| Aspect | FISCO BCOS | Triquan |
| OS support | CentOS 7.2+ / Ubuntu 16.04+ only (both EOL) | Any modern Linux (Ubuntu 24.04, RHEL 9) |
| Containers | Limited | Full Docker / Kubernetes |
2.7 Gas Model & UX
| Aspect | FISCO BCOS | Triquan |
| Gas model | Metered | Gasless |
| B2B2C viability | Poor — users dislike fees | Excellent — seamless |
Triquan's biggest UX advantage. For B2B2C (issuing credentials / notarizing for individuals), metered gas is a dealbreaker; Triquan's gasless model gives end-users zero friction.
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
| Dimension | FISCO BCOS | Triquan | Advantage |
| Architecture | Monolithic, proprietary | Modular, standard EVM | Triquan |
| Consensus | PBFT/Raft (2017) | QBFT (modern) | Triquan |
| Performance | 20k–200k TPS | TBD | FISCO BCOS |
| EVM compatibility | Partial | Full (Prague) | Triquan |
| JDK | Oracle 1.8 (EOL) | OpenJDK 25 | Triquan |
| OS support | EOL only | Any modern Linux | Triquan |
| National crypto | Supported (bolt-on) | Native (wrapped) | Triquan |
| Gas model | Metered | Gasless | Triquan |
| Efficiency | Fixed interval | On-demand (~95% idle cut) | Triquan |
| Ecosystem maturity | Extensive (China) | Emerging (global) | FISCO BCOS |
| Production scale | 300+ deployments | Limited | FISCO BCOS |
04 Regulatory Positioning
| Filing | FISCO BCOS | Triquan |
| ICP filing | Compliant | Filed (Zhejiang ICP 2025202213-10) |
| Public Security filing | Compliant | Compliant |
| CAC blockchain filing | Filed (that consortium chain) | In progress |
Note: "Filed (that consortium chain)" refers to FISCO BCOS itself; Triquan's own CAC blockchain filing is in progress and no filing number has been issued yet.
"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 网络参数
| 链名称 | 泉链 / Triquan Chain |
| 链 ID / 网络 ID | 2869 |
| 共识 | QBFT(拜占庭容错)——即时最终性 |
| 执行客户端 / 运行时 | Hyperledger Besu 26.6.1 · OpenJDK 25 |
| EVM 版本 | Prague(Pectra 代) |
| 出块方式 | 按需(有负载约 5 秒);空闲时每 30 秒一个空块 |
| 最终性 | 即时 / 确定性(无回滚) |
| 手续费模型 | 零手续费——零基础费、零最低 gas 价 |
| 原生单位 | UNIT(内部记账单位,无货币价值、不可转让、浏览器隐藏) |
| 代币经济 | 无发行、无挖矿奖励、无交易、无投机 |
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 密码学
| 国密 | SM2(签名)、SM3(哈希)、SM4(对称)——原生支持(封装) |
| 国际标准 | secp256k1(ECDSA)、Keccak-256 |
| 传输安全 | TLS/SSL,含国密 SSL |
| 身份 | 基于 PKI;链上参与方身份登记 |
2.5 存储与数据治理
存储引擎 RocksDB,采用默克尔帕特里夏树世界状态。数据本地化——全部节点与数据托管于运营方管控、位于其属地的基础设施。查询经区块浏览器链下索引(与账本解耦)。账本仅追加、具密码学链接,记录不可事后更改。
03 高效——按需出块
泉链按需出块:有负载时加速、空闲时安静。空闲期抑制空块并将网络产生的数据削减约 95%,在普通商用硬件上稳定运行——同时降低成本与存储占用。
04 监管监督
- 监督节点——运营方可为主管机关配置专门的只读 / 监管节点,在不授予写入权限的前提下,对全部链上记录提供实时、防篡改的可见性。
- 可审计性——每笔交易与记录均被永久且可验证地记录;任何记录均可通过重算其密码学哈希并与链上取值比对而独立验证。
- 运营方问责——浙江玮瀚科技有限公司为网络、参与方及内容管理义务的唯一责任主体。
05 公开端点与安全
| 区块浏览器 | https://explorer.triquan.com |
| RPC(只读) | https://rpc.triquan.com |
| 暴露范围 | 只读 JSON-RPC(ETH/NET/WEB3/TRACE);写入受链上账户许可控制;管理/共识/许可类方法不对外暴露 |
所有公开端点启用 TLS;写入/共识/管理端口对公网防火墙隔离;账户与节点双层许可;确定性最终性(无回滚风险);无代币经济(消除投机与金融工具风险)。
06 合规定位
| 备案 / 要求 | 状态 |
| ICP 备案 | 符合 |
| 公安联网备案 | 符合 |
| 网信办区块链信息服务备案 | 高度可行(许可制、具监督节点能力) |
| 国密 SM2/3/4 | 支持 |
| 数据本地化 | 运营方管控基础设施 |
| 无代币 / 无投机 | 零手续费,无发行、交易或金融工具属性 |
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
| Chain name | 泉链 / Triquan Chain |
| Chain ID / Network ID | 2869 |
| Consensus | QBFT (Byzantine Fault Tolerant) — immediate finality |
| Execution client / runtime | Hyperledger Besu 26.6.1 · OpenJDK 25 |
| EVM version | Prague (Pectra generation) |
| Block production | On demand (~5 s under load); one empty block / 30 s when idle |
| Finality | Immediate / deterministic (no reorgs) |
| Gas model | Gasless — zero base fee, zero minimum gas price |
| Native unit | UNIT (internal accounting unit; no monetary value, non-transferable, hidden in explorer) |
| Token economy | None — no issuance, mining rewards, trading or speculation |
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
| National crypto | SM2 (signatures), SM3 (hashing), SM4 (symmetric) — native (wrapped) |
| International standard | secp256k1 (ECDSA), Keccak-256 |
| Transport security | TLS/SSL incl. national SSL |
| Identity | PKI-based; on-chain participant identity registry |
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
| Block explorer | https://explorer.triquan.com |
| RPC (read) | https://rpc.triquan.com |
| Exposure | Read-only JSON-RPC (ETH/NET/WEB3/TRACE); writes are admission-controlled by on-chain account permissioning; admin/consensus/permissioning methods not exposed |
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
| Filing / Requirement | Status |
| ICP filing | Compliant |
| Public Security filing | Compliant |
| CAC blockchain information service filing | Highly feasible (permissioned, supervisory-node capable) |
| National cryptography SM2/3/4 | Supported |
| Data localization | Operator-controlled infrastructure |
| No token / no speculation | Gasless; no issuance, trading or financial-instrument traits |
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.