Skip to content

⚡ Weak broadcast of data proposals in mempool #1547

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

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

hhalex
Copy link
Contributor

@hhalex hhalex commented Aug 22, 2025

Prepare balancing replication in Mempool

  • Reduce poda expectations to Weak certificate (f+1)
  • TODO: Poda should be stored (CreateOrUpdate), even with no data proposal, to avoid mem leak with buffering, to be able to put it in a cut

Next PR:

  • add possibility in SyncRequest/SyncReply to specifiy lane in request

@hhalex hhalex changed the title ⚡ Weak broadcast of data prosposals in mempool ⚡ Weak broadcast of data proposals in mempool Aug 22, 2025
Copy link

codecov bot commented Aug 22, 2025

Codecov Report

❌ Patch coverage is 81.92771% with 15 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
src/mempool/own_lane.rs 46.66% 8 Missing ⚠️
crates/contracts/staking/src/state.rs 86.00% 7 Missing ⚠️
Files with missing lines Coverage Δ
src/mempool.rs 87.42% <100.00%> (+5.25%) ⬆️
src/mempool/storage.rs 83.98% <100.00%> (+0.38%) ⬆️
crates/contracts/staking/src/state.rs 90.69% <86.00%> (-1.93%) ⬇️
src/mempool/own_lane.rs 77.94% <46.66%> (+0.26%) ⬆️

... and 4 files with indirect coverage changes

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

Successfully merging this pull request may close these issues.

1 participant