Cake wallet frustration

[Karl_3000]

When I want to make transaction, this is the error it was showing. But if I try two more times, the transaction will be successful. I have tried it many times today but it kept showing the error.



After the error it was showing this error later if I try to send the transaction again without closing the app.


I went through the nodes, I used the one that is in green and not in orange or red and the synching was fast but to make transaction was a different thing entirely that is coupled with frustration.

After trying for more than 7 times and the two errors is showing after I close and open the app again continuously, I fed up and import my seed phrase on Bluewallet and the transaction was successful on Bluewallet within few seconds that I imported the seed phrase..

Cake wallet is buggy.

[OmegaStarScream]

I found this (altho it is from last year) googling the issue: https://forum.cakewallet.com/t/transaction-commit-failed-please-contact-support/343

The answer suggests that you should first update your wallet ( if it's not already) and then try again.

[nc50lc]

Cake wallet is buggy.

It would've been beneficial on both sides if they at least provided a way to export or view logs on situations like this.
All I see are for lightning, payjoin and silent payment logs.

I went through the nodes, I used the one that is in green and not in orange or red -snip-

Even if you didn't, it should automatically use the most stable connection if the red or orange ones failed.
Since it failed 7 times this time, there could be some issue with your ISP or network with cake wallet's default Electrum nodes.

At least you can manually add any reliable Electrum server there if you decided to still use it.

Also, Cake has other connections (under App settings->Connections) that can be heavy for some networks if left enabled.

On the other hand, BlueWallet uses a different server that your network has no issue connecting with.

[Kruw]

Maybe your coins were frozen by Cake because you used a VPN?  https://x.com/Kruwed/status/1869564255080718626



Which part of the wallet are you using? If you use Spark or swaps, Cake's partners can steal your coins:

Just make sure to NEVER use Cake Wallet, they will scam you out of your coins since they use Spark (a statechain, which is custodial and has no privacy) instead of Lightning:



https://x.com/sethforprivacy/status/1861838715049615833

[Karl_3000]

Maybe your coins were frozen by Cake because you used a VPN?  https://x.com/Kruwed/status/1869564255080718626

Which part of the wallet are you using? If you use Spark or swaps, Cake's partners can steal your coins:

I am not using swap on Cake wallet, I do not even have any altcoins on the wallet, only what I use it for is bitcoin receiving and sending.

Cake wallet has inbuilt Tor but I use the wallet with ISPN.

Cake developers need to work on some things on the wallet.

[BitMaxz]

Maybe your coins were frozen by Cake because you used a VPN?  https://x.com/Kruwed/status/1869564255080718626

Isn't the Cake wallet non-custodial?
So, how does Cake control and freeze your wallet? Whether you use a VPN or not, they don't have complete control over your wallet.

I think the OP issue is due to the server node since it works on Blue Wallet; they use different servers, and I think to solve this issue, you need to change the server from Cake Wallet. Usually, we can change the server on wallet settings.

[Kruw]

Isn't the Cake wallet non-custodial?
So, how does Cake control and freeze your wallet? Whether you use a VPN or not, they don't have complete control over your wallet.

Swaps, Spark, and Cake Pay are all custodial.

[nc50lc]

Maybe your coins were frozen by Cake because you used a VPN?  https://x.com/Kruwed/status/1869564255080718626

I am not using swap on Cake wallet, I do not even have any altcoins on the wallet, only what I use it for is bitcoin receiving and sending.

Then it's likely related to the Electrum servers in Cake's settings.

The three of those are proprietary, Cake's legacy and two electrum servers.
The other one from its major developer.

Manually adding a reliable server may solve it.

Cake developers need to work on some things on the wallet.

The thing is, if issues like this isn't reported, the developers wont know that it's occurring since most users don't experience this issue.
If you want to help them and have the time, you can consider posting a new issue in their repo: github.com/cake-tech/cake_wallet/issues

[RGBTC]

But if I try two more times, the transaction will be successful.

I'm more suspicious of a broadcast/node or timeout issue.
One thing to check, was the TXID present when it failed the first time? If it was, don't send it again, as it could cause duplicate transactions or wallet confusion.

[pooya87]

But if I try two more times, the transaction will be successful.

I'm more suspicious of a broadcast/node or timeout issue.
One thing to check, was the TXID present when it failed the first time? If it was, don't send it again, as it could cause duplicate transactions or wallet confusion.

It seems like the timeout error (no peer reply) has a different error message and it will print Transaction failed to broadcast, please try again in a second (explicitly saying try again later not just contact support).

The message OP is getting (contact support) is the generic bare minimum error message that seems to have been thrown here which is when all other checks fail to detect why it failed and considering that "error" is discarded, there is no way of knowing or logging what the problem was for failing here.

So perhaps the Electrum server is actually rejecting OP's transaction. It could be Double spend, Script verification failure, Node's mempool being full!, even having insufficient fee...
Unless I'm not finding it in Cake's source, their handling of error messages is way too short. Here is the long list of messages Electrum "handles": https://github.com/spesmilo/electrum/blob/1de4403375199f9c393aa6f1c100a0a9847c3826/electrum/interface.py#L1630