Add EIP: BLOB Data and Rollup Operator Rewards

[khajievN]

ATTENTION: ERC-RELATED PULL REQUESTS NOW OCCUR IN ETHEREUM/ERCS

--

When opening a pull request to submit a new EIP, please use the suggested template: https://github.com/ethereum/EIPs/blob/master/eip-template.md

We have a GitHub bot that automatically merges some PRs. It will merge yours immediately if certain criteria are met:

• The PR edits only existing draft PRs.
• The build passes.
• Your GitHub username or email address is listed in the 'author' header of all affected PRs, inside .
• If matching on email address, the email address is the one publicly listed on your GitHub profile.

[eth-bot]

File EIPS/eip-00000.md

Requires 1 more reviewers from @axic, @g11tech, @gcolvin, @lightclient, @SamWilsn

[nerolation]

This is spam.

[abcoathup]

This doesn't appear to be an EIP (in its current form)

Rollups are already using blobs, with the incentive that it is generally cheaper than calldata: https://www.growthepie.xyz/economics

[sopia19910]

Hello,

Ethereum has adopted layer technology, where L2 is connected to the Ethereum blockchain with finality at lower fees. This means that L2 blocks are also recognized as part of the Ethereum blockchain.

In other words, Layer 2 is part of the Ethereum blockchain, and I believe that this scalability should extend not only to blocks but also to validators and the reward system. However, the current focus is solely on block expansion, which has led to the perception that Ethereum is becoming centralized.

Therefore, I believe that if the validator and reward systems are also expanded, Ethereum would not be considered centralized.

To address this issue, our team has made a proposal, and we plan to continue suggesting specific code modifications to support this.

To clarify what we are proposing: ultimately, we are suggesting not just providing rewards to operators who perform rollups, but also creating a system where the consensus algorithm of L2 chains interacts with L1 and receives rewards based on that interaction. We will further elaborate on this in more detail.

[github-actions]

The commit dbbf917 (as a parent of dd6f693) contains errors.
Please inspect the Run Summary for details.