walletSwapFaultExecuteTimeout property

String get walletSwapFaultExecuteTimeout

IntoZec execute overran the host-side timeout (#367, F5): the cause may be transport OR a local stall (a busy store consuming most of the window), so this HEDGES both — unlike walletSwapFaultConnection, it must not firmly blame the user's connection. Money-safe: an IntoZec execute moves no wallet funds; re-quoting is the remedy.

In en, this message translates to: 'The swap couldn't start in time — the connection may be slow, or the wallet was busy. Get a new quote and try again.'

Implementation

String get walletSwapFaultExecuteTimeout;