From 9b2611759e85ead5c2e83aa5497a4ef8e2cf0a4e Mon Sep 17 00:00:00 2001 From: sashass1315 Date: Sat, 30 Aug 2025 14:09:19 +0300 Subject: [PATCH 1/4] Update mining-reward.md --- 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 fac0a88..78a7d68 100644 --- a/docs/incentive-mechanism/mining-reward.md +++ b/docs/incentive-mechanism/mining-reward.md @@ -7,6 +7,6 @@ The mining reward is paid to miners for providing data service. Miners receive m The mining reward consists of two parts: * Base reward: the base reward, denoted by $$R_{base}$$, is paid for every accepted mining proof. The base reward per proof decreases over time. -* Storage reward: the storage reward, denoted by $$R_{storage}$$, is the perpetual reward from storing data. When a PoRA falls in a pricing segment, half of the balance in its Reward Pool are claimed as the storage reward. +* Storage reward: the storage reward, denoted by $$R_{storage}$$, is the perpetual reward from storing data. When a PoRA falls in a pricing segment, half of the balance in its Reward Pool is claimed as the storage reward. The total reward for a new mining proof is thus: $$R_{total} = R_{base} + R_{storage}$$ From 3545c97c043dba1cf638416f40e54d2fba6d3209 Mon Sep 17 00:00:00 2001 From: sashass1315 Date: Sat, 30 Aug 2025 14:12:44 +0300 Subject: [PATCH 2/4] Update proof-of-random-access.md --- 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 c10d81f..b83ea9f 100644 --- a/docs/incentive-mechanism/proof-of-random-access.md +++ b/docs/incentive-mechanism/proof-of-random-access.md @@ -1,6 +1,6 @@ # Proof of Random Access -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. +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 compute 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, which consists of the chosen random nonce, the loaded data chunk and the proof for the correctness of data chunk to the mining contract. From 032e7d1f43bac00fb4fc64125d8c8dfd69756727 Mon Sep 17 00:00:00 2001 From: sashass1315 Date: Sat, 30 Aug 2025 14:15:18 +0300 Subject: [PATCH 3/4] Update architecture.md --- docs/architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/architecture.md b/docs/architecture.md index 3897fff..9bbcc22 100644 --- a/docs/architecture.md +++ b/docs/architecture.md @@ -22,4 +22,4 @@ On top of the log layer, 0G Storage provides a Key-Value store runtime to manage ## Dependencies -The 0G Storage Node is depended by the [0G Storage KV](https://github.com/0glabs/0g-storage-kv). 0G Storage KV is essentially a wrapper layer on top of 0G Storage Node in order to provide mutable KV Store and transaction processing to applications. 0G DA uses the KV Store to store metadata of the data blobs. +The 0G Storage Node is depended on the [0G Storage KV](https://github.com/0glabs/0g-storage-kv). 0G Storage KV is essentially a wrapper layer on top of 0G Storage Node in order to provide mutable KV Store and transaction processing to applications. 0G DA uses the KV Store to store metadata of the data blobs. From ab5ab9621ca5a125d7c3d0e99a9c754ea0d29ba9 Mon Sep 17 00:00:00 2001 From: sashass1315 Date: Thu, 4 Sep 2025 20:21:10 +0300 Subject: [PATCH 4/4] Update architecture.md --- docs/architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/architecture.md b/docs/architecture.md index 9bbcc22..3897fff 100644 --- a/docs/architecture.md +++ b/docs/architecture.md @@ -22,4 +22,4 @@ On top of the log layer, 0G Storage provides a Key-Value store runtime to manage ## Dependencies -The 0G Storage Node is depended on the [0G Storage KV](https://github.com/0glabs/0g-storage-kv). 0G Storage KV is essentially a wrapper layer on top of 0G Storage Node in order to provide mutable KV Store and transaction processing to applications. 0G DA uses the KV Store to store metadata of the data blobs. +The 0G Storage Node is depended by the [0G Storage KV](https://github.com/0glabs/0g-storage-kv). 0G Storage KV is essentially a wrapper layer on top of 0G Storage Node in order to provide mutable KV Store and transaction processing to applications. 0G DA uses the KV Store to store metadata of the data blobs.