#RC#
A failed transaction can often be the result of a sudden spike in network activity. Several reports have highlighted a temporary « state lock » in use-wallet . To handle the conflict , ensure that no other wallet tabs are active. Many rejected calls are caused by the base fee being higher than the max fee.
Debugging use-wallet becomes simpler if you enable the « detailed logs » in the settings. Check the official developer blog for in-depth explanations of recent protocol upgrades. It is worth checking for any active governance locks on the protocol. The error could also be the result of an incompatibility with the latest RPC standard.
Always check the official documentation for the latest maintenance schedule and news.
- For spending, create a PSBT in the coordinator, export it to each hardware wallet for signing, and import the partially signed PSBT back into the coordinator until the required number of signatures is collected; use air-gapped workflows or hardware signing bridges and avoid exposing unsigned or private keys to third-party services.
- Hosted custodians may be appropriate for small holdings or for users who cannot manage keys, but they are poor choices for privacy-sensitive funds.
- Keep your Sapling spending keys offline whenever possible.
Spanish 
French 
German 
Polish 
Italian