Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redundant transactions in blocks in the same layer #23

Open
lrettig opened this issue Feb 5, 2020 · 1 comment
Open

Redundant transactions in blocks in the same layer #23

lrettig opened this issue Feb 5, 2020 · 1 comment

Comments

@lrettig
Copy link
Member

lrettig commented Feb 5, 2020

Following on our conversation in this thread:

barakshani
we get redundancy, but how much would depend on the number of transactions waiting in the mempool. Given the number of (average) blocks in a layer and the limit of transaction per block (so basically given the limit of transactions in a layer), there is some number of transactions in the mempool for which we don't expect to get duplications at all (if the limit of transactions in a layer is n, then once there are roughly n^2 transactions in the mempool, we expect no duplications)

@barakshani what happens when there is < n transactions in the mempool? Don't all of the blocks in a layer basically contain the same set of transactions then? Nothing would break, but it just seems like a lot of redundant data storage doesn't it?

@barakshani
Copy link

yes. correct. we may have dynamic tx selection, so miners won't feel there entire block with all the txs (just because of this redundancy)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants