OptionaloriginalError: ErrorOptionaldetails: Record<string, unknown>Optional ReadonlycauseOptional ReadonlydataOptional structured data attached to the failure (e.g. on-chain receipt).
Optional ReadonlyexpectedHow many messages/parties the wait expected.
Optional ReadonlymissingParties that had not responded when the wait expired, when known.
ReadonlyphaseWhich stage ran out of time — see CeremonyTimeoutPhase.
Optional ReadonlyreceivedHow many had actually arrived when the wait expired.
Optional ReadonlysessionThe relay session the ceremony was running in, when known.
OptionalstackOptional ReadonlywaitedHow long the timed-out wait ran before giving up.
Optional ReadonlywaitingThe signer-sdk's own label for the expired wait (e.g. 'partyCount', 'protocolMessage').
Thrown when a ceremony (account creation, transaction signing, or message signing) fails because a protocol wait expired.
No timeout is retryable in place. A ceremony whose parties have gone silent cannot be resumed — recovery always means a fresh ceremony (a new
submitTx/createAccount/... call), never re-joining the same session.The error carries the signer-sdk's structured diagnostics: check phase and missingPeerIds to tell "a co-signer never joined" apart from "a joined peer dropped mid-ceremony". The full diagnostic payload (relay party snapshots, socket connectivity, quiet time) is preserved on the inherited SaltCeremonyError.data field — include it in support reports.
Example: Handling a timed-out transaction