版权声明（Copyright Notice）

本文翻译自@ZKCross团队关于ZKCross项目的文档。已得到作者的授权。译者为@chainguys。转载请注明作者和译者。

（Coptyright©2021 by @ZKCross ,translated by @chainguys）

本翻译文章所展示的一切信息都只是为了学习和交流目的，不能也不应成为任何财务或投资建议。

(All content shown are for communication and learning purposes, cannot and should not be viewed as any form of Financial or Investment Advice)

本翻译文章所展示的一切信息都只是为了学习和交流目的，不能也不应成为任何财务或投资建议。

(All content shown are for communication and learning purposes, cannot and should not be viewed as any form of Financial or Investment Advice)

什么是 ZKCross (What is ZKCross)

ZKCross is a trustworthy cross-chain Layer2 network backed by zero-knowledge technology.

ZKCross 是一个由零知识证明技术支持的可信跨链 Layer2 网络。

It creates a universal layer that connects various blockchains, on top of which rich cross-chain applications can run safely and efficiently offering a seamless multi-chain user experience.

它创建了一个连接各种区块链的通用层，在此之上丰富的跨链应用程序可以安全高效地运行，用户可以拥有无缝的多链体验。

ZKCross为何如此独特? (What makes ZKCross unique)

安全可靠 (Security & Trustworthy)

ZKCross addresses the third-party trust issue of cross-chain by verifying computations on the dest chain using zk-SNARK proofs.

通过使用zk-SNARK证明来验证目标链上的计算，ZKCross 解决了跨链第三方信任问题。

zk-SNARK proofs are mathematically certified to guarantee that only valid cross-chain transactions are executed and cannot be manipulated or falsified, hence ensuring the security of funds.

zk-SNARK 证明已经过数学验证，保证只有有效的跨链交易被执行，而不能被操纵或伪造，进而确保资金安全。

• Zero-knowledge proof guarantees that nobody, including the platform itself, can upload fake transactions or fund withdrawal request to the dest chain successfully.
  零知识证明保证，包括平台本身在内的任何人都无法上传虚假交易或提款请求到目标链。

• In virtue of ZK-Rollup's on-chain data availability, account states can always be rolled back in case of attacks, even when all the data on ZKCross Layer2 is lost.
  凭借 ZK-Rollup 的链上数据可用性，即使 ZKCross Layer2 上的所有数据都丢失，帐户状态也可以在受到攻击时始终回滚。

低成本和高扩展性 (Low Cost and High scalability)

ZKCross leverages zk-Rollup technology batching a large number of cross-chain transactions into a single one, so as to reduce the cost and improve cross-chain scalability without sacrificing security.

ZKCross 利用 zk-Rollup 技术将大量跨链交易变为单个批量处理，从而在不牺牲安全性的情况下降低了成本并提高了跨链可扩展性。

通用Layer2 (Universal Layer2)

ZKCross's target is to provide a universal layer to manipulate and synchronize the global state between various block-chains which support smart contracts. To achieve this, ZKCross introduces a Layer2 chain (ZKCross Layer2) to process most of the transactions that query or alter the state.

ZKCross 的目标是：提供一个通用层，来操作和同步支持智能合约的各种区块链之间的全局状态。为了实现这一点，ZKCross 引入了 Layer2 链（ZKCross Layer2）来处理大部分查询或改变状态的交易。

This model lets ZKCross scale communication across many chains, regardless of how many there are.

无论有多少链，该模型都可以让 ZKCross跨多链扩展通信。

ZKCross vs 其他 (ZKCross vs Others)

Compare with other cross-chain solutions: ZKCross is zero-knowledge-proof based which is more secure, trustworthy, and scalable(high throughput/low cost).

与其他跨链解决方案相比：ZKCross 基于零知识证明，更加安全、可信、可扩展（高吞吐量/低成本）。

ZKCross 如何工作? (How does ZKCross work)

ZKCross is designed to have a chain at layer-2 that acts as a relayer. This layer 2 chain monitors and synchronizes the state of many separate blockchains to ensure a consistent state throughout the whole network. Below is a normal zkRollup function within Ethereum.

ZKCross 的设计是：在layer 2有一条链作为中继器。该layer 2链监控和同步许多独立区块链的状态，进而确保整个网络的状态一致。下面是以太坊中一个正常的 zkRollup功能。

However, ZKCross uses this zero-knowledge technology as the foundation for cross-chain communication by solving the third parties' trustworthy problems that other zkRollup experience using a zk-SNARK proof.

然而，ZKCross 使用这种零知识证明技术作为跨链通信的基础，然后使用 zk-SNARK 证明解决了其他 zkRollup 会遇到的第三方信任问题。

The zk-SNARK improves cross-chain security and solves the third parties' trustworthy problem by zk-SNARK proofs.

通过 zk-SNARK 证明，zk-SNARK提高了跨链安全性并解决了第三方的信任问题。

This proof will be generated to ensure that:
此证明会被用来确保：

• All state changes are the result of accurately running the zk circuits.
  所有状态变化都是准确运行 zk回路 (zk circuits) 的结果

• And then, these zk-SNARK proofs will be submitted to the Layer1 zk-Verify module smart contract.
  然后，这些 zk-SNARK 证明将被提交给 Layer1 中zk-Verify 模块的智能合约。

Requests for funds flow will be executed only after zk-Verify returns success.

只有在 zk-Verify 返回成功后，才会执行对资金的请求。

The process guarantees that ZKCross can prevent almost all known cross-chain attacks. For example, even if the private keys of all trusted intermediates are leaked. The protocol funds are still safe because the zk-Verify module verifies signatures and zk-SNARKs proof, which is mathematical security.

该过程保证了 ZKCross 可以阻止几乎所有已知的跨链攻击。例如，即使所有可信中间人的私钥都被泄露。协议的资金仍然是安全的，因为 zk-Verify 模块的验证签名和 zk-SNARKs 证明，这是数学层面的安全性。

ZKCross架构 (ZKCross Architecture)

The core part of ZKCross is a universal Layer2 chain with zk-Circuits running on top of it. Also, there are several Layer1-chain and off-chain components.

ZKCross 的核心部分是一个通用的 Layer2 链，zk回路(zk-Circuits)在其上运行。此外，还有几个 Layer1 链和链下组件。

核心组件(Core components)

• ZKCross Layer2 Chain
  ZKCross Layer2 链

• zk-Circuits
  zk回路

• Layer2 zk-Relayers
  Layer2 zk中继器

• Layer1 chain relayers
  Layer1 链中继器

在Layer1链上 (On Layer1-Chain)

• zk-Bridge contracts
  zk跨链桥合约
• zk-Verify contracts
  zk验证合约

ZKCross Layer2 链 (ZKCross Layer2 Chain)

ZKCross' target is to provide a universal layer to manipulate and synchronize the global state between various block-chains. To achieve this, ZKCross introduces a Layer2 chain (ZKCross Layer2) to process most of the transactions that query or alter the state.

ZKCross 的目标是提供一个通用层，来操作和同步各种区块链之间的全局状态。为了实现这一点，ZKCross 引入了 Layer2 链（ZKCross Layer2）来处理大部分查询或改变状态的交易。

Currently, ZKCross Layer2 Chain is a normal proof-of-stake chain, it produces blocks and validates transactions the same as other proof-of-stake chains except ZKCross Layer2 Chain uses ZKC token as gasfee instead of ETH.

目前，ZKCross Layer2链是一个普通的 PoS 链，除了 ZKCross Layer2 链使用 ZKC 代币而不是 ETH 作为 gas费用 之外，它的出块和验证交易与其他 PoS 链相同。

The biggest difference between ZKCross layer2 Chain and other chains is that all application running on top of ZKCross Layer2 is written using zk-Circuits. e.g for a cross-chain dex, an AMM curcit engineer is needed.

ZKCross layer2 链与其他链的最大区别在于，所有运行在 ZKCross Layer2 之上的应用都是使用 zk回路(zk-Circuits) 编写的。例如，对于跨链 dex，需要 AMM 回路工程师。

(If you are not familiar with zk-Circuits, please have a look at this document for reference.)

（如果您不熟悉 zk-Circuits，请查看 这篇文档 以供参考。）

交易 (Transactions)

In ZKCross the global state of an application is compressed as a Merkle hash tree. An application in ZKCross is a set of operations (f : S → S) which are defined as how the global state (S) of the application can be changed.

在 ZKCross 中，应用的全局状态被压缩为 Merkle 哈希树。ZKCross 中的应用程是一组操作（f : S → S），被定义为如何更改应用的全局状态（S）。

A ZKCross transaction is composed of four stages: Operating Stage, Batching Stage, Proving Stage, Finalizing Stage.

ZKCross 交易由四个阶段组成：操作阶段(Operation Stage)、批处理阶段(Batching Stage)、证明阶段(Proving Stage)、完成阶段(Finalizing Stage)。

操作阶段 (Operating Stage)

At the operating stage, an operation is performed on ZKCross Layer2 and changes the global state (S) thus changing the Merkle root.

在操作阶段，在ZKCross Layer2 进行操作并改变全局状态（S），进而改变 Merkle 根。

批处理阶段 (Batching Stage)

After the operating stage, the ZKCross Layer2 relayers will notice it and then pack the operation information into a transaction pool.

操作阶段结束后，ZKCross Layer2 中继器会注意到它，然后将操作信息打包到交易池中。

证明阶段 (Proving Stage)

When sufficient transactions are batched in ZKCross-Monitor, it compresses the computation into ZKSnark proof. The proof is encoded as the sequence of operation arguments together with an updated merkle tree.

当在ZKCross监视器中的批处理交易足够多时，它会将计算压缩为 ZKSnark 证明。证明与更新的默克尔树一起被编码为操作参数序列。

完成阶段 (Finalizing Stage)

Once a proof of batched operation sequence is generated by a ZKCross Layer2 relayer, it will broadcast to various underlying block-chains. Each connected layer1 chain will verify the proof and then send acknowledge back to the ZKCross Layer2 to finalize the transaction.

一旦 ZKCross Layer2 中继器生成批处理操作序列的证明，它将广播到各种基础/底层区块链。每个连接的 layer1 链将验证证明，然后将确认发送回 ZKCross Layer2 来完成交易。

申请 (Application)

A ZKCross Layer2 application is defined by a bunch of operations (f : state → state) that alter and query the application state s.

一个 ZKCross Layer2 应用程序由一组改变和查询应用状态 s 的操作（f : state → state）定义。

Layer2 state can be encoded into a list of Merkle Tree leaf nodes from which a Merkle hash tree can be built.

Layer2 状态可以编码为 Merkle 树叶节点列表，从中可以构建默克尔哈希树。

A SNARK proof of f (s) = s' is a snark proof generated from the following circuit constraint:

从以下回路约束生成一个f (s) = s' 的 SNARK 证明：

At the operation stage, s' is calculated and stored in the ZKCross Layer2. Furthermore, an operation Event is fired after the operation stage which will be captured by the ZKCross Layer2 relayer which will generate the related snark proof.

在操作阶段，s' 被计算并存储在 ZKCross Layer2 中。此外，在操作阶段之后会触发一个操作事件，该事件会被 ZKCross Layer2 中继器捕获，并生成相关的 snark 证明。

Merkely树编码的应用状态 (Merkely Tree Encoding of Application State)

Merkle tree is a tree in which every leaf node is labeled with the cryptographic hash of a data block, and every non-leaf node is labeled with the cryptographic hash of the labels of its child nodes.

Merkle 树是一棵(逻辑)树，其中每个叶节点都用数据块的密码哈希标记，每个非叶节点都用其子节点标签的密码哈希标记。

As shown in the above graph, each data block has a unique Merkle Tree Index(MTI) and each MTI encodes a unique path from top to leaf. For example, suppose that the height of the Merkle tree is k. Then there are 2(k)-1 non-leaf nodes and the first node of leaf node is a k length binary number key = 1000 · · · 00. Moreover, the path from the leaf node to the top node can be calculated by dividing the index by two:

如上图所示，每个数据块都有一个唯一的默克尔树索引（MTI），每个 MTI 都将一个从顶部到叶子的唯一路径进行编码。例如，假设 Merkle 树的高度为 k。那么有2(k)-1个非叶子节点，叶子节点的第一个节点是一个长度为k的二进制数秘钥 = 1000···00。此外，从叶子节点到顶部节点的路径可以通过用索引除以2得到：

Also, the sibling path can be calculated as:
此外，兄弟路径可以计算为：

To calculate the root hash after the modification of data of D(p0 ), we need to calculate new hash of H(pi) using the formula of the hash rule of Merkle Tree H(p i+1 ) = hash(pi , si )

为了计算 D(p0 ) 数据修改后的根哈希，我们需要使用默克尔树的哈希规则 H(p i+1 ) = hash(pi,si ) 来计算新的哈希H(pi)

Thus it follows that the entire constraints of the merkley tree can be represented as follows:

因此，默克利树的整个约束可以表示如下：

• before modification
  修改前

• After modification
  修改后

zk-SNARK 回路 (zk-SNARK Circuits)

The circuits defined for ZKP can help Layer1 chain properly verify the following thing:

为ZKP定义的回路可以帮助 Layer1 链正确验证以下内容：

• A Command is sent by an invalid end-user (by validating the signature and command target).
  命令是否由无效的最终用户发送（通过验证签名和命令目标）

  • Validate the signature of the command.
    验证命令的签名。

  • Validate that the command’s target assets belong to the user.
    验证命令的目标资产是否属于用户。

  • Check the public key in storage.
    检查存储中的公钥。

• The storage is properly modified according to the command.
  是否根据命令正确修改存储。

  • The transaction logic is written into the circuits.
    交易逻辑被写入回路。

回路输入 (Circuit Inputs)

• 1.A batch of commands.
  一组批处理命令

• 2.A secure hash of the batch of commands, thus we can make these commands private.

  一组批处理命令的安全哈希，由此我们可以将这些命令转为私密。

• 3.Signatures of these commands, can be private because to attack the circuits by giving a wrong signature is cryptographically difficult.

  这些命令的签名可以是私密的，因为通过出示错误签名来攻击回路，在密码学上是困难的。

• 4.Merkle tree info
  Merkle 树信息

  • inital root hash H(p0)
    初始根哈希 H(p0)

  • final root hash H(pK)
    最终根哈希 H(pK)

  • Paths that can help the circuits to verify the merkle tree change. These paths are private because the hash function for the merkle tree is a cryptographically secure hash.
    可以帮助回路验证默克尔树变化的路径。这些路径是私密的，因为merkle树的哈希函数是加密安全函数。

回路中的约束包括 (The constraint in that circuits include)

• 1.The hash of the commands is equal to the input hash.
  命令的哈希值等于输入的哈希值。

• 2.The signature of each command is valid.
  每个命令的签名都是有效的。

• 3.The public key should be the correct one stored in merkle tree (so it also needs to verify the merkle tree path for the public key).
  公钥应该正确存储在merkle树中（所以还需要验证公钥的merkle树路径）。

• 4.Each command has multiple steps on changing the merkle tree, so it needs to verify each merkle tree path, and also verify the changes (usually it only changes a leaf value, so the circuits can calculate the root hash after the change).
  每个命令对merkle树的改变都有多个步骤，所以需要验证每一个merkle树的路径，还要验证变化（通常只改变一个叶子值，所以回路可以计算改变后的根哈希）

• 5.The merkle tree root is truly changed from the start to the end through these change steps.
  通过这些变更步骤，merkle树根从头到尾真正进行了变化。

链上合约 (On-Chain contracts)

The On Layer1 Chain contracts mainly contains two parts: bridge interface and verification interface for token assets transfer.

在Layer1 链上的合约主要包含两部分：代币资产转移的跨链桥接口和验证接口。

跨链桥接口 (Bridge Interface)

• Deposit
  存款

  Put assets into the account of the bridge contract from the user’s Layer1 account.
  将资产从用户的 Layer1 账户放入跨链桥合约的账户。

• Withdraw
  提款

  Withdraw assets from the account of the bridge contract back into the user’s Layer1 account.
  将跨链桥合约账户中的资产提取回用户的 Layer1 账户。

验证接口 (Verification Interface)

The Verification interface verifies the ZK-SNARK proof generated by the Layer2 zk-Relayer.

验证接口验证 Layer2 zk-中继器生成的 ZK-SNARK 证明。

function zk_verify(
    uint256 l2account,
    uint256[] memory tx_data,
    uint256[] memory verify_data,
    // [8]: old root, [9]: new root,
    // [10]: sha_low, [11]: sha_high
    uint256 vid,
    uint256 nonce,
    uint256 rid
)

链下组件 (Off Chain Components)

zk中继器 (zk-Relayers)

Each time ZKCross Layer2 zk-Relayer captures an event, it pushes the event into a rollup queue. Once the rollup queue reaches its maximal size, a zk proof will be generated by ZKCross Layer2 zk-Relayer.

ZKCross Layer2的zk中继器 (zk-Relayers) 每次捕获到一个事件，它都会将该事件推送到一个汇总队列中。一旦汇总队列达到其上限，ZKCross Layer2 zk中继器 (zk-Relayers)将生成 zk 证明。

ZKCross Layer2 zk-Relayer gives each batched transaction a unique transaction id and broadcasts its zk proof to ZKCross' zk bridge contract on Layer1 blockchains.

ZKCross Layer2的中继器 (zk-Relayers)为每个批处理交易提供一个唯一交易 id，并将其 zk 证明广播到 ZKCross 在 Layer1 区块链上的zk跨链桥合约。

观察者 Watchers

The watcher observes the user's interactions with the zk-bridge contract (by watching the zk-bridge contract) and notifies to ZKCross Layer2.

观察者观察用户与zk跨链桥(zk-bridge) 合约的交互（通过观察zk跨链桥合约）并通知 ZKCross Layer2。

现有应用 (Existing Applications)

There are currently two existing applications built on top of ZKCross.
目前构建在 ZKCross 之上有两个应用。

• Cross Chain Dex
  跨链去中心化交易所

• NFT Bridge
  NFT跨链桥

第三方应用 (Third-Party Applications)

There are currently no third-party applications implemented on top of the ZKCross message passing mechanism. If you are planning to build one cross-chain application on top of ZKCross, let us know in our Discord!

目前没有在 ZKCross 消息传递机制之上实现的第三方应用。如果您计划在 ZKCross 之上构建一个跨链应用，请在我们的 Discord 中告诉我们！

跨链Dex用户指南 (CrossChain Dex UserGuide)

Let’s look at an example: Assume there are two blockchains: Chain A and Chain B. Now, what happens if we want to swap tokens of Chain A to tokens of Chain B? e.g swap 10 ETH to 10 BNB.

让我们看一个例子：假设有两条区块链：链 A 和链 B。现在，如果我们想将链 A 的代币交换为链 B 的代币，那会发生什么？例如将 10 ETH 兑换成 10 BNB。

To do a cross-chain token swap from Ethereum to BSC chain, ZKCross first monitors a deposit event to our zk-Bridge of Ethereum. (e.g user deposit 10 ETH event). And then the user can see his 10 ETH balance in ZKCross layer2 Chain.

为了进行从以太坊到 BSC 链的跨链代币交换，ZKCross 首先监控到我们的以太坊 zk-Bridge 的存款事件—例如用户存入 10 ETH 事件。然后用户可以在 ZKCross layer2 链中看到他的 10 ETH 余额。

Then he can swap ETH to BNB in cross-chain layer2 AMM-DEX which is high tps and low gas fees.

然后他可以在跨链layer2 中高tps和低gas费的AMM-DEX里将ETH兑换成BNB。

Then he can withdraw BNB from our layer2 chain to BSC Chain, the zk-Relayers will generate a zk-Proof together with withdraw request and submit them to zk-Verify module in BSC.

然后他可以将 BNB 从我们的 layer2 链提取到 BSC 链，zk中继器 (zk-Relayers) 将生成一个 zk证明 (zk-Proof) 和一个提取请求，并将它们提交给 BSC 中的 zk验证 (zk-Verify) 模块。

Once zk-Verify module confirms the zk-Proof is correct, the user can see BNB in his BSC account balance.

一旦 zk验证 (zk-Verify) 模块确认zk证明 (zk-Proof) 是正确的，用户就可以在他的 BSC 账户余额中看到 BNB。

第三方应用 (Third-Party Applications)

Coming Soon
即将添加

ZKCross SDK

Many applications using ZKCross may require a frontend to interact with the underlying smart contracts and ZKCross Layer2. We currently provide an SDK that supplies several utilities for developers including:

许多使用 ZKCross 的应用可能需要前端来与底层智能合约及ZKCross Layer2 交互。我们目前提供的 SDK 可为开发人员提供多种实用程序，包括：

• Methods for interacting with ZKCross Layer 1 smart contracts.
  与 ZKCross Layer 1的智能合约交互的方法。

• Tools for submitting and parsing structured messages through ZKCross. 通过 ZKCross 提交和解析结构化消息的工具。

• Methods for interactive with ZKCross Layer2.
  与 ZKCross Layer2 交互的方法。

The SDK detail will be coming soon.
SDK 详细信息即将推出。

代币经济学 (Tokenomics)

ZKCross uses the veToken model, which is similar to curve finance. This model has been battle-tested with billions of dollars and attracted a thriving ecosystem around it.

ZKCross 使用类似于曲线金融的 veToken 模型。这种模式已经过数十亿美元的实战考验，并吸引了围绕它的蓬勃发展的生态系统。

There are two tokens of ZKCross: $ZKC and $veZKC.

ZKCross 有两种代币：$ZKC 和 $veZKC。

$ZKC简介 (Introducing $ZKC)

$ZKC is the ZKCross DAO token. The main purpose of $ZKC is to incentivize the ZKCross community, including liquidity providers and node operators, and get as many users involved as possible in the protocol's governance.

$ZKC 是 ZKCross DAO 代币。 $ZKC 的主要目的是激励 ZKCross 社区，包括流动性提供者和节点运营商，并让尽可能多的用户参与协议的治理。

总供应量 (Total Supply)

The total supply of $ZKC is: 1,000,000,000$ZKC 的总供应量为：1,000,000,000

代币分配和时间表 (Token Distribution and Schedule)

• 51%Community Treasury
  51% - 社区金库

• 20% Investors
  20% - 投资者

• 19% Team, Advisors, and Strategic Partners
  19% - 团队、顾问和战略合作伙伴

• 10% Marketing, Initial Liquidity, Airdrop
  10%- 营销、初始流动性、空投

The portion allocation to the team will be subject to a one-year lockup followed by a two-year linear vesting period.

分配给团队的部分将有一年的锁定期，然后是两年的线性归解锁。

Investors' tokens will be vested in 2 years on a quarterly based.
投资者的代币将在 2 年内按季度解锁。

社区金库 (Community Treasury)

A community-managed treasury opens up a world of infinite possibilities. We hope to see a variety of experimentation, including ecosystem grants and public goods funding, which can foster additional ZKCross ecosystem growth.

社区管理的金库打开了一个无限可能的世界。我们希望看到各种各样的实验，包括生态系统赠款和公共产品资助，这可以促进 ZKCross 生态系统的额外增长。

The community treasury will retain 51% of the $ZKC supply to distribute on an ongoing basis through contributor grants, community initiatives, liquidity mining, and other programs.

社区金库将保留 51% 的 $ZKC 供应，通过贡献者赠款、社区倡议、流动性挖矿和其他计划持续分配。

ZKCross community members control all $ZKC in the community treasury through voting governance.

ZKCross 社区成员通过投票治理，控制社区金库中的所有 $ZKC。

veZKC是什么?(What’s veZKC)

veZKC stands for vote-escrowed ZKC. It is a certificate of your ZKC locked for some time. Anyone intent to get veZKC can lock ZKC for any time between 1 year and four years.

veZKC 表示投票托管的 ZKC。它是您ZKC 锁定一段时间的证书。任何想要获得 veZKC 的人都可以将 ZKC 锁定 1 年到 4 年。

After the ZKC token is locked, the token holders will have a non-zero balance of veZKC. The longer you lock ZKC, the more veZKC you receive.

ZKC 代币锁定后，代币持有者将拥有非零余额的 veZKC。您锁定 ZKC 的时间越长，您收到的 veZKC 就越多。

投票权 (Voting power)

All ZKCross votes will be done based on voters' veZKC balances instead of ZKC balances. This ensures long-term alignment as only users locking $ZKC can participate in ZKCross’ governance and community treasury allocation.

所有 ZKCross 投票将基于选民的 veZKC 余额而不是 ZKC 余额进行。这确保了长期一致性，因为只有锁定 $ZKC 的用户才能参与 ZKCross 的治理和社区金库分配。

Any distribution of ZKC in community treasury, including grants, strategic partnerships, governance initiatives, liquidity minings, reward weight setting, and other programs, has to pass through the governance process via voting.

ZKC 在社区金库中的任何分配，包括赠款、战略合作、治理举措、流动性挖矿、奖励权重设置等项目，都必须通过以投票进行的治理过程。

费用分享 (Fee Sharing)

A percentage of fees collected by ZKCross will be distributed to veZKC holders through community lead DAO proposals.

ZKCross 收取的，一定比例的费用，将通过社区主导的 DAO 提案分配给 veZKC 持有者。

提升 (Boosting)

Another main benefit for veZKC is the ability to boost your rewards on provided liquidity, node operators, or any other incentives you get from ZKCross Ecosystem.

veZKC 的另一个主要好处是能够提高您对提供的流动性、节点运营商或您从 ZKCross 生态系统获得的任何其他激励措施的奖励。

FAQ

Coming Soon
即将添加

社区 (Community)

Discord: https://discord.gg/eveHqJqzdh

Twitter: https://twitter.com/thezkcross

Telegram: https://t.me/ZKCross

Blog: https://blog.zkcross.org

有用链接 (Links)

• Github

• Contracts & Audits
  智能合约 & 审计

  Coming Soon
  即将添加

• Layer2 RPC Address
  Layer2 PRC地址

  Coming Soon
  即将添加