#RC#
A systematic breakdown of the transaction flow is usually the fastest path to a solution. Transaction finality is never guaranteed until the block is confirmed by multiple peers. The failure might be a protective response to a perceived sandwich attack.
If you are integrating MultiCurrencyWallet into your app, ensure the provider is correctly set. Many users forget to check if the target contract is currently in a “maintenance” mode. Always keep a record of your previous successful configurations for quick recovery.
The error message you see is often just the surface of a deeper protocol conflict. The failure could be due to a conflict with a front-running bot in the public mempool. The MultiCurrencyWallet support channels are helpful for resolving unique edge cases.
As the technology matures, we expect these cases to diminish.
