Hopefully, the Bitcoin Foundation takes care of the various trademarks that have already occupied the name "Bitcoin".
Otherwise, it may have to rename itself soon...
|
|
|
I have the android wallet and I must say that I'm not very happy with it's performance. It works well, but when it starts to download the blocks, my whole device freezes up and I am unable to do anything for quite a while. I have an app watcher and it tells me the app will take 80-90% of a processor power for a while. I have a Samsung Galaxy S2...
Is your device mostly caught up with blocks or is it coming off a fresh start that its downloading the whole chain? it is mostly caught up, but downloading even half a day worth of blocks freezes the device for a minute. It's not always, but sometimes it gets very slow, or totally frozen Can you take this issue to the bug tracker? http://code.google.com/p/bitcoin-wallet/issues/list
|
|
|
Why does bitcoin-qt show transaction time stamps as the time it received/processed the block rather than the time the transaction happened?
I also find this very irritating. Has this issue been discussed or is there a bug report already?
|
|
|
It's great to see a new Bitcoin client, especially one that uses BitCoinJ.
Nyhm, you said you're using BitCoinJ 0.5.2 - do you add any patches on top of that? I'm asking because plain BitCoinJ cannot do fees yet. Without fees, lots of users will see outgoing transactions not confirming.
|
|
|
Yes, sure, I was thinking of something like that.
After being pushed back and trying again - this time with money in your hands - you'll be granted access. Similar to HTTP authentication mechanisms.
|
|
|
I think there should be a way for the user to hand a signed Bitcoin transaction directly to the webserver requesting the coins. Because there is no guarantee that even a non-confirmed transaction will ever arrive. Perhaps the sender does not even have Internet access (the web page could be on a local LAN only).
|
|
|
Also am 2.8. wieder?
Genau, quasi über-über-morgen findet der Stammtisch wieder statt. Ich selbst komme auch erst um 22 Uhr, aber ich nehme an dass die meisten schon kurz nach 19 Uhr eintrudeln werden.
|
|
|
Is this patent a threat to the QR code function in Bitcoin Wallet?
If Australia has something like prior art, this patent will be invalid (at least the payment part of it).
|
|
|
In any case, it would be a good idea to be able to encrypt the private keys.
Encrypting private keys in the wallet is already underway in BitCoinJ. It will probably take a cycle for it getting into the apps. if your phone is rooted (and I would think that the intersection between people rooting their phones and people using bitcoins is not empty), another application is more likely to be able to access the wallet-protobuf content.
Why is that? To my understanding, apps would still need to expoit security bugs, and the mere existence of them is unrelated to wether you have rooted your phone or not.
|
|
|
If your phone is rooted, you can copy your wallet from /data/data/de.schildbach.wallet/files/wallet-protobuf
If you can't root your phone, I would need to send you a special version that has the ability to copy your wallet to your sdcard. However, this is a quite dangerous feature, as all other apps you got on your phone can steal your wallet/private keys from the sdcard easily.
|
|
|
Nur so als kleine Erinnerung: Morgen (13.7.) startet der Bitcoin Hackathon!
|
|
|
Sorry, but I have a specific desire to copy my PC wallet to my phone and use it.
You'll probably never be able to copy wallet.dat directly. The closest you can get is exporting and importing the private keys and rescan the blockchain. This is currently not supported in Bitcoin Wallet but maybe will in future (patches welcome). If you switch your PC wallet to MultiBit, that wallet format (protobuf) is compatible to Bitcoin Wallet. You'll need root on your Android device to push the wallet though. Whichever route you take, be careful. Its easy to unintentionally double-spend with the same keys in two wallets.
|
|
|
The blockchain never completed with this application. Now I think it was be unrealistic to hold 2gb on my phone. Which version did you try (or how long ago)? It does not hold 2 GB but only approx 20 MB (headers only).
|
|
|
Fornit asked me to post download statistics here. As of today, Bitcoin Wallet has been installed 12640 times (not counting re-installs or updates), but only 3588 are still active.
|
|
|
More comments:
What's the diagonal cross right to the address field supposed to do? If it's a shortcut for clearing the field (to enter a fresh address), move it to inside the field like all modern UIs do.
For generic operations like "clear field", use standard icons of each platform. Don't invent your own icons. If you need to (for example because it is Bitcoin specific), follow the style guide of each platform. On Windows though, probably all hope is lost :-)
IMHO, the ellipsises ("Enter a Bitcoin address..." + "...and amount") do not work well, because it adds an unnecessary textual reference. I'd try "enter Bitcoin address" and "enter amount".
|
|
|
The first row column of image buttons looks like it meant as icons for the text fields to the right. That's irritating IMHO.
I'd try to get rid of them: - Expanding the UI should go into the window title. Actually is there any difference to the maximize window button? - Options should either go away or can also go into the window title. - Fetching addresses from the address book (that's what the upper left image button is meant for?) could perhaps be moved next to "copy address" (which should also be an image button).
Contrasts are much to harsh. Get rid of the black background as long as your text fields have white background.
That coin in the background does not work. It just distracts from the UI.
For mockups, try to insert actual values. For example, how does the interface look like if your balance is BTC 12.50034563?
That said, it's good to have non-intrusive UI on Desktop PCs as well. Spending is mostly an implicit activity and I'd like to not be distracted from what I am actually doing.
|
|
|
Bitcoin-qt offers a "sign message" dialog. It contains the warning
"Be careful not to sign anything vague, as philishing attacks may try to trick you into signing your identity over to them."
Can anyone give an example how such an attack would look like? I currently don't understand why this feature is present in bitcoin-qt (sending messages is something I use eMail or Jabber for) and also which attacks are possible because of this feature.
|
|
|
|