You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The node must be connected to TOR with the proxy flag and has the onlynet=onion qualifier set also. The node is connected to peers and at the chain tip when compared to known good explorers. The user attempts to send a TX, either normal send or CoinJoin, or protx, it doesn't matter and the TX never gets ISD, nor mined. It claims to be broadcast and in mempool. The TX cannot be abandoned and using the resend option does not push it through. The only way to get the TX to confirm, is to restart the wallet without connection to TOR. Then the TX will go through as expected. This behavior started in v20 and affects all v20.x releases. It has been reported by numerous community members myself included. Tested with windows wallet.
The text was updated successfully, but these errors were encountered:
The node must be connected to TOR with the proxy flag and has the
onlynet=onion
qualifier set also. The node is connected to peers and at the chain tip when compared to known good explorers. The user attempts to send a TX, either normal send or CoinJoin, or protx, it doesn't matter and the TX never gets ISD, nor mined. It claims to be broadcast and in mempool. The TX cannot be abandoned and using the resend option does not push it through. The only way to get the TX to confirm, is to restart the wallet without connection to TOR. Then the TX will go through as expected. This behavior started in v20 and affects all v20.x releases. It has been reported by numerous community members myself included. Tested with windows wallet.The text was updated successfully, but these errors were encountered: