Expand description
Session lifecycle: create, round, result, destroy.
A Session owns the per-party state of one threshold protocol
run. The framework drives it round-by-round: feed in the messages
received from peers, get back the messages to send, repeat until a
round signals complete, then read the Session::result.
The session delegates all scheme-specific work to a SessionImpl
produced by the registered crate::registry::TcScheme. The
framework layer above this is transport-agnostic — see
TODO.roadmap/05-networking-primitives.md for how crate::message::Messages
get moved between parties.
Structs§
- Session
- One party’s view of one threshold protocol run.
- Session
Params - Parameters handed to
Session::create.