From 4ec30d29395060742f6ba6f56be7fc8bacd3c7c4 Mon Sep 17 00:00:00 2001 From: Maximilian Hubert <64627729+gap-editor@users.noreply.github.com> Date: Sat, 1 Feb 2025 15:02:29 +0100 Subject: [PATCH 1/4] typo run.md have added a colon and have removed the repetition --- docs/run.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/run.md b/docs/run.md index a5de009..71ed016 100644 --- a/docs/run.md +++ b/docs/run.md @@ -4,7 +4,7 @@ ### Setup Environment -Install dependencies Node.js, yarn, hardhat. +Install dependencies: Node.js, yarn, hardhat. - Linux @@ -56,7 +56,6 @@ networks: { ### Compile ```shell -yarn yarn compile ``` From 0d97c4b52584eb30d4b257dfa968e588a7b4998f Mon Sep 17 00:00:00 2001 From: Maximilian Hubert <64627729+gap-editor@users.noreply.github.com> Date: Sat, 1 Feb 2025 15:04:51 +0100 Subject: [PATCH 2/4] typo proof-of-random-access.md have changed "PoRA consists of" to "PoRA, which consists" for clarity. --- docs/incentive-mechanism/proof-of-random-access.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/incentive-mechanism/proof-of-random-access.md b/docs/incentive-mechanism/proof-of-random-access.md index 2fb4861..58baa57 100644 --- a/docs/incentive-mechanism/proof-of-random-access.md +++ b/docs/incentive-mechanism/proof-of-random-access.md @@ -2,7 +2,7 @@ The ZeroGravity network adopts a Proof of Random Access (PoRA) mechanism to incentivize miners to store data. By requiring miners to answer randomly produced queries to archived data chunks, the PoRA mechanism establishes the relation between mining proof generation power and data storage. Miners answer the queries repeatedly and computes an output digest for each loaded chunk until find a digest that satisfies the mining difficulty (i.e., has enough leading zeros). PoRA will stress the miners' disk I/O and reduce their capability to respond user queries. So 0G Storage adopts intermittent mining, in which a mining epoch starts with a block generation at a specific block height on the host chain and stops when a valid PoRA is submitted to the 0G Storage contract. -In a strawman design, a PoRA iteration consists of a computing stage and a loading stage. In the computing stage, a miner computes a random recall position (the universal offset in the flow) based on an arbitrary picked random nonce and a mining status read from the host chain. In the loading stage, a miner loads the archived data chunks at the given recall position, and computes output digest by hashing the tuple of mining status and the data chunks. If the output digest satisfies the target difficulty, the miner can construct a legitimate PoRA consists of the chosen random nonce, the loaded data chunk and the proof for the correctness of data chunk to the mining contract. +In a strawman design, a PoRA iteration consists of a computing stage and a loading stage. In the computing stage, a miner computes a random recall position (the universal offset in the flow) based on an arbitrary picked random nonce and a mining status read from the host chain. In the loading stage, a miner loads the archived data chunks at the given recall position, and computes output digest by hashing the tuple of mining status and the data chunks. If the output digest satisfies the target difficulty, the miner can construct a legitimate PoRA, which consists of the chosen random nonce, the loaded data chunk and the proof for the correctness of data chunk to the mining contract. ## Fairness From f631712f375b0287a20986c12f44b3b80dd3eb83 Mon Sep 17 00:00:00 2001 From: Maximilian Hubert <64627729+gap-editor@users.noreply.github.com> Date: Sat, 1 Feb 2025 15:06:56 +0100 Subject: [PATCH 3/4] typo contributing.md lint is passing" could be more precisely stated as "the linter is passing" for clarity --- contributing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contributing.md b/contributing.md index 9265b0d..55c17dd 100644 --- a/contributing.md +++ b/contributing.md @@ -4,7 +4,7 @@ ### Checks -* [ ] I've made sure the lint is passing in this PR. +* [ ] I've made sure the the linter is passing in this PR. * [ ] I've made sure the tests are passing. Note that there might be a few flaky tests, in that case, please comment that they are not relevant. * [ ] Testing Strategy * [ ] Unit tests From b2d96e23d1c4e6195992dfcfff9833fabe99fad3 Mon Sep 17 00:00:00 2001 From: Maximilian Hubert <64627729+gap-editor@users.noreply.github.com> Date: Sat, 1 Feb 2025 15:08:27 +0100 Subject: [PATCH 4/4] typo mining-reward.md subject-verb agreement (the data chunks belong) --- docs/incentive-mechanism/mining-reward.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/incentive-mechanism/mining-reward.md b/docs/incentive-mechanism/mining-reward.md index c781d86..fac0a88 100644 --- a/docs/incentive-mechanism/mining-reward.md +++ b/docs/incentive-mechanism/mining-reward.md @@ -1,6 +1,6 @@ # Mining Reward -0G Storage creates pricing segments every 8 GB of data chunks over the data flow. Each pricing segment is associated with an Endowment Pool and a Reward Pool. The Endowment Pool collects the storage endowments of all the data chunks belongs to this pricing segment and releases a fixed ratio of balance to the Reward Pool every second. The rate of reward release is set to 4% per year. +0G Storage creates pricing segments every 8 GB of data chunks over the data flow. Each pricing segment is associated with an Endowment Pool and a Reward Pool. The Endowment Pool collects the storage endowments of all the data chunks belong to this pricing segment and releases a fixed ratio of balance to the Reward Pool every second. The rate of reward release is set to 4% per year. The mining reward is paid to miners for providing data service. Miners receive mining reward when submit the first legitimate PoRA for a mining epoch to 0G Storage contract.