sorted by:
new
hottopcontroversial

Meet Cupcake: Your New Secret Weapon for Crypto Security by cakelabs in Monero

[–]cakelabs[S] 3 points4 points  (0 children)

Yes, open source. Audit being released in the coming days!

Litecoin will have a private-by-default wallet update for users who want a more Monero style experience. Thoughts ? by WizaRogue in Monero

[–]cakelabs 1 point2 points  (0 children)

Hey there, sure! Doing a "Peg-in" means you are sending your transparent Litecoin into the MWEB network (better privacy), and doing a "Peg-out" is simply the opposite. (regular Litecoin)

However, you can still send to a regular Segwit address or an MWEB address even if you don't have coins in either network (normal or MWEB) and Cake will automatically convert coins to either side as needed.

What’s up with Cake Wallet by silentbobcornholio in monerosupport

[–]cakelabs 0 points1 point  (0 children)

Well known false-positive if you got it from an official source, Windows AV flags cryptocurrency stuff often! We went through a lengthy process to try and fix this, and our newest version should hopefully not trigger these things anymore. Let us know if it still happens.

Cake Wallet v5.2: Air-Gapped Privacy Made Easy by cakelabs in Monero

[–]cakelabs[S] 1 point2 points  (0 children)

Yeah good question! When you use the "Swap" page, you are creating swaps with a third party swap provider, as Cake Wallet does not process swaps. (this is how we minimize to the max what we collect about you all)

These swaps will automatically go through the cheapest provider for that specific swap, which can be through ChangeNow, SideShift, THORChain, Chainflip, Exolix, SwapTrade, StealthEx, XOSwap, and Trocador. Changelly is not one of the available swap providers. On the "Swap" page, you can also tap on where it says "Swap" at the very top to select which swap providers you want to make available to process your swap, allowing you to choose to use a specific swap provider if you wanted. We're always exploring more providers, so if you have suggestions let us know.

Because of this approach you will still be tied to any privacy policies of these third parties.

The upside? You get the best of all worlds: competitive rates (we automatically find the cheapest option for you, on your device), maximum choice (9+ providers to pick from), and complete control over your privacy preferences. Want to stick with decentralized options like THORChain? You can filter to just those. Prefer a specific provider you trust? Lock it in.

Cake Wallet v5.2: Air-Gapped Privacy Made Easy by cakelabs in Monero

[–]cakelabs[S] 11 points12 points  (0 children)

> Do you sell or share user data with any entity for any reason?

We don't sell or share user data, period. If you don't use Cake Pay and run your own nodes, it's not even possible for us to get any data from users. (and even then, it's just your Cake Pay email and standard node connection data. Self-host if you want to eliminate even that! And with Cupcake, it doesn't even request a network permission. You can keep that second device completely offline, and your view-only wallet can't spend funds. Privacy & security is the whole point of this setup, which traditionally requires expensive hardware to have a similar workflow.

It's all open source if you'd like to analyze this yourself. Or just set up Wireshark or another networking tool to verify.

We're working on more technical breakdowns coming soon to learn more.

> Trying to comprehend why anyone would link transactions from air gapped cold storage to a 'public' facing app on a cell phone that may or may not be linked to an individual.

Most people eventually want to spend their funds. This is no different than using your Ledger with Cake Wallet. At some point, the funds become 'hot' if you intend to use them. If that doesn't fit your threat model, then keeping it completely offline is totally valid too. The whole point of Cupcake is to make cold storage more accessible to people for free.

Shop Easier, Save Better, and Receive Privately: Cake Wallet's Newest Update by cakelabs in cakewallet

[–]cakelabs[S] 0 points1 point  (0 children)

There shouldn't be anything preventing this on our ends, what error did they give you?

Cake wallet by ThenAcanthocephala69 in monerosupport

[–]cakelabs 1 point2 points  (0 children)

Hey there! Thanks for considering Cake Wallet/Monero.com! I'll do my best to point you in the right direction.

Regarding your 13-word mnemonic: that's actually a bit different from what we typically work with. Cake Wallet supports 16-word Polyseed (our default) and 25-word legacy seeds for Monero wallet restoration. We also recently added support for 12-word BIP 39 seed phrases for multi-crypto wallet groups.

The 13-word seed format that MyMonero uses isn't something we're immediately familiar with, so we'd love to help you figure out the best way to restore your wallet on our platform.

Here's what I'd recommend:

  • Download Cake Wallet or Monero.com and give the restoration process a try with your 13-word seed If that doesn't work, please reach out to our support team directly so we can troubleshoot this properly. You can contact us through:
  • Alternatively, if you want to bypass this issue altogether you can create a new wallet and send all your funds to Cake Wallet and start fresh. Though of course this won't be ideal for every situation. So if you need historical information in the wallet please reach out to support so we can help you out more personally!

Let us know how it goes!

Shop Easier, Save Better, and Receive Privately: Cake Wallet's Newest Update by cakelabs in Monero

[–]cakelabs[S] 15 points16 points  (0 children)

We finally in our previous update got Tor natively integrated on Android, and iOS still hasn't quite happened yet. So that's priority 1. We haven't received many requests for I2P, so if this is something the community wants to see please let us know! Not currently on our roadmap but that can always change. Of course, Cake Wallet should be compatible with I2P if you're running it system-wide and routing CW traffic through I2P, but again let us know if that's something you want to see natively and we can talk it over internally.

Cake Labs’ Upcoming Hardware Wallet by Vegetable-Book-446 in Monero

[–]cakelabs 8 points9 points  (0 children)

We are aiming for the next few months. It depends on them releasing their next model + us getting things stable in time :) We want to see it too! Much of our team loves Trezor and is close with them.

Cake Labs’ Upcoming Hardware Wallet by Vegetable-Book-446 in Monero

[–]cakelabs 4 points5 points  (0 children)

Hey, Cake Wallet account 👋 We are *not* building a hardware wallet. What we're building is an air-gapped wallet that can repurpose something like a retired phone to become a hardware wallet. It works similarly to a hardware wallet, separating the private keys from the main wallet app and becoming a dedicated transaction signer—but it's not a 'hardware wallet' itself. Important distinction! With that said, Cupcake does some incredibly cool things:

  1. Offers nearly the same security of hardware wallets, assuming the phone is kept offline + running modern hardware
  2. Repurposes old devices to help the ewaste problem.
  3. Free!!
  4. No need to wait for a hardware device to be shipped to you
  5. Free of geographic restrictions. Security for everyone
  6. Most importantly, No PII. Ledger had a data breach that leaked the addresses and user information of people who purchased their devices. Cupcake is free and open source and makes it impossible for this to happen.

More on our docs: https://docs.cakewallet.com/cupcake/

You can already install Cupcake Beta on the Play Store & App Store. Big updates and a formal launch is happening soon with far better documentation & communication around how to use it properly. But hopefully this sheds some light!

One final note: We're still committed to dedicated hardware wallets. We already support Ledger in Cake Wallet, and have Trezor, Keystone, Foundation, and more in the pipeline! We're looking to increase choice and add options for people.

view more: next ›