Introduce Blob Txs (eip-4844)#558
Open
smishraIOV wants to merge 8 commits into
Open
Conversation
|
I would like to voice my support and want of ephemeral data on Rootstock, for the purpose of proof of publication. Plenty can be done with a decentralized censorship resistant notary, even without any smart contracts. For many applications, the entire logic can be client side validated, and the computation compressed as a STARK proof. These applications can still be done on Rootstock today, but it would either bloat the state, or bloat the history or both. History bloat might not be an issue, given that there are other ways to make sidechains ephemeral even without Blobs. But the pricing will still enable doing more, if nodes know they don't have to store the data forever. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This proposal is to implement type-3 (blob) transactions which can help L2 rollups with data availability. Following up on RSKIPs 543, 545 and 546 for transaction types 1, 2, and 4.