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.

Sign up for GitHub

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

Jump to bottom

Variable size transactions #8

Open
amiller opened this issue May 26, 2017 · 0 comments
Open

Variable size transactions #8

amiller opened this issue May 26, 2017 · 0 comments
Labels
design-needed

Comments

@amiller
Copy link
Owner

amiller commented May 26, 2017

All benchmarking and efficiency analysis so far involves assuming transactions are constant size. In some applications transactions submitted by users may need to vary in size. For example, Ethereum transactions can provide data, Bitcoin transactions spend varying numbers of inputs.

The efficiency proof depends on assuming transactions can be randomly selected uniformly random. Does it hold if some transactions are large?
@amiller amiller mentioned this issue Jul 13, 2017
Open
majvan pushed a commit to majvan/HoneyBadgerBFT that referenced this issue Dec 15, 2021
@sbellem
Extract local compute phase of BA into a function
3de89bf 
Also handles case where BA value is not equal to coin

fixes amiller#8

Except for the blocking operation of getting the coin, the code that is
extracted into a function corresponds to phase 3 described in [MMR14];
lines 7-11 in fig. 2 (A BV-broadcast-based algorithm implementing binary
consensus ...).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
design-needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@amiller