|
I have seen many different varities, but never a 1L barrel.
|
|
|
|
...
Any idea who or what could own this wallet?
F2Pool |
|
|
|
Who holds the private keys? |
|
|
|
Great! For instance, this allows you to import your TREZOR word list in case your device was lost or damaged so you can quickly move your funds to safety. Just for the sake of symmetry... Can I also use word list generated by Mycelium during HD account backup as input for Trezor? Yes, but have in mind that Trezor provides higher security than what you can get on an android device, and by having the same master seed on two platforms gives you the least common denominator... Security wise. So, I would only do that if my phone was broken. |
|
|
|
1.2.2 is out. This is a minor update which adds a few Local Trader features based on user request: - Added 'Info' button next to 'Buy' button so you can see information about the seller before starting a trade. - Add USD price for 1 BTC using small fonts for ads that are on a different currency. - You can now change the currency when creating/editing a sell ad - You can now see your receiving address before a trade starts (if you have more than one address) ScreenshotLocal Trader now has 1311 traders, 969 ads, and has conducted 124 trades with a total volume of 111 BTC. Every trade has two traders. We are working on a google map that displays all the ads world-wide - Jan Is this the latest changelog for the main (non-beta, non-testnet) branch? Can you link to these (and the beta, testnet version changelogs) in the OP? It's hard to find these throughout the thread. The latest generally available version is 1.3.3, and the release notes were published here: v1.3.3 was released to Google Play store, github, and our site. The list of changes from last regular release include: * Generic scan button in the main view - Use this to quickly scan QR codes to send bitcoins. In the future, this may be used to quickly log into websites with BitID. * Improvements to barcode scanning with flashlight toggle and autofocus setting * Email notifications for LocalTrader - Google Push Notifications system is still kind of unreliable, and we can't fix it because it's Google servers that are having issues, so this is a fix until we figure out something better. * Fixes and connectivity fallback for dns issues - A few days ago we had an issue where our domain name, which is pointing to our servers, was temporarily turned off by our provider while they verified that we are who we say we are. Should this happen again, wallets will switch to contacting our servers with their IP numbers directly (this is also likely temporary, until we move everything to Tor) * Various crash fixes We think that this will be the last feature update for the non-HD version. Stay tuned for an upcoming Mycelium HD release. I have added the above to the OP (You can see all the releases/tags in the GitHub repository here: https://github.com/mycelium-com/wallet/tags but unfortunately we haven't linked the release notes of the individual versions to the GitHub repository.) |
|
|
|
...
This is true. It is also true mycellium app loses private keys.
Can you elaborate on that? |
|
|
|
Hi guys, I was having a little trouble working out a nice, safe way to get my private keys out of the data.xml for importation back into Mycelium. I think I could have used bitaddress.org but I decided to write something to do it for me. I'm letting it out to the public in case anyone else might find it useful (it also might be interesting to study for other purposes). It must be run in the same directory as the data.xml and it will spit out a list of the public, private and WIF encoded keys to the terminal and will create a webpage with the public and private keys listed on it as QR codes ready for scanning (I would recommend using a browser on the local filesystem to open it and not having it on a live web server (unless you're totally internet disconnected and probably not even then)).
This may be useful for creating a paper backup even. You may want to increase the level of the QR code in that case. Currently set to "L" for low.
Pretty cool stuff  With Mycelium 2.0 we migrate away from using data.xml and store stuff in a sqlite database instead, so there will be a bit of coding to get it out going forward. |
|
|
|
I realise that one of the “philosophies” behind the Mycelium 2.0 wallet is to take users away from managing addresses. The UI as it stands basically requires users to use receiving addresses in sequence as they are offered up.
However, with the availability of BIP32/39/44 key/address generators, it is easy to generate forward addresses online/offline using our 12 word mnemonic code with or without password. For a particular Account, a user might want to generate receiving addresses, say, 1 to 10 and give them out to one party who is going to make regular payments to him. I have tried simulating something like this with the testnet version and everything seems fine.
1) Are there any issues with using 2.0 in this way?
2) Could future versions of Mycelium offer the option to generate forward addresses within the application?
3) How far out in a chain, over unused addresses, does 2.0 scan to look for funds?
1. No issues. This is perfectly fine. 2. Yes 3. We scan 20 address ahead on the external chain to comply with account lookahead discovery as dictated by BIP44 |
|
|
|
...
With the current version of Mycelium you can go to the Keys tab and see the addresses you are working on. Some of those addresses have a key associated with them, they are the ones you can spend from. The ones without a key are so called read-only addresses, you can monitor them but not spend from them.
With Mycelium 2.0 the Keys tab is renamed to Accounts. All your existing keys/addresses are now called accounts and work like before. Those are the ones I call legacy accounts.
In addition you will have one or more Hierarchal Deterministic (HD) accounts following the BIP32/BIP44 standard. An HD account is one that automatically generates new addresses as you use the wallet for sending and receiving. This means that you get much more anonymous (today anyone who knows your Mycelium bitcoin address can see all transactions associated with it).
Furthermore, because we now have BIP32 support this means that one backup of one secret is enough to generate all the private keys/addresses you will ever need for all the HD accounts you will ever need. Everything can be deterministically generated from one secret. The backup mechanism we use follows the BIP39 standard, and basically involves that you write down 12 random words on paper.
As a user you will not have to worry about all of those addresses, they are managed internally.
Today Mycelium lets you monitor 20 separate bitcoin addresses. For some of those addresses you also have a key (the default), which lets you spend from them
Great So what your saying is the old way will not disappear, I will be able to choose ? Lets just say I want to make a new account can I make it like a legacy ? And how will I be able to make another legacy type account with Mycelium 2.0, I assume there are options for this? Or are you saying that ANY new account created from M-2.0 will be HD and will transact in the NEW style? If this is the case does this mean I will never be able to make another legacy account with M-2.0 other than my old account from previous version of mycelium meaning I will have to make it outside of M-2.0 and then import it? Thanks for clarification I mean who knows when I feel comfortable I may jump to HD, but its still great to have a choice. Correct, you have a choice. But, the wallet will no longer let you create new random legacy accounts (create a new random key), you can however import a private key that you have made elsewhere by selecting Advanced when creating a new account. In that scenario we expect the user to know what he does and that he has the private key stored safely outside the wallet. It will not be part of the HD account backup. We really wish our users to be safe and not loose funds because they sent funds to a key that they cannot recover. You should really try it out. Everything is available for the testnet, where you can play around with worthless testnet coins: https://play.google.com/store/apps/details?id=com.mycelium.testnetwalletOnce you have it installed you can get free testnet coins by "buying" them (for free) from Virtual Trader when you click Buy / Sell Bitcoins |
|
|
|
thanks guys,
so as for my queries, is this going to effect the way I transact now as well as transact from my cold storage, I really do not want to mess around with different change addresses, I just do not want to know about it and I want to use the same address as I do now. I also want to keep 1 Cold Storage backup and not keep changing my backup every single time I make a simple transaction from it.
In that case, after the 2.0 upgrade, you should just keep using your existing (legacy accounts) and cold storage spending. Sorry, but I don't understand it, could you make it a bit clear. Thanks With the current version of Mycelium you can go to the Keys tab and see the addresses you are working on. Some of those addresses have a key associated with them, they are the ones you can spend from. The ones without a key are so called read-only addresses, you can monitor them but not spend from them. With Mycelium 2.0 the Keys tab is renamed to Accounts. All your existing keys/addresses are now called accounts and work like before. Those are the ones I call legacy accounts. In addition you will have one or more Hierarchal Deterministic (HD) accounts following the BIP32/BIP44 standard. An HD account is one that automatically generates new addresses as you use the wallet for sending and receiving. This means that you get much more anonymous (today anyone who knows your Mycelium bitcoin address can see all transactions associated with it). Furthermore, because we now have BIP32 support this means that one backup of one secret is enough to generate all the private keys/addresses you will ever need for all the HD accounts you will ever need. Everything can be deterministically generated from one secret. The backup mechanism we use follows the BIP39 standard, and basically involves that you write down 12 random words on paper. As a user you will not have to worry about all of those addresses, they are managed internally. Today Mycelium lets you monitor 20 separate bitcoin addresses. For some of those addresses you also have a key (the default), which lets you spend from them |
|
|
|
thanks guys,
so as for my queries, is this going to effect the way I transact now as well as transact from my cold storage, I really do not want to mess around with different change addresses, I just do not want to know about it and I want to use the same address as I do now. I also want to keep 1 Cold Storage backup and not keep changing my backup every single time I make a simple transaction from it.
In that case, after the 2.0 upgrade, you should just keep using your existing (legacy accounts) and cold storage spending. They continue work as they do today. The main benefits of using the new HD accounts are to be more anonymous and only making one backup ever. |
|
|
|
Hi, I've read quickly through the 47 pages here but I could not find anything about signing a message with my Mycelium wallet address to prove its mine. Is there a way to do this? Thanks in advance.
Yep. Go to the Keys tab, select a key, then choose Sign Message. |
|
|
|
Here is a problem I have been having when doing in person trades. I have been using wallet32 for all my trades lately (until the mycelium hd wallet comes out). Often I am doing trades where there are more than one people that I have to trade with at the same time, usually one guy I know and his friend. I have a few times run into the problem where I cant send funds to the second guy right away because all my bitcoins are tied up with the last transaction. I have to wait for one confirm before the remaining funds are sent back to one of my change addresses. I know I can keep different amounts on different addresses/accounts to try and avoid this problem but this is a pain to send smaller amounts to a bunch of separate addresses and can start costing some significant money at 0.0001 per transaction. My question is, are there any plans to one day implement the ability on the mycelium wallet to sent to multiple addresses in one transaction such as one is able to do on mytrezor.com z.B.?
From day one Mycelium has allowed you to send "unconfirmed change sent to self" just like the satoshi client. So you won't have to wait for a confirmation to send the next transaction. You can however not spend coins sent from another address before it has confirmed. This also applies to the HD upgrade. Wait a minute, I am totally confused here, Mycelium doesn't use change addresses right? I have tested this myself, I sent a transaction to an address, 2 seconds later I sent another transaction to another address, Both TRansactions confirmed seconds apart from each other. When I check the transaction history it only shows 2 transactions to these addresses, it doesnt show any change returning to my address. I thought Change address was just a feature that wallet devs can implement or not, its up to them and I thought mycelium did not implement this feature, which I am thankful for. Or am I wrong? does mycellium use the same address as the change address , so in reality there is 2 transactions being sent . 1 to the receiver and 1 back to the sender. Is this a MUST-USE feature of bitcoin? I have another question for the updates to come - Will you think about implementing Multi-Sig option as this is truly the future of security and other contracts. How awesome would it be if Mycelium did it all. Lastly is offline signing on your roadmap? These last 2 features would literally make this app unstoppable and allow people who have never used bitcoin before to really see the power of it all in one single app. The current version does not use separate change addresses, but the next version will. However, this is unrelated to being able to spend 'change sent back to self'. When you send a transaction you almost always have a change output which goes back to one of your own addresses (unless you spend exactly all value of your unspent outputs). Most wallet implementations allow you to spend that change immediately without confirmation as you are not expected to double spend yourself. We are thinking about multi-sig, but it will have to wait until we have BIP32/39/43/44 under our belt, which will happen in the next release. By offline signing I guess you mean the ability to transfer sufficient unsigned data to an offline wallet, have it create a signed transaction, and then transfer the transaction to the online wallet. We have been thinking about that for a long time but there are a few things holding us back. 1. For security reasons it is not enough to just transfer the unsigned transaction offline. You need to transfer all the complete set of transactions that fund the new transaction. This allows the offline signer to verify that you do not pay an exorbitant fee. This can easily mean tens or hundreds of kilo bytes of data. Using animated QR codes will not suffice. You need something like a USB stick or a bluetooth (which may open another attack vector) 2. It requires you to use a second phone for only that purpose, which will be a turn off for many users. I am not saying that we will not do it, but it is not as trivial as it may seem. |
|
|
|
Here is a problem I have been having when doing in person trades. I have been using wallet32 for all my trades lately (until the mycelium hd wallet comes out). Often I am doing trades where there are more than one people that I have to trade with at the same time, usually one guy I know and his friend. I have a few times run into the problem where I cant send funds to the second guy right away because all my bitcoins are tied up with the last transaction. I have to wait for one confirm before the remaining funds are sent back to one of my change addresses. I know I can keep different amounts on different addresses/accounts to try and avoid this problem but this is a pain to send smaller amounts to a bunch of separate addresses and can start costing some significant money at 0.0001 per transaction. My question is, are there any plans to one day implement the ability on the mycelium wallet to sent to multiple addresses in one transaction such as one is able to do on mytrezor.com z.B.?
From day one Mycelium has allowed you to send "unconfirmed change sent to self" just like the satoshi client. So you won't have to wait for a confirmation to send the next transaction. You can however not spend coins sent from another address before it has confirmed. This also applies to the HD upgrade. |
|
|
|
Amazing update! Thanks so much for your hard work! By the way, are there any plans on supporting the HW.1? I recently bought one and they work great IMO. We don't currently have it on our roadmap. |
|
|
|
|
Mycelium 2.0 for testnet ALPHA 6 released to the play store, and should be available in an hour or two.
A lot has changed since the Alpha 4 release. Some of it:
- We are now based on BIP39 word lists for backup / restore. You only need one backup forever, and no more encrypted PDF backups
- When you install Mycelium for the first time you are asked whether you want to create a new wallet or restore a backup (Restore is Trezor + wallet32 compatible (BIP39 + BIP44)). Your first account will be an HD account
- When you do an upgrade from version 1.x a new master seed and the first HD account is automatically created
- We nodge users to make a backup by showing a "Secure My Funds" button if no backup has been made yet + if one of the HD accounts have funds.
- We nodge users to move funds away from 'legacy' accounts by showing a "Secure My Funds" button if a legacy account has funds.
Note: when upgrading from Alpha 3 to Alpha 6 the account names will disappear. Once we hit production the 1.x names will be properly be migrated from your classic keys/addresses to accounts.
If you are a translator you'll get a notification later today for all the new HD strings. Let's get this baby out.
|
|
|
|
I have managed to repeat the condition I described above. Firstly, when no Account is highlighted, the top bar is NOT entirely blank, I was mistaken previously; it has only the logo and menu icon. Secondly, the condition seems to occur when switching to the Accounts page immediately after a transaction. Thirdly, the condition goes away if I change the view to landscape from portrait. I have screenshots if you need them.
Screenshots would be interesting. Please share here or send them to developers@mycelium.com. Also, what device are you using? |
|
|
|
Been testing and it looks great.
One suggestion, not sure whether I might have missed something or maybe I'm still to new at this.
When clicking on 'Receive' one have the option to enter an amount with the 'Optional Amount'. When I select this I see that the amount is entered in bitcoin. Would it be possible to maybe be able to change this to enter an amount in say fiat i.e. USD?
I think this might make it easier as often a transaction is based on a fiat value which one then first have to convert to bitcoin before one can enter it here. Would be much faster if I could just enter say USD 200 and have the QR generated with the relevant bitcoin value.
Hope above makes sense. Other than that looks great.
Thanks. You can do this already, but maybe it is not that obvious. "BTC" is an icon, and if you click it the valuue turns into your selected fiat currency. |
|
|
|
* Email notifications for LocalTrader - Google Push Notifications system is still kind of unreliable, and we can't fix it because it's Google servers that are having issues, so this is a fix until we figure out something better.
How to change email address in LocalTrader? About HD Wallet: Can I see more (used?) receiving addresses? Can I import Electrum Public Key (for watch-only functionality)? Can I create Public Key of Mycelium Master Seed? You can set the notification email address in settings. You cannot see old receiving addresses directly. In general reusing address makes you less anonymous. There are two workarounds however: 1. You can select a transaction in an account and 'Show Details'. This will list all the addresses participating in the transaction. If the transaction was you sending, then the input addresses will be yours. 2. You can select an account and select 'Show Unspent Outputs'. This will list those of your addresses that have funda in them. In general I think we should all be moving away from directly managing/using addresses. You cannot directly view/export the root public key from the master seed. You can however see the BIP39 word list (in settings for now as a debug thing). We are probably going to add a feature that allows you to properly export the master seed word list. That list can be imported into other BIP39 compatible tools. |
|
|
|
Thanks ....
I am considering replacing multibit with mycelium. But I need access to the private key in mycelium to do this.
I tried to import the key from clipboard, but the option is greyed out even after copying the test to the clipboard.
How do I get the clipboard import option to be active?
(If you wish to migrate then I think it is a better idea to send the funds using a transaction.) The clipboard button automatically gets enabled if you have a private key on it in SIPA format. Here is an example: KwWVqndQMw1DyL4Sb2moNArofcQztswhGbSkX2M9mhDBv6BtZ6gW DON'T use it except for testing purposes! On some phones there have been problems with the clipboard, so alternatively you can turn it into a QR code using some software you trust. |
|
|
|
|
Show Posts
