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

Bin txs into shreds without breaking them #18956

Open
behzadnouri opened this issue Jul 29, 2021 · 2 comments
Open

Bin txs into shreds without breaking them #18956

behzadnouri opened this issue Jul 29, 2021 · 2 comments
Labels
do-not-close Add this tag to exempt an issue/PR from being closed by the stalebot

Comments

@behzadnouri
Copy link
Contributor

So that the receiver can do sig-verify out of order.

  • Need to confirm metadata/header would not tip the size over MTU limit for current mainnet txs.
  • Figure out how to maintain forward/backward compatibility at switching point across cluster.

https://discord.com/channels/428295358100013066/478692221441409024/822602147199582229
https://discord.com/channels/428295358100013066/478692221441409024/870088483388137482

we can change the format of the shred to be a list of full TXs
with some metadata on entry and order in that entry if we need to bin them out of order for efficiency

we might have to quietly lower the size and hope no one currently running is impacted
at some point, we should add stored TXs where users can upload a bigger tx into an account and execute it
that would also let VMs continue large computations

Also for reference: #17102

@aeyakovenko
Copy link
Member

It's effective even if it's not done for 100% of the TXs. so the few that trip the MTU size header can be split.

@steviez
Copy link
Contributor

steviez commented Jul 29, 2021

Think this one and #16403 have similar intentions

@github-actions github-actions bot added the stale [bot only] Added to stale content; results in auto-close after a week. label Dec 27, 2022
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 3, 2023
@behzadnouri behzadnouri removed the stale [bot only] Added to stale content; results in auto-close after a week. label Jan 3, 2023
@behzadnouri behzadnouri reopened this Jan 3, 2023
@github-actions github-actions bot added the stale [bot only] Added to stale content; results in auto-close after a week. label Jan 4, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 11, 2024
@behzadnouri behzadnouri added do-not-close Add this tag to exempt an issue/PR from being closed by the stalebot and removed stale [bot only] Added to stale content; results in auto-close after a week. labels Jan 12, 2024
@behzadnouri behzadnouri reopened this Jan 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-close Add this tag to exempt an issue/PR from being closed by the stalebot
Projects
None yet
Development

No branches or pull requests

3 participants