-
Notifications
You must be signed in to change notification settings - Fork 3
Add 5-party networking and PRF key setup to ampc-actor-utils #142
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
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we potentially avoid duplication from adding this if we just add send_to(role) and recv_from(role) in the existing ControlChannel trait?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is what Claude had to say:
send_next/recv_prevcompile fine but always fail at runtime — exactly the kind of latent failure your engineering rules say to avoid. With separate traits, calling ring methods on a mesh channel is a compile error, not a production incident.ControlChannelis implemented outside this crate —iris-mpc-cpu's checkpoint protocol has its ownInMemoryRingimplementation of the trait iniris-mpc/iris-mpc-cpu/src/checkpoint_protocol/transport.rs. Adding required methods toControlChannelbreaks that implementation the momentiris-mpcbumps its pinned rev; adding them as defaulted methods that return errors just reintroduces the hidden-failure problem in every existing implementor.sync()on the ring is a 3-party barrier over two streams; on the mesh it's an all-to-all barrier over N−1 streams with deterministic role ordering. And "next"/"prev" have no canonical meaning in a mesh — a merged trait would force every caller to know which subset of the API is live for the object they hold.ControlChannel, N-party code holds aMeshControlChannel, andNetworkHandlehands out whichever one the caller asks for.The 2nd and 3rd point convince me it's technically easier to keep the separate trait for now.
And this applies only to the control channel. This is different from the channels they use for data during the MPC protocol, which are non-blocking channels already in a mesh configuration.