From a77469446f3781b629476839da303be8f68140e1 Mon Sep 17 00:00:00 2001 From: nizzle Date: Wed, 23 Oct 2024 11:07:36 +0500 Subject: [PATCH 01/10] A proposal to reward rollup operators for submitting BLOB data to L1 --- EIPS/BLOB Data and Rollup Operator Rewards.md | 48 +++++++++++++++++++ 1 file changed, 48 insertions(+) create mode 100644 EIPS/BLOB Data and Rollup Operator Rewards.md diff --git a/EIPS/BLOB Data and Rollup Operator Rewards.md b/EIPS/BLOB Data and Rollup Operator Rewards.md new file mode 100644 index 0000000000000..ec3169bb54fce --- /dev/null +++ b/EIPS/BLOB Data and Rollup Operator Rewards.md @@ -0,0 +1,48 @@ +--- +title: +description: +author: +discussions-to: +status: Draft +type: +category: # Only required for Standards Track. Otherwise, remove this field. +created: <2024-10-23> +requires: # Only required when you reference an EIP in the `Specification` section. Otherwise, remove this field. +--- + +## Abstract + +This proposal designs a system that rewards rollup operators for using BLOB data and DATA TX. The goal is to allow rollup operators to submit data processed on Layer 2 (L2) to Layer 1 (L1) and receive economic incentives, thereby improving the network's scalability and efficiency. + +## Motivation + +Rollups play an important role in improving Ethereum's scalability, but there is currently no clear reward mechanism for rollup operators. This proposal suggests using BLOB data and DATA TX to create a reward system for rollup operators, aiming to promote network activation and mitigate the centralization issue in Ethereum staking. By providing rewards based on L2 consensus, this system can encourage more participants and strengthen decentralization. + +## Specification + +1. BLOB Data Usage: Rollup operators store large-scale data in BLOB space and submit it to L1 for verification. +2. Reward Mechanism: Once the data is successfully submitted and verified, rollup operators are rewarded with L1 coins (ETH). +3. DATA TX: The transaction that transfers the data is processed by the rollup protocol, and the result is reflected in L1, where the final reward is granted. + +The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 and RFC 8174. + +## Rationale + +Rollup operators handle many transactions and large amounts of data, supporting the scalability and stability of the network. By providing a clear reward system for operators processing large-scale data using BLOBs, more participation can be encouraged, promoting the decentralization of the Ethereum network. This will allow the network to handle larger transaction volumes and maximize efficiency. + +TBD + +## Backwards Compatibility + +BLOB data, introduced through EIP-4844, is a new method for efficiently storing large-scale data. This proposal aims to extend that system by providing rewards to rollup operators, thereby enhancing network performance. By facilitating efficient data processing and rewards between L1 and L2, the proposal seeks to improve the network’s scalability and efficiency. +No backward compatibility issues found. + +## Security Considerations + +The reward mechanism must be based on accurate verification, with clear rules to prevent fraudulent activity. Rollup operators submitting incorrect data should not receive rewards, and the reliability and accuracy of the data must be ensured. + +Needs discussion. + +## Copyright + +Copyright and related rights waived via [CC0](../LICENSE.md). From 9c7a1c062186d58da424dc23001657d59f9af09c Mon Sep 17 00:00:00 2001 From: nizzle Date: Wed, 23 Oct 2024 11:17:02 +0500 Subject: [PATCH 02/10] filename change --- ...LOB Data and Rollup Operator Rewards.md => eip-blob-rollup.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename EIPS/{BLOB Data and Rollup Operator Rewards.md => eip-blob-rollup.md} (100%) diff --git a/EIPS/BLOB Data and Rollup Operator Rewards.md b/EIPS/eip-blob-rollup.md similarity index 100% rename from EIPS/BLOB Data and Rollup Operator Rewards.md rename to EIPS/eip-blob-rollup.md From e053fe7d7cfb1872f5e7be8f7b27a74157f40750 Mon Sep 17 00:00:00 2001 From: nizzle Date: Wed, 23 Oct 2024 12:36:10 +0500 Subject: [PATCH 03/10] filename change --- ...p-blob-rollup.md => eip-draft-blob-rollup-reward.md.md} | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) rename EIPS/{eip-blob-rollup.md => eip-draft-blob-rollup-reward.md.md} (90%) diff --git a/EIPS/eip-blob-rollup.md b/EIPS/eip-draft-blob-rollup-reward.md.md similarity index 90% rename from EIPS/eip-blob-rollup.md rename to EIPS/eip-draft-blob-rollup-reward.md.md index ec3169bb54fce..9e78630b93b49 100644 --- a/EIPS/eip-blob-rollup.md +++ b/EIPS/eip-draft-blob-rollup-reward.md.md @@ -1,13 +1,12 @@ --- title: description: -author: -discussions-to: +author: +discussions-to: status: Draft type: -category: # Only required for Standards Track. Otherwise, remove this field. +category: created: <2024-10-23> -requires: # Only required when you reference an EIP in the `Specification` section. Otherwise, remove this field. --- ## Abstract From ce00dab2303f4fc30d58e4f296e71fdebcfb949c Mon Sep 17 00:00:00 2001 From: nizzle Date: Wed, 23 Oct 2024 12:39:52 +0500 Subject: [PATCH 04/10] filename change --- EIPS/{eip-draft-blob-rollup-reward.md.md => eip-7570.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename EIPS/{eip-draft-blob-rollup-reward.md.md => eip-7570.md} (100%) diff --git a/EIPS/eip-draft-blob-rollup-reward.md.md b/EIPS/eip-7570.md similarity index 100% rename from EIPS/eip-draft-blob-rollup-reward.md.md rename to EIPS/eip-7570.md From 8c704cc002b5744842652cefa51b103de79b361d Mon Sep 17 00:00:00 2001 From: nizzle Date: Wed, 23 Oct 2024 12:44:57 +0500 Subject: [PATCH 05/10] changes --- EIPS/eip-7570.md | 21 +++++++++++---------- 1 file changed, 11 insertions(+), 10 deletions(-) diff --git a/EIPS/eip-7570.md b/EIPS/eip-7570.md index 9e78630b93b49..22e4cb10ca7a2 100644 --- a/EIPS/eip-7570.md +++ b/EIPS/eip-7570.md @@ -1,12 +1,13 @@ --- -title: -description: -author: -discussions-to: +eip: 7570 +title: BLOB Data and Rollup Operator Rewards +description: A proposal to reward rollup operators for submitting BLOB data to L1. +author: Ryo Ha (@sopia19910) , Khajiev Nizomjon (@khajievN) , Seongsu Kim (@munak) +discussions-to: https://ethereum-magicians.org/t/7570 status: Draft -type: -category: -created: <2024-10-23> +type: Standards Track +category: Core +created: 2024-10-23 --- ## Abstract @@ -19,9 +20,9 @@ Rollups play an important role in improving Ethereum's scalability, but there is ## Specification -1. BLOB Data Usage: Rollup operators store large-scale data in BLOB space and submit it to L1 for verification. -2. Reward Mechanism: Once the data is successfully submitted and verified, rollup operators are rewarded with L1 coins (ETH). -3. DATA TX: The transaction that transfers the data is processed by the rollup protocol, and the result is reflected in L1, where the final reward is granted. +1. **BLOB Data Usage**: Rollup operators store large-scale data in BLOB space and submit it to L1 for verification. +2. **Reward Mechanism**: Once the data is successfully submitted and verified, rollup operators are rewarded with L1 coins (ETH). +3. **DATA TX**: The transaction that transfers the data is processed by the rollup protocol, and the result is reflected in L1, where the final reward is granted. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 and RFC 8174. From b991a190924a83a3e3ba8c2de88780f74e894b71 Mon Sep 17 00:00:00 2001 From: nizzle Date: Wed, 23 Oct 2024 12:55:21 +0500 Subject: [PATCH 06/10] changes --- EIPS/eip-7570.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/EIPS/eip-7570.md b/EIPS/eip-7570.md index 22e4cb10ca7a2..7f51b6a8ba3f5 100644 --- a/EIPS/eip-7570.md +++ b/EIPS/eip-7570.md @@ -3,7 +3,7 @@ eip: 7570 title: BLOB Data and Rollup Operator Rewards description: A proposal to reward rollup operators for submitting BLOB data to L1. author: Ryo Ha (@sopia19910) , Khajiev Nizomjon (@khajievN) , Seongsu Kim (@munak) -discussions-to: https://ethereum-magicians.org/t/7570 +discussions-to: https://ethereum-magicians.org/t/blob-data-and-rollup-operator-rewards/21446?u=sopia19910 status: Draft type: Standards Track category: Core @@ -34,7 +34,7 @@ TBD ## Backwards Compatibility -BLOB data, introduced through EIP-4844, is a new method for efficiently storing large-scale data. This proposal aims to extend that system by providing rewards to rollup operators, thereby enhancing network performance. By facilitating efficient data processing and rewards between L1 and L2, the proposal seeks to improve the network’s scalability and efficiency. +[BLOB data](./eip-4844), introduced through EIP-4844, is a new method for efficiently storing large-scale data. This proposal aims to extend that system by providing rewards to rollup operators, thereby enhancing network performance. By facilitating efficient data processing and rewards between L1 and L2, the proposal seeks to improve the network’s scalability and efficiency. No backward compatibility issues found. ## Security Considerations From cf149df1bf9a4800cf2b900bbd95ed735ac43c42 Mon Sep 17 00:00:00 2001 From: nizzle Date: Wed, 23 Oct 2024 12:57:00 +0500 Subject: [PATCH 07/10] changes --- EIPS/eip-7570.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/EIPS/eip-7570.md b/EIPS/eip-7570.md index 7f51b6a8ba3f5..8b506dce43eaa 100644 --- a/EIPS/eip-7570.md +++ b/EIPS/eip-7570.md @@ -3,7 +3,7 @@ eip: 7570 title: BLOB Data and Rollup Operator Rewards description: A proposal to reward rollup operators for submitting BLOB data to L1. author: Ryo Ha (@sopia19910) , Khajiev Nizomjon (@khajievN) , Seongsu Kim (@munak) -discussions-to: https://ethereum-magicians.org/t/blob-data-and-rollup-operator-rewards/21446?u=sopia19910 +discussions-to: https://ethereum-magicians.org/t/blob-data-and-rollup-operator-rewards/21446 status: Draft type: Standards Track category: Core @@ -34,7 +34,7 @@ TBD ## Backwards Compatibility -[BLOB data](./eip-4844), introduced through EIP-4844, is a new method for efficiently storing large-scale data. This proposal aims to extend that system by providing rewards to rollup operators, thereby enhancing network performance. By facilitating efficient data processing and rewards between L1 and L2, the proposal seeks to improve the network’s scalability and efficiency. +[BLOB data](./eip-4844), is a new method for efficiently storing large-scale data. This proposal aims to extend that system by providing rewards to rollup operators, thereby enhancing network performance. By facilitating efficient data processing and rewards between L1 and L2, the proposal seeks to improve the network’s scalability and efficiency. No backward compatibility issues found. ## Security Considerations From 6c0ecba6f92e8b39c3dfa051feaa096bb083dca7 Mon Sep 17 00:00:00 2001 From: Khajiev Nizomjon Date: Thu, 24 Oct 2024 07:32:24 +0500 Subject: [PATCH 08/10] Update EIPS/eip-7570.md Co-authored-by: Andrew B Coathup <28278242+abcoathup@users.noreply.github.com> --- EIPS/eip-7570.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-7570.md b/EIPS/eip-7570.md index 8b506dce43eaa..9776e8f23b28f 100644 --- a/EIPS/eip-7570.md +++ b/EIPS/eip-7570.md @@ -1,5 +1,5 @@ --- -eip: 7570 +eip: to be assigned title: BLOB Data and Rollup Operator Rewards description: A proposal to reward rollup operators for submitting BLOB data to L1. author: Ryo Ha (@sopia19910) , Khajiev Nizomjon (@khajievN) , Seongsu Kim (@munak) From dbbf9173595ce3dc5c749491faf9165be0bc7965 Mon Sep 17 00:00:00 2001 From: nizzle Date: Sat, 26 Oct 2024 05:08:24 +0500 Subject: [PATCH 09/10] filename change --- EIPS/{eip-7570.md => eip-to be assigned.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename EIPS/{eip-7570.md => eip-to be assigned.md} (100%) diff --git a/EIPS/eip-7570.md b/EIPS/eip-to be assigned.md similarity index 100% rename from EIPS/eip-7570.md rename to EIPS/eip-to be assigned.md From 08a42691d1bc65d097494a203ebfa755bb126ae3 Mon Sep 17 00:00:00 2001 From: nizzle Date: Sat, 26 Oct 2024 05:10:45 +0500 Subject: [PATCH 10/10] filename change --- EIPS/{eip-to be assigned.md => eip-00000.md} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename EIPS/{eip-to be assigned.md => eip-00000.md} (99%) diff --git a/EIPS/eip-to be assigned.md b/EIPS/eip-00000.md similarity index 99% rename from EIPS/eip-to be assigned.md rename to EIPS/eip-00000.md index 9776e8f23b28f..b53f91dd1bd15 100644 --- a/EIPS/eip-to be assigned.md +++ b/EIPS/eip-00000.md @@ -1,5 +1,5 @@ --- -eip: to be assigned +eip: 00000 title: BLOB Data and Rollup Operator Rewards description: A proposal to reward rollup operators for submitting BLOB data to L1. author: Ryo Ha (@sopia19910) , Khajiev Nizomjon (@khajievN) , Seongsu Kim (@munak)