-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Shreds are always zero-padded #8909
Labels
stale
[bot only] Added to stale content; results in auto-close after a week.
Milestone
Comments
Closed
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
stale
bot
added
the
stale
[bot only] Added to stale content; results in auto-close after a week.
label
Apr 19, 2021
Fixed by #16602 |
This was referenced Jun 6, 2023
Open
This was referenced Jun 6, 2023
Open
This was referenced Jun 7, 2023
This was referenced Jun 8, 2023
This was referenced Jun 9, 2023
This was referenced Sep 29, 2023
Open
Open
Open
Open
Open
Open
This was referenced Oct 6, 2023
Open
Open
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
Shreds are always zero padded to 1320 bytes even if the payload is less than that. This is most likely a cause of 3x bandwidth and storage requirements than necessary on an idle network.
Proposed Solution
Only transmit and store the used part of the shred.
The text was updated successfully, but these errors were encountered: