This is not an inexpensive vodka. Top shelf pricing.
That said, if any USA folks want a sample, I'm pouring it, hit me up.
I'll second that. If you get near Aarhus in Denmark let me know so we can do this: http://youtu.be/sd9TlXY078A  What is the price in the US |
|
|
|
Nice ... good vid also.
So what are memory protections like on that private key once it has been imported? It seems like you can load any amount, up to total held in that address, so is it recommended to send remainder to new cold storage key or ... ?
The private key is only in memory while the transaction is created. As soon as the spend workflow is done the private key is gone. If the amount is not maxed out the remainder is sent back to the cold storage address. There is no option to specify/scan an alternate change address. If an attacker can get to the private key in memory in the short time where it is present there is not much gained by sending the change to another address. If the private key is obtained it is already too late. To make this really secure you should use a dedicated device with the single purpose of doing cold storage spending, with nothing else installed. |
|
|
|
If I don't spend all the money, will change go back to the paper wallet?? Just want to double-check. Yes. |
|
|
|
Bug report: When attempting to send from this address: https://blockchain.info/address/1K3bMZ7SvkzoGZTYD5EpYPKbN8PPQKqidGwhich currently contains 2.48345024 BTC and hitting the "max" button to send everything it will only allow me to send 1.91515024 BTC Any attempt to enter any larger amount will be denied with "insufficient funds to pay fee". This address contains only a dozen outputs and a fee of 0.5683 BTC (over 400 Euro!) seems a bit high to me. Edit: is it maybe the unusual pay-to-pubkey format of some of the unspent outputs? These were generated by Schildbach when It moved coins internally between 2 addresses (this is a key that was formerly used in my Schildbach wallet and was imported into Mycelium). If this is the case then you need to fix it so that it can use these types of outputs as transaction inputs. You will need a different type of signature script for these inputs, only the signature and not the pubkey because the pubkey will come from the output script, see wiki: https://en.bitcoin.it/wiki/Script#Standard_Generation_Transaction_.28pay-to-pubkey.29Edit2: This will most likely happen more often when people start importing keys from Schildbach. These pay-to-pubkey transactions are generated by Schildbach when it does its emergency transactions, when funds are sent to an old address that was flagged as insecure (due to the Android bug) it will immediately sweep the funds into a new secure address and it will use pay-to-pubkey for it. All these pay-to-pubkey transactions you can see arriving in my above address result from this. sounds like a bug to me. the fees should not be that high. we will try to reproduce it, but i don't expect a fix extremely soon (realistically, i'd work on that week 20.1-24.1) as a workaround, i'd recommend importing the key to bitcoin-qt and consolidating the funds there. Mycelium does not support using pubkey outputs. It was never a priority as next to nobody is using it these days. So what you see in the UI is the maximum you can send from the address while paying a normal sizes fee. The rest will be left untouched. This does not mean that the rest will be the fee, but I agree that it is a bit unclear. If you click OK (without Send) you will see the fee that it calculates. All this said, we probably should support pubkey outputs. In 2 1/5 years of BitcoinSpinner / Mycelium pubkey outputs have never been requested. |
|
|
|
Can you ask how blockchain.info does it?
piuk very seldomly responds. My guess is that they go for a happy-go-lucky approach. If you search for stuck transactions and blockchain.info you get quite a few hits. |
|
|
|
I got this from the NEFT marketing guy in CA. In San Francisco the two best merchants are the Jug Shop and Bryans Market. In Marin they can go to Mill Valley Market and Woodlands in Tiburon. In Santa Rosa they can go to the Bottle Barn. |
|
|
|
I second this. Sometimes I just want to move funds between my own accounts. Besides, with merchant services options coming out soon, you guys are having to work on custom set fees, anyway, right?...
I am not certain what you mean by "merchant services options". Where the merchant requests the transaction, the transaction is signed by the sender and transferred to the merchant, and the merchant verifies it before broadcasting it to the network. Thus the merchant is able to demand a certain custom sized fee, and decline a transaction if the fee they want is not included. Regarding zero fees, why not do what blockchain.info does, and allow zero fee transactions, and if they don't get confirmed after 24 hours, scrap the transaction and make the coins spendable again. Is it so easy to scrap a tx? If it's in everyones mem-pool, would it likely get replaced by a double-spend one with a fee? Correct. The a relaying node (or miner for that matter) will regard another transaction using the same inputs as a double spend. The transaction has to get removed from the memory pool of receiving nodes before you can send out a version with a higher fee using some of the same inputs. This happens naturally over time (as nodes get rebooted) but it is hard to tell when that will be. So basically some of your inputs are stuck. (real) Transaction replacement was part of the original Bitcoin protocol, but was disabled pretty early on (if it was ever fully enabled). |
|
|
|
I am not certain what you mean by "merchant services options".
Where the merchant requests the transaction, the transaction is signed by the sender and transferred to the merchant, and the merchant verifies it before broadcasting it to the network. Thus the merchant is able to demand a certain custom sized fee, and decline a transaction if the fee they want is not included. ... Ahh, yes, the payment protocol. We cannot really rely on it right now as it is not really used much yet. Going forward this is likely to change. |
|
|
|
Is there a way to get rid of the "backup missing" message?
The "backup missing" message is shown as long as you have a private key which was created by the wallet and which hasn't been backed up with verification. Private keys imported (e.g. from paper) are verified by default, as you have proven to have an external source (backup) of the key. One way to get around this is to create a private key by external means and import it to the wallet, and then delete the automatically generated initial key. Why do you need to print off the PDF and then scan it in to verify? I don't want to make a print of it.
You don't have to print the PDF. You can scan it from the display of your computer. The reason for verifying is that you may have made a mistake when you made the backup. - The PDF send to a wrong email address, or you accidentally deleted it before printing ...
- The password not written down correctly/readable
A backup that does not work is worse than no backup at all, as you think you are good. More coins have been lost due to lack of backups than due to theft. We really want to help users not loosing coins. |
|
|
|
Any updates on message signing with mycelium? copy/paste buttons on the gui would be handy too (for message signing, and generally copying addresses)
Message signing is in the works. |
|
|
|
I second this. Sometimes I just want to move funds between my own accounts. Besides, with merchant services options coming out soon, you guys are having to work on custom set fees, anyway, right?...
I am not certain what you mean by "merchant services options". In the fee space bitcoin-qt 0.9 will have some changes for getting a "fee market" going, which will calculate fees dynamically depending on fees paid in previous blocks. We will implement something along those lines. Here are some of my thoughts on this topic: https://bitcointalk.org/index.php?topic=166302.0 |
|
|
|
Fee
The fee is calculated to be 0.0001 for each 1000 bytes of transaction size. This way the fee matches the minimum relay fee enforced by bitcoin nodes. If you go below that you risk that your transaction gets stuck in the network and never confirms. If we allow users to go below that, and blame it on us when their transactions get stuck. I totally get your point. Nonetheless, can you please (only in Expert mode, and perhaps with the information from your quote above as warning) add the possibility to customize the fee? How about: in Export mode by default still use 0.1 mBTC per 1000 bytes, but make it editable, and mention "recommended fee = xxx" in the edit fee screen/popup. There are many occasions where I really don't care if a tx gets somewhat delayed or not (when transferring funds to myself, for example) and in Expert mode, one can be assumed to understand the difference. The thing is that your transaction may not only "get somewhat delayed", it may never confirm at all. By paying 0.0001 for each 1000 bytes of transaction size (round up) it stays above the minimum relay fee required by nodes relaying the transaction to miners. Those are the rules of the network. If we don't follow those rules users will experience transactions getting stuck. "freeing" your coins after that can be a nightmare, there are many threads on this forum on this topic. This will hit us (the developers) with a slew of angry users, as they will blame the wallet, and I really hate having angry users. Fees in Bitcoin are quite complex and most users who consider themselves experts do not understand how it works. All that said there is something we can do. The rules of the relaying nodes are not there to guarantee the miner some mining profit. The rules are there to limit transaction spam... a DOS attack filter, that prevents someone to send transactions to himself indefinitely, filling up the memory pool of relaying nodes. When the relay rules were introduced a portion of the memory pool / block size was reserved for what is called priority transactions. In short a transaction gets a priority according to the "age" of its inputs. If the "age" is sufficiently "old" ( details here). Nodes will relay a priority transaction with a zero fee. Relaying does not guarantee inclusion in a block, and if the network continues to grow without the 1 MB block limit rising (or some other technical advancement) then the fees are bound to rise above the minimum relay fee. Until now Mycelium has not considered zero fee high priority transactions. Something to work on. |
|
|
|
Anyone know, is it possible to get this in the USA?
Good news! I've been informed that NEFT is now "available in California" and that they are "looking to begin in Las Vegas" this month. These do have the Bitcoin logo on the barrel (as they were on the ones at the Bitcoin Conference in San Jose). I didn't get the name(s) of merchants selling NEFT, ... but I believe BevMo was supposed to be one. I'll solicit help from some SoCal Bitconers to learn where NEFT can be purchased, but if anyone following this thread already knows, please share! I have a direct line to the owner of NEFT  In LA, Jons Market - 6 Locations: - House of Liquor
- Anush Bakery
- Remedy Liquor
- Joe’s Liquor
- Eden Wine & Spirits
- Super Meat & Liquor
And this guy sells everywhere in LV - You can contact him directly. When buying in Bitcoin you get 10% discount! Stefan Manchev VP International Affairs Rebel Wine & Spirits 4132 S. Rainbow BLVD. #150 Las Vegas, NV 89103 Direct: 702.420.0284 And here is the bomb: In one month I will stop selling Neft for fiat to anyone - only for BTC.  Stephen, as far as I remember you are located in California... knock yourself out |
|
|
|
What are the requirements to get the  "bitcoin expert" tag? *ping* |
|
|
|
Christmas is over, and I hope you had a good one! Would BIP32 be an option for mycelium?
I really don't like the single address (well, multiple single address) approach any more. It's just not good for anyones privacy.
I know this would be a huge change, both on the usability side as well as on your server infrastructure, but is it something you have considered and why did you decide against it? Are the reasons related to the bitcoincard somehow?
BIP32 is part of the plans for Mycelium, but as you say it is a big change, and we simply haven't gotten there yet. Our focus right now are features that allow new users to discover bitcoin and make it easy to get some coins (get their feet wet). Andreas and I working on Mycelium full time, but we can see that we really need some more man-power, in particular developers. So if you are a skilled developer who is not afraid of Java and Android, and live in the Vienna neighborhood, send me a PM. |
|
|
|
|
Phin, was that you? LOL
Link please.
|
|
|
|
|
Use Mycelium for Android.
|
|
|
|
|
Show Posts
