Skip to content

SIP: block streaming #51

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
Open
mwtian wants to merge 1 commit into
base: main
Choose a base branch
from
Open

SIP: block streaming #51

mwtian wants to merge 1 commit into from

Conversation

@mwtian
Copy link
Contributor

@mwtian mwtian commented Mar 3, 2025

No description provided.

@luispdm
Copy link

luispdm commented Aug 25, 2025 •
edited
Loading

Hi 👋
Any updates on this one?

@mwtian
Copy link
Contributor Author

mwtian commented Aug 26, 2025

Hi @luispdm, since there is no objection, hopefully this proposal can get merged soon. There is a plan to invest more time into the design and implementation in 1-2 months.

luispdm
luispdm reviewed Aug 27, 2025
View reviewed changes
sips/sip-block-streaming.md

Currently Sui has 320-350ms p50 consensus latency and sub 700ms p50 e2e transaction settlement latency. But it can take longer for non validators to receive the latest transactions. The diagram below illustrates the common case:

![transaction_propagation](../assets/sip-block-streaming/transaction_propagation.png)
Copy link

@luispdm luispdm Aug 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The link to the image is broken, it should be changed to: assets/sip-block-streaming/txn_propagation.png

@LoboSolitario
Copy link

LoboSolitario commented Sep 8, 2025

GM GM
In the proposed SIP, it is mentioned that one validator will be directly connected to one state sync full node. This validator will be publishing all its consensus data to the SSFN. But will this also include all the global transactions or just the local txs that are being processed by that validator?
And did I understand it correctly that there will be a one-to-one connection between the validator and SSFN, and other subscribers or full nodes need to connect to that SSFN to get the relevant consensus data?

@mwtian
Copy link
Contributor Author

mwtian commented Sep 8, 2025

Validators are forwarding all consensus blocks, which will contain all transactions in the system. Each SSFN connects to a validator unless it disconnects. But a validator can connect to one or more SSFNs.

@mwtian
Copy link
Contributor Author

mwtian commented Oct 7, 2025 •
edited
Loading

Planning to make some minor updates here. We are starting to build an experimental implementation for this.

zihehuang
zihehuang approved these changes Oct 7, 2025
View reviewed changes
Copy link
Collaborator

@zihehuang zihehuang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving this since the experimental implementation is already in development

@luispdm
Copy link

luispdm commented Oct 8, 2025

Thanks for the update. Do you mind sharing a link to the repo/branch where the development is being done @mwtian? Thank you.

@Cvijan4PointO
Copy link

Cvijan4PointO commented Nov 24, 2025

Do we have any updates on this? Would be nice to see this live.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@zihehuang zihehuang zihehuang approved these changes

+1 more reviewer

@luispdm luispdm luispdm left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@mwtian @luispdm @LoboSolitario @Cvijan4PointO @zihehuang