Hi, adoption is growing with local markets. We have a concern about the node management in CakeWallet :
The cakewallet.com node seems always the selected default for all new app downloads :
could the node be randomly selected between the 6+ nodes list please ?
could you add a 2nd .onion nodes into default list for the new downloaded apps ?
Important : could you add an auto-fallback node function, so that a newbie keeps being synchronized even if Feds come for cakewallet.com ?
(Maybe a popup to ask after some down time, and even ask for Tor activation ? To be discussed)
Bonus : show a “remaining time” instead/aside the “remaining block sync” text, in the top progress bar : newbies don’t really know what a block is, so rarely opened wallet become easier to understand
Thanks by advance, always greatful for your work !
We actually already have this approach to nodes as an internal WIP item, where we’ll natively randomly select between trusted nodes (with a user still having the ability to edit/add/remove nodes, of course), similar to that seen in Feather.
For the sync status – we also have this as a WIP item with some internal test builds, hope to roll it out shortly and give muchc more useful information in the sync bubble
Thanks this is great news, looking forward to testing it and showing how resilient CW is
Would it be possible to have a demo button hidden (only for those who knows, and who canvass) when mnemonic words are displayed, so we don’t have to write down each time when simply doing a demo in front of a merchant ?
This is a major obstacle to canvassing !
Other remarks, for Desktop Windows :
In 1.0.0 version, we were able to get 24 mnemonic words when creating a Bitcoin wallet. This is great and important to get the most brute force resistance, when using Shamir/partial copies manually stored especially
In 1.1.0 version, when creating a “New seed” (no “group seed”), it is now only 12 mnemonic words : how come please ? Would it be possible to go to 24 by default ?
maybe it should be explained the pros/cons between “Group” vs “New” seed. Risk of theft, risk of losing the seed etc…
Important : when trying to download Windows .exe file, people get lost in Github and don’t know what to chose
now we get Brave/Chrome virus alert and downloaded .exe file is autodeleted every time ! > maybe with a .msi, or a .zip, or another method ?
Will definitely consider this, but the concern would always be that people would discover it and skip seed verification and then complain when they lose funds… But will think on how this can be done, it’s a great recommendation!
Cake support both 12 and 24 word seeds, with 12 being the default because they’re just as secure as 24 word seeds and far easier to store/restore. You can learn more in a post I wrote for Foundation here:
If you still want to use a 24 word seed, you can select that option in the Advanced settings drop down when creating a wallet.
Unfortunately there is very little we can do about this, but will investigate as well.
Would you have some news about 1, for onboarding acceleration please ?
Thanks ok, so by default it’s BIP39 (12 words) and we have to select Electrum for 24 words ? Would be great to precise the necessary word number beside Electrum / BIP 39 slider, or even better in the previous screen below the typing field for mnemonics !
(focusing ++ on UX cause we always get the same questions from blocked beginners !)
For Windows, would it be possible to update the website CakeWallet.com button for Windows download to a direct Github URL ? I think we are loosing a lot of people with this basic problem (I’m embarrassed myself to tell people that “it’s very simple” then I need to dive into Github release artifacts in front of them… ). Maybe at least a stable version and not the last one !
Also the Windows download button on website CakeWallet.com has a bug and is difficult to click on
For demos, you can just force close the app and re-open it and it will skip the verification and open the wallet (this is not recommended tho, as we want the users to save their seeds safely to avoid losing funds)
you can use both 12 and 24 words for both bip39 and electrum seed types
yup, thanks for the feedback, we are currently working on improving our website and hopefully soon you will find it in a better shape
Hi team, it’s been a year and a half, we talked about auto node switching / auto node fallback
Did you implement this feature actually and pushed it on the stores ?
Because it’s a few days we have been experiencing Sync issues with XMR, and beginners are contacting us because they are stuck, whereas the selected node should be switched automatically for the next node that is currently healthy (green)
Thanks by advance,
Bank-Exit collective (bank-exit.org)
We had deployed this earlier this year, but it was not in reality a good feature as it more commonly switched nodes based on temporary network issues and caused more problems then it solved.
Unfortunately there was a common community node that users were connected to recently (Hashvault) that has had critical issues with transaction broadcast among other things and has been a huge headache. We removed it from our node list entirely in v6.3.x and urge all users to switch off of it if they’re still using it for some reason, instead using our official node or a personal node of their own.
Hmm, thanks for the update
We should have an “hybrid” intermediary system, because what happened with Hashvault will happen with other nodes, and we are loosing hundreds of Monero people each time
Could you please share some more details about the issues that occured with switched nodes ? It could be something softer with a “threshold” (or “hysteresis”) that wait for a certain time or a number of attempts before switching
What are thinking the other guys about this ? Other ideas ? We need adaptivity/dynamic stuff in these times of repression
I am curious, could you explain how not having an automatic node-switching feature might make you use a different wallet? I know you’ve brought up the hashvault node debacle in your prior replies, but that’s one case, not multiple. What is wrong with simply going to nodes list, picking a different one that the wallet connects to and being done with it? Or better yet, manually putting in remote ones that you trust, or your own, self-hosted node(s)?
I am not associated with Cake, yet it makes me legitimately curious when you say:
Otherwise other Monero wallets that implement auto-switch are going to be the new standard
I understand, to put it more clearly : this puts us in an awkward position and makes fools of both us and the Monero system. @sethforprivacy@vik
People when they use their credit/debit card, don’t even know where the payment terminal connects, or a damn idea of what’s going on to pay. They just pay.
We are at the adoption stage where it’s exactly the same : people know there is big problems with money and gov, they trust Monero as an alternative, they just want it to work.
No geeky thing,
No elliptic curve, GPG and node distribution 2 hours explanation,
Just open app, receive and send, like with bank app
We are now in the process of onboarding city officials : we don’t want to be ridiculous again saying to each one of them “it’s broken again, go in parameters and choose this xxxyyyy.wtf geeky URL and it might work this time”
Trust is very thin to have adoption work. So I’m reaching out again to CakeWallet team : could you go deeper to have a auto-node switching solution please, soon ?
We have onboarded thousands to CakeWallet, even elected officials. This feature is not much asked… youtube.com/watch?v=e7dywiZIpWg
Moreover, repression is raging here in Europe, could shutdown some nodes.
Developing : (for transparency, discussed with Vik)
What I’m pushing for is to bring back the auto-switch by default, BUT with a smarter version that offers a mu ch smoother experience.
This is not a demand for someone like me - who knows how to tweak settings - but for mainstream adoption: the average user who just wants to use their wallet without tinkering, even a year later, and even if three nodes have gone down in the meantime.
Here is a vibecoded simulator to test all scenarios from “standard” to “chaos” :
It allows for reproducing the tricky “Hashvault” failure (status OK, but non-functional) as well as other scenarios involving node failure or disappearance.
After some testing. the two most relevant approaches seem to be:
Quorum
or
EWMA + non-sticky
Could some of you “play” with this simulator so we can debate on the best method ?
). Maybe at least a stable version and not the last one !
What I’m pushing for is to bring back the auto-switch by default, BUT with a smarter version that offers a mu ch smoother experience.
: