Skip to main content

Module error

Module error 

Source
Expand description

Error types shared between the client and its modules Error types shared between the client and its modules.

The client implements the traits in crate::module and crate for its modules, so the failures those traits report have to be nameable from both sides; they live here rather than in fedimint-client, which the modules do not depend on.

Structs§

ApiVersionDiscoveryError
The client and the federation’s peers share no core API version.
InsufficientBalanceError
The primary module cannot fund a transaction: the balance it holds is below what the transaction needs.
OperationAlreadyExistsError
An operation with the same id already exists in the operation log.
OperationNotFoundError
No operation with the requested id exists in the operation log.

Enums§

AddStateMachinesError
A failure to add state machines to the client’s executor.
MetaFetchError
A failure to fetch the federation’s meta fields.
ModuleLookupError
A failure to find a module able to serve a request.
OperationLookupError
A failure to look up one of a module’s own operations.
TransactionSubmitError
A failure to build, submit or complete a client transaction.