Crate stoffel_mpc_coordinator_off_chain

Modules§

AssignedMaskReservation
AssignedMaskShare
AssignedMaskedInputEvent
CoordinatorRPCServerConnectionBase: The basic server-side information for one client connection to the coordinator RPC interface. Can be extended by the developer.
CoordinatorRPCServerSharedBase: The basic internal state of the coordinator RPC server. Can be extended by the developer.
ExecutionRegistration: Immutable data that binds one invocation to its program and client I/O layout.
InputAssignment
InputClientRange: One client’s contiguous block of global input slots. A client’s own inputs are always numbered 0..count (see every InputAssignment producer), so the wire format only needs one entry per client rather than one per input: register_execution’s global slot index i falls in the range starting at the sum of every earlier range’s count, with per-client label i - that_start. Expanded into one InputSlotAssignment per slot on receipt (see CoordinatorExecutionState::new) — that expansion only costs memory, not JSON bytes.
InputSlotAssignment: One global input slot, expanded from an InputClientRange. Not sent over the wire — see InputAssignment for why.
OffChainCoordinatorClient
OffChainCoordinatorServer: The exterior wrapper of the server-side coordinator.
OneOffShutdownConfig

CoordinatorRPCBaseError: Errors returned to RPC clients by the basic coordinator RPC interface.
Event: Events that mimic those used for the on-chain coordinator.

DEFAULT_MAX_CONCURRENT_EXECUTIONS: A deliberately small, explicit bound for the number of live executions owned by one RPC listener. Finished executions must be retired before this many more are registered.
DEFAULT_MAX_RETIRED_EXECUTIONS: How many sealed-but-not-unanimously-acknowledged executions are remembered. A sealed execution holds no protocol state, so this only has to be large enough that a slow but honest party can still acknowledge its own executions after the quorum sealed them.
DEFAULT_ONE_OFF_SHUTDOWN_GRACE: How long a one-off coordinator waits for parties to acknowledge the terminal round after the designated party requests shutdown. Unanimous acknowledgement closes immediately; the bound preserves liveness when a faulty party never acknowledges.

CoordinatorRPCBaseClient: Client implementation for the CoordinatorRPCBase RPC API.
CoordinatorRPCBaseServer: Server trait implementation for the CoordinatorRPCBase RPC API.
StoffelCoordinatorRPCClient: Client implementation for the StoffelCoordinatorRPC RPC API.
StoffelCoordinatorRPCServer: Server trait implementation for the StoffelCoordinatorRPC RPC API.

ClientIdentity: An MPC client interacts with two types of entities: the coordinator and nodes. Towards the nodes, the MPC client uses a public key (currently ECDSA). Towards the coordinator, it uses either an Ethereum address (on-chain) or the same public key as for the nodes (off-chain).