先说明面上的。官方文档写得很清楚:“matches and stores data off chain and provides smart contract level guarantees of their execution on chain”。订单匹配走链下,结算结果通过智能合约上链保证。这套ZK Stack validium加中央限价订单簿的架构,能跑60万笔/秒,速度确实直逼CEX。Spearbit在2024年12月做了28天全面审计,团队在认真做工程,这点得承认。
但拆完技术细节,我有点犯嘀咕。
官方“Architecture Overview”里有一句:“users requests are routed through our Backend infrastructure - the only permissioned entity allowed to execute transactions against our smart contracts”。所有请求必须经过GRVT后端,后端是唯一被允许向L2合约提交交易的主体。翻译成人话:GRVT跑的是私有链。后端被入侵,整个系统就暴露了。官方在Validium模式说明里也承认“operator keeps block data confidential”,即数据掌握在运营商手里。四层合约加私有后端入口,每个接口都是潜在漏洞点。审计能覆盖代码逻辑,覆盖不了跨层交互的组合漏洞。多层防御到底是在堵漏洞还是在堆攻击面?我说不好。
深夜翻@grvt_io 官方文档,翻到Hybrid Architecture那节时我停下。FAQ里写得清楚:“GRVT has a hybrid architecture that is made up of both on-chain and off-chain systems for scalability, security, and privacy.”链下撮合、链上结算。再看数据,600,000笔/秒、亚毫秒级延迟。CEX级速度加ZK自托管,这套组合拳确实漂亮。
但我翻到另一段愣住了。文档说:“A subset of the off chain actions are pushed to the GRVT chain. These actions are then published as zero-knowledge proofs to verify off-chain transactions on Ethereum.”链下撮完打包成ZK证明扔上以太坊。听着顺,但L2BEAT的风险评估专门点了一句:“Each update to the system state must be accompanied by a ZK proof”,问题就在这个“必须”上。
ZK证明生成依赖Boojum虚拟机特定版本。底层迭代、版本升级,兼容性漏洞跟着来。批量证明验证一旦失效,所有用户提现、结算全得堵死。L2BEAT的ZK Catalog专门追踪各项目的verifier合约,流程是“regenerating Solidity files directly from source code to confirm deployed contracts are legitimate”。他们为什么这么干?因为验证密钥生成依赖trusted setup,而“SNARKs require a trusted setup”这是信任假设。