Skip to content

Extract MPC into a separate crate#487

Open
zhouwfang wants to merge 1 commit intomainfrom
zhoufang/iop-291-extract-mpc-into-a-separate-crate
Open

Extract MPC into a separate crate#487
zhouwfang wants to merge 1 commit intomainfrom
zhoufang/iop-291-extract-mpc-into-a-separate-crate

Conversation

@zhouwfang
Copy link
Copy Markdown
Contributor

#16

@zhouwfang zhouwfang requested a review from bmwill as a code owner April 24, 2026 22:13
@zhouwfang zhouwfang changed the title Extract mpc into a separate crate Extract MPC into a separate crate Apr 24, 2026
@zhouwfang zhouwfang force-pushed the zhoufang/iop-291-extract-mpc-into-a-separate-crate branch from e63d2fc to e40c098 Compare April 24, 2026 22:19
@zhouwfang zhouwfang force-pushed the zhoufang/iop-291-extract-mpc-into-a-separate-crate branch from e40c098 to a680ff8 Compare April 24, 2026 22:35
@zhouwfang zhouwfang requested review from benr-ml and jonas-lj and removed request for benr-ml and jonas-lj April 24, 2026 22:38
@bmwill
Copy link
Copy Markdown
Contributor

bmwill commented Apr 27, 2026

Whats the main motivation for this? our code shouldn't be big enough yet to really warrant splitting this yet to get a perf bump

@zhouwfang
Copy link
Copy Markdown
Contributor Author

Whats the main motivation for this? our code shouldn't be big enough yet to really warrant splitting this yet to get a perf bump

Not perf, layering for code health. It makes the 3 fields in Hashi struct owned by MpcServiceState in the new crate, and Hashi delegates. So Hashi becomes a consumer of an MPC library rather than the owner of MPC internals. State changes become local to the mpc crate instead of touching Hashi.

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.

2 participants