You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently the transport and protocol execution logic for the signing and DKG protocols moved out of server and into a new crate entropy-protocol which is designed to be run both on the server and client side.
Because of fears about the difficulties with wasm, i moved only the bare minimum things needed on the client side. There are still modules in server which relate to protocol execution or transport but aren't needed on the client side.
Why is this issue relevant?
I think it makes sense to keep that stuff all together in one crate
What steps are required to resolve this?
I would move these modules into entropy-protocol but gate them behind the server feature flag so they are only compiled in 'server mode'.
Does this change the spec? HTTP, extrinsic, or storage? Is it breaking? Clearly describe the new interface.
No this should not break anything
The text was updated successfully, but these errors were encountered:
Recently the transport and protocol execution logic for the signing and DKG protocols moved out of
server
and into a new crateentropy-protocol
which is designed to be run both on the server and client side.Because of fears about the difficulties with wasm, i moved only the bare minimum things needed on the client side. There are still modules in
server
which relate to protocol execution or transport but aren't needed on the client side.Why is this issue relevant?
I think it makes sense to keep that stuff all together in one crate
What steps are required to resolve this?
I would move these modules into
entropy-protocol
but gate them behind theserver
feature flag so they are only compiled in 'server mode'.Does this change the spec? HTTP, extrinsic, or storage? Is it breaking? Clearly describe the new interface.
No this should not break anything
The text was updated successfully, but these errors were encountered: