trasla
|
|
September 25, 2014, 01:58:49 PM |
|
Yeah, change is kinda funky when you first learn about it. Even more fun is that many wallets actually generate a new change address to send the change to (So you end up with many different private keys in a wallet). I prefer the way Mycelium does it though.
In the upcoming version, when using an HD account, mycelium will as well generate a new address for each change. It will also generate a new receiving address every time you receive coins. All of this will take place under the hood, so you dont have to see or manage the keys, you just have an account with a balance where you can spend and receive.
|
|
|
|
|
|
|
There are several different types of Bitcoin clients. The most secure are full nodes like Bitcoin Core, but full nodes are more resource-heavy, and they must do a lengthy initial syncing process. As a result, lightweight clients with somewhat less security are commonly used.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
OnkelPaul
Legendary
Offline
Activity: 1039
Merit: 1003
|
|
September 25, 2014, 02:02:18 PM |
|
You should probably submit your CV right now anyway, so you're first in line when a new hiring round starts Looks like they're a cool company to work for. Onkel Paul I don't know. I've cold submitted a few in the past and in my experience "We will keep your CV on file" never leads anywhere. Which is understandable. Hiring is usually a process. I see that for big companies, but Mycelium is a pretty small company (yet) so it's unlikely that your CV would be stuffed away without being noticed. Submitting the CV now does not mean that you should then be quiet when they call for resumes in another hiring round, but that you should follow up with updated CV info and state your interest in their job offer. Good luck whatever route you choose! Onkel Paul
|
|
|
|
hgmichna
|
|
September 25, 2014, 02:03:35 PM |
|
In the upcoming version, when using an HD account, mycelium will as well generate a new address for each change. It will also generate a new receiving address every time you receive coins. All of this will take place under the hood, so you dont have to see or manage the keys, you just have an account with a balance where you can spend and receive.
Could you explain this more precisely? What happens when I receive two amounts and later want to send them to another address. How exactly are they joined? Will that be two transactions? I appreciate all improvements that lead to more privacy.
|
|
|
|
trasla
|
|
September 25, 2014, 02:14:36 PM |
|
Could you explain this more precisely? What happens when I receive two amounts and later want to send them to another address. How exactly are they joined? Will that be two transactions?
It will be only one transaction. Now, when you receive two transactions, you have two unspent outputs on one address, and when you send an amount which requires both of them, they get joined in a single transaction. The same thing will happen with HD, only difference is the two unspent outputs will be sitting on different addresses. So whenever you give someone your receiving address, it will be a fresh, unused one, and he can not check your previous transactions (note that he could probably link it to other addresses you use later, once you spend the coins - we will work on improving this through using some coinjoin methods sometime in the future). When you send money, some outsider seeing the transaction can not easily determine how much was actually sent, cause the change will go to a brand new address as well, and we put outputs in a random order. HD alon will not grant perfect privacy, but is an important base step to get rid of address reuse and be able to build some fancy stuff on top.
|
|
|
|
hgmichna
|
|
September 25, 2014, 02:27:37 PM |
|
… The same thing will happen with HD, only difference is the two unspent outputs will be sitting on different addresses. So whenever you give someone your receiving address, it will be a fresh, unused one, and he can not check your previous transactions (note that he could probably link it to other addresses you use later, once you spend the coins - we will work on improving this through using some coinjoin methods sometime in the future).
When you send money, some outsider seeing the transaction can not easily determine how much was actually sent, cause the change will go to a brand new address as well, and we put outputs in a random order. HD alon will not grant perfect privacy, but is an important base step to get rid of address reuse and be able to build some fancy stuff on top.
Thanks, now I understand it much better. However, one thing is still unclear to me. If two amounts sit in two different bitcoin addresses, but I send one amount that is bigger than either one, will the recipient get two transactions from two different addresses? Or is there some clever way to join them before or while they are sent?
|
|
|
|
trasla
|
|
September 25, 2014, 02:35:19 PM |
|
However, one thing is still unclear to me. If two amounts sit in two different bitcoin addresses, but I send one amount that is bigger than either one, will the recipient get two transactions from two different addresses? Or is there some clever way to join them before or while they are sent?
There will be only one transaction, which has inputs from two different addresses.
|
|
|
|
hgmichna
|
|
September 25, 2014, 02:48:08 PM |
|
There will be only one transaction, which has inputs from two different addresses.
Ah, thanks! I should have guessed. Have never received such a transaction. I am very much looking forward to the new version. Currently I keep creating new temporary addresses manually, but I don't find the time to keep doing backups, so I live in fear. (:-) The new version will relieve me of that.
|
|
|
|
Newar
Legendary
Offline
Activity: 1358
Merit: 1001
https://gliph.me/hUF
|
|
September 25, 2014, 04:21:04 PM |
|
With the new version coming up has there been any considerations to include tipping (or allowing multiple "recipients" transations)?
|
|
|
|
Rassah
Moderator
Legendary
Offline
Activity: 1680
Merit: 1035
|
|
September 25, 2014, 05:30:07 PM |
|
With the new version coming up has there been any considerations to include tipping (or allowing multiple "recipients" transations)?
Not yet. Though we have received this request a few times from a couple of people, at this point we think adding multiple recipients may make the wallet more confusing for normal users. For instance, if you scanned a wrong address, and wish to scan the right one, are you replacing the old one, or adding a new recipient? Also, since it's already possible to send transactions over and over to multiple people, even with 0 confirmations, we don't think it's very necessary, aside from extra convenience.
|
|
|
|
Mendozer123
Newbie
Offline
Activity: 7
Merit: 0
|
|
September 28, 2014, 07:35:52 AM |
|
Apologies if this doesn't belong here, someone suggested I ask the question in this thread.
Don't know where I went wrong - gladly pay for assistance Today at 01:33:47 AM #1 Short story. Long time MYCELIUM user, same wallet for 8+ months Overnight I login and find a strange new public key which I don't recognise. I also see that my entire phone book has been deleted. My original wallet still shows up as a secondary and the balance is correct but I have no private key associated and I do not know what to do.
I'm going to get burnt for saying I can't remember if I followed proper backup protocol with my wallet when I first started using it, so I don't have any private keys or passwords backup up :-) At the time. I stupidly found all the bitcoin jargon too hard to follow and since my wallet was carrying amounts so small not to be concerned I did not pay proper attention.
Can anyone assist me in any way - I will pay generously I ran in to a few sites that claim to be able to recover your key/password but I am dubious.
Thanks in advance to anyone who can suggest something easy enough for a tech noob like me to try, alternatively I'm happy to pay someone to help
|
|
|
|
bitofc
|
|
September 28, 2014, 07:47:30 AM |
|
is Mycelium 2.0 a multi-sig wallet?
|
|
|
|
trasla
|
|
September 28, 2014, 11:41:03 AM |
|
Mendozer, do you have beta releases enabled? (Is the tab with your keys called 'Keys' or 'Accounts'…) Did I get this right: Without action by you, you got an additional Key, and the one you had before switched to read only? Since you said you don't remember about backups, I guess you don't have a backup pdf plus the written down password?
|
|
|
|
trasla
|
|
September 28, 2014, 11:42:02 AM |
|
is Mycelium 2.0 a multi-sig wallet?
No, the first HD release will not include management for multi sig.
|
|
|
|
DaveF
Legendary
Offline
Activity: 3472
Merit: 6264
Crypto Swap Exchange
|
|
October 04, 2014, 05:59:57 PM |
|
Hello, I am having a small issue.
I have 2 incoming transactions to my Mycelium address that are *never* going to confirm (Small BTC amount, large TX size, 0 TX fee). Is there a way to purge them from being displayed or just purge them from my phone?
It's not critical, just really annoying.
Thanks, Dave
|
|
|
|
birr
|
|
October 04, 2014, 11:06:38 PM |
|
Here's something a little different for you all to think about. I have a friend who who buys coins from me and he uses mycelium. But... he doesn't back things up (and until this morning I didn't know this). You can guess what's coming: he broke his phone. And lost 26 coins. Coins that I sold him, so although it was his own fault, I still would like to help him. Friend lives in Brooklyn and uses android devices (obviously, because he uses Mycelium). So I have two issues I need to solve.
Issue number one: He probably needs a data recovery specialist. I say probably, because the shop he took the phone to told him there's more to this phone's problems than a broken screen. Something in the circuitry was damaged. So getting the keys out of memory is going to require expert help. Any ideas?
Issue number two: He has agreed to let me generate a key pair, back up/save it, and send him the private key so that he can import it into mycelium. That way he can't screw up again. I need to figure out how to send him the private key securely, and still have him be able to import it. Which means sending an image of the qr code, because text private key import is unsafe. Maybe I can attach the qr code to an email and encrypt it? He has used gpg and has a public key he can send me. I started looking into how to use gpg and really just want a simple way to get things done, but this doesn't look too simple. So could use suggestions. For what it's worth, my only computer is a nexus 7 tablet. I have it set up dual boot with android and Ubuntu touch. I booted into ubuntu, opened terminal and generated a gpg key, but I'm not sure I even need it. From my cursory googling it looks like maybe all I need is his public key, and a gpg app for android...?
Issue number one is much more important.
|
|
|
|
ffe
|
|
October 05, 2014, 12:46:33 AM |
|
For issue 2:
Download bitaddress.org to your own computer and run it off the internet.
Generate a paper wallet with BIP38 encryption enabled. The secret side is encrypted (starts with a 6) and can be sent safely to your friend. (QR encoded).
BIP38 secret keys can be loaded into Mycelium by providing the password.
|
|
|
|
birr
|
|
October 05, 2014, 12:49:41 AM |
|
Okay, then I can tell him the password over the phone. Next question: does Mycelium save keys on the flash card or hard drive? If it's the flash card, maybe he can just put the card in a working phone.
|
|
|
|
Richy_T
Legendary
Offline
Activity: 2436
Merit: 2120
1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k
|
|
October 05, 2014, 01:12:23 AM |
|
Mycelium saves the keys to the internal memory. Depending on the phone and in exactly what manner it's broken, it may be harder or easier to recover. It usually should be possible to recover it one way or another if encryption isn't involved but it may mean someone has to de-solder the flash chip in the worst situation.
|
1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k
|
|
|
birr
|
|
October 05, 2014, 02:11:56 AM Last edit: October 05, 2014, 02:46:56 AM by birr |
|
Thanks. The Mycelium clipboard import feature doesn't recognize encrypted private keys and the button stays greyed out. Since text doesn't work, I'll have to use qr. The only way I've found to take a pre-existing private key and generate a bip38 encrypted qr is: Paste key in bit2factor.org, create encrypted text key. Convert text to qr code using goqr.me or some other text-to-qr generator. While I've tested this method and it works, the extra steps create vulnerabilities. I remember I asked about encrypted text import before. It would make sense to have it. But lacking that, maybe there is some simple way to turn a private key into an encrypted qr code that I don't know about? Edit: this works OK https://bitcoinpaperwallet.com/bip38-password-encrypted-wallets/
|
|
|
|
jacktheking
Legendary
Offline
Activity: 1484
Merit: 1001
Personal Text Space Not For Sale
|
|
October 05, 2014, 02:16:04 AM |
|
I downloaded this to my android few days back. I have transferred all my Bitcoin from desktop wallet to Mycelium. I have also created a backup. Well, I found MyCelium useful and.. we can use it anywhere as long as our smartphone is with us!
|
So sad! This profile does not appear as the #1 result (on anonymous) Google searches anymore.
Time to be active on the crypto forums again? Proud to be one of the few Legendary members of the Sparkie Red Dot!
Gonna put this on my resume if I ever join a cryptocurrency/blockchain industry!
|
|
|
|