diff --git a/docs/guides/ZKPool-A0.md b/docs/guides/ZKPool-A0.md deleted file mode 100644 index 2925784..0000000 --- a/docs/guides/ZKPool-A0.md +++ /dev/null @@ -1,43 +0,0 @@ -## Taiko Project Support - -Taiko is a decentralized, Ethereum-equivalent zk-rollup project with Type 1 zkEVM technology. - -ZKPool A0 Phase 0 (ZKPool A0-0) is dedicated to the Taiko Alpha-4 (A4) Testnet, and supports users who want to join as individual provers. According to the plan, ZKPool will soon expand into more ZKP projects. - -Taiko A4 Testnet comes with a new staking-based prover economics. Blocks will be distributed to the top 32 staked provers. To become one of the top 32 provers, a substantial amount of Test Taiko tokens (TTKOe) and a minimum of 32 prover machines are required. It's very difficult for smaller and solo provers to successfully compete in this staking contest. - -## Hardware requirements - -The Taiko project supports various provers to join, CPU, GPU, and so on. To avoid dominance by hardware performance, it has a relatively long proof window that CPU devices can join as a prover. - -ZKPool will provide both CPU and GPU binaries (coming soon), and it will also open-source the prover client codes to support 3rd party to build its hardware binary. - -The hardware that meets the minimum requirements can run CPU prover binary: - -- 8 or 16 core CPU -- 32 GB memory - -In Taiko A4, the proof time on the above hardware may take more than 10 minutes. - -Note from [Taiko](https://taiko.mirror.xyz/HJCWBluTwmNyWRkhzIXXr0k5xAaalRNtmlyDMJTu_ws): this is not representative of what a full ZK-EVM proof will eventually cost as not all circuits are included yet. More circuits are being integrated as we go. - -In the future, the hardware requirements may be updated as Taiko covers more circuits. - -## Reward distribution - -According to [Taiko](https://taiko.mirror.xyz/HJCWBluTwmNyWRkhzIXXr0k5xAaalRNtmlyDMJTu_ws): - -> Please note, reward or profit considerations (if any) will heavily depend on a variety of factors, and are in no way guaranteed. This holds for proposers, provers, and all network participants. Certain assumptions used may not reflect reality for the duration of the testnet period, protocol flaws can be found, and mainnet timing is uncertain. We reserve the right to adjust the program, with the ultimate goal of testing unprecedented permissionless proposing and proving in a ZK-Rollup. You should only participate if you are keen to help the network test a technical design. Basically, for science. -> - -ZKPool will share the reward of TTKOe with provers, and in ZKPool A0-0, the distribution rule is: - -- ZKPool: 20% -- Prover: 80% - -Note: - -1. The distribution rule is just for testing in the Testnet. ZKPool has the right and plans to adjust it in the future. -2. The rewards are calculated based on a certain interval, for example, on a daily basis. -3. Currently, the reward cannot be withdrawn and will be recorded under the prover's wallet address. ZKPool will soon upgrade to support users in withdrawing the TTKOe. -4. The reward's actual value is not guaranteed. We participate to help Taiko to test and become a successful zk-rollup. \ No newline at end of file diff --git a/docs/guides/how-to-connect-ZKPool.md b/docs/guides/how-to-connect-ZKPool.md new file mode 100644 index 0000000..317afc1 --- /dev/null +++ b/docs/guides/how-to-connect-ZKPool.md @@ -0,0 +1,14 @@ +--- +sidebar_label: 'How to Connect as ZKP Requester' +sidebar_position: 1 +--- + +# Introduction +Currently, in ZKPool A1, we are opening the prover market to Taiko projects. + +We are also working on opening it to all zkp projects. A detailed guide will be released soon. + +# The Prover Market Endpoint for Taiko +HTTP: http://taiko-a5-prover-simple.zkpool.io + +HTTPS: https://taiko-a5-prover.zkpool.io \ No newline at end of file diff --git a/docs/overview.md b/docs/overview.md index bd320d7..97f1364 100644 --- a/docs/overview.md +++ b/docs/overview.md @@ -55,6 +55,6 @@ The design principles of ZKPool include: The ZKPool will have the following milestones: -- Centralized solution for one ZKP project -- Connect multiple ZKP projects with the unified ZKP provers -- Fully decentralized ZKP computing pool +- Connect one ZKP project (Done) +- Connect multiple ZKP projects with the UMP (Universal Modular Prover) (Ongoing) +- Fully decentralized ZKP computing pool via Super-UMP (TBD) \ No newline at end of file diff --git a/docs/guides/introduction.md b/docs/products/Release.md similarity index 60% rename from docs/guides/introduction.md rename to docs/products/Release.md index 2d956be..0a3b8f5 100644 --- a/docs/guides/introduction.md +++ b/docs/products/Release.md @@ -1,38 +1,17 @@ --- -sidebar_label: 'Introduction' -sidebar_position: 1 +sidebar_label: 'Release' +sidebar_position: 2 --- -# Introduction +# ZKPool A1 -ZKPool aims to connect various ZKP applications and ZKP provers and provide the following capabilities: - -- ZKPool gathers smaller provers' capacity together and provides bond as a pool. -- ZKPool operates to minimize the risks of being slashed. -- ZKPool calculates and distributes the rewards of provers. -- ZKPool makes it really easy for provers to join. - -Initially, ZKPool will assume the risk and provides bond on behalf of all the provers connected to the pool. The pool is open for registered provers to connect to. - -## General Flow - -Currently, the general flow is as follows: - -1. Register on [https://zkpool.io](https://zkpool.io/), generate the user account's unique access key. -2. Use the one command installation script to connect to ZKPool. -3. Login to [https://zkpool.io](https://zkpool.io/) to view prover machine status and rewards. - -## Releases - -### ZKPool A1 - -#### Taiko Project Support +## Taiko Project Support Taiko is a decentralized, Ethereum-equivalent zk-rollup project with Type 1 zkEVM technology. ZKPool A1 is dedicated to the [Taiko Alpha-5 (A5) Testnet](https://taiko.mirror.xyz/0jc5XA5RVjOUNVdRdGmw9prlsC4deA1XgZJppmXh8rs), and supports users who want to join as individual provers. -#### Hardware requirements +## Hardware requirements ZKPool supports various provers to join, CPU, GPU, and so on. @@ -43,7 +22,7 @@ The hardware that meets the minimum requirements can run CPU prover binary: - 8 or 16 core CPU - 32 GB memory -#### Reward distribution +## Reward distribution As ZKPool takes the risk of slashing, pays the Gas fee for submitting the proof and operation cost, ZKPool will share the reward of tokens with provers. Currently the distribution rule is: @@ -59,6 +38,4 @@ Note: 5. The actual value of the reward is not guaranteed. We participate to help Taiko test and become a successful zk-rollup. 6. ZKPool may consider offering additional incentives from the platform side, especially for early participants. However, this has not yet been determined. -### Legacy -#### [ZKPool A0](./ZKPool-A0.md) diff --git a/docs/products/_category_.json b/docs/products/_category_.json new file mode 100644 index 0000000..3182b52 --- /dev/null +++ b/docs/products/_category_.json @@ -0,0 +1,8 @@ +{ + "label": "Products", + "position": 3, + "link": { + "type": "generated-index", + "description": "Introduction about the products of ZKPool" + } +} diff --git a/docs/products/images/UMP.jpg b/docs/products/images/UMP.jpg new file mode 100644 index 0000000..6357214 Binary files /dev/null and b/docs/products/images/UMP.jpg differ diff --git a/docs/products/images/ecosystem.png b/docs/products/images/ecosystem.png new file mode 100644 index 0000000..55da7ac Binary files /dev/null and b/docs/products/images/ecosystem.png differ diff --git a/docs/products/images/two tier table.jpg b/docs/products/images/two tier table.jpg new file mode 100644 index 0000000..967f8c6 Binary files /dev/null and b/docs/products/images/two tier table.jpg differ diff --git a/docs/products/images/two-tier.jpg b/docs/products/images/two-tier.jpg new file mode 100644 index 0000000..5f5603e Binary files /dev/null and b/docs/products/images/two-tier.jpg differ diff --git a/docs/products/introduction.md b/docs/products/introduction.md new file mode 100644 index 0000000..762821c --- /dev/null +++ b/docs/products/introduction.md @@ -0,0 +1,46 @@ +--- +sidebar_label: 'Introduction' +sidebar_position: 1 +--- + +# Introduction + +ZKPool is an open and permissionless platform that connects various ZKP projects and provers, offering multiple capabilities: + +- ZKPool gathers the capacity of smaller provers and acts as a super prover proxy, providing necessary stake to ZKP projects. +- ZKPool provides competitive price to win the proof tasks and minimize the risks of being slashed. +- ZKPool distributes the rewards of provers among participants. +- ZKPool simplifies the process of joining for provers and ZKP projects. + +# The Ecosystem of ZKPool +The participants in ZKPool include: +1. ZKP Requester: Refers to ZKP projects that require ZKP proofs. +2. ZKP Prover: Operators who own the hardware and run the provers. +3. ZKP Accelerator: A team that provides accelerated software implementation for certain ZKP projects. + +The ZKP requester can also be a ZKP accelerator. For example, a ZKP project may have its own best GPU-accelerated software. + +The ZKP prover can also be a ZKP accelerator. For example, ZKP prover operators may develop their own accelerated software. + +The ecosystem is represented in the following diagram: +![Ecosystem](./images/ecosystem.png) + +# Two-tier ZKP proving tokenomics +Currently, many ZKP projects use their own proving systems and tokenomics. To establish a healthier and more cost-effective ZKP proving ecosystem, a two-tier proving tokenomics model can be a viable solution. Taiko proposed a solution after several rounds of iteration of proving tokenomics. We have further extended this solution to a two-tier framework. + +Under this approach, each ZKP project operates as tier 1, defining its own tokenomics. However, the selection, scheduling, penalty, reward, and rating of provers are delegated to tier 2, which is a shared prover pool. +![Two-tier](./images/two-tier.jpg) + +The scope of the two tiers is as follows: + +| | Tier 1 (ZKP projects) | Tier 2 (ZKPool) | +| --- | --- | --- | +| Scope | • Publish proof task.
• Establish rewards and penalties.
• Define key metrics such as proof window. | • Aggregate proof task.
• Schedule and rate prover resources.
• Distribute rewards.
• Assume penalty risk.
• Define price competition strategy | + + +# UMP (Universal Modular Prover) +ZKPool utilizes UMP (Universal Modular Prover) to integrate various provers. + +A Universal Modular Prover can run on the same hardware platform while supporting the proving work of various ZKP projects. + +![UMP](./images/UMP.jpg) \ No newline at end of file