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

How to get jito uuid #639

Open
cnstephen opened this issue Jul 28, 2024 · 0 comments
Open

How to get jito uuid #639

cnstephen opened this issue Jul 28, 2024 · 0 comments

Comments

@cnstephen
Copy link

How to get jito uuid
GXKe pushed a commit to GXKe/jito-solana that referenced this issue Aug 14, 2024
@mergify @behzadnouri @yihau
v1.18: pads last erasure batch with empty data shreds (backport of ji…
9d8d5f3 
…to-foundation#639) (#927)

* pads last erasure batch with empty data shreds (jito-foundation#639)

For duplicate blocks prevention we want to verify that the last erasure
batch was sufficiently propagated through turbine. This requires
additional bookkeeping because, depending on the erasure coding schema,
the entire batch might be recovered from only a few coding shreds.

In order to simplify above, this commit instead ensures that the last
erasure batch has >= 32 data shreds so that the batch cannot be
recovered unless 32+ shreds are received from turbine or repair.

(cherry picked from commit 293414f)

# Conflicts:
#	core/src/repair/repair_service.rs

* resolves merge conflicts

---------

Co-authored-by: behzad nouri <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cnstephen