In such cases its best to report a bug via the app, because that includes your logfile and (optionally) a dump of your wallet. The longer you wait with this, the smaller the chances we'll find the issue. For feature request its best to use the issue tracker at http://code.google.com/p/bitcoin-wallet/issues/listIf you reset the blockchain, your outgoing stuck tx should be either gone or confirmed - depending on if they made it into the blockchain. Either way, the Bitcoins will not be lost. |
|
|
|
Ok, so I don't need to sync it regularly then? It will do so every day, automatically?
Won't that be a problem for people with limited data plans? Doesn't Bitcoin Wallet need to download all transactions to find which ones are relevant to my wallet?
It synchs regularly, interval based on how long you did not use the app. It also triggers a synch when you plug in a a charger, which in many cases means you're also on WLAN. If you don't send or receive coins, it basically just synchs the headers (12 kB per day plus some overhead). Plus transactions, if you have any (~500 bytes per tx). If that's harmful to your data plan, you better disable mobile data entirely. |
|
|
|
|
And on to the next version 3.10 RC in the beta channel and on the download page...
It "embeds" the fee calculator directly into the send and request coins forms rather than needing to go through a separate dialog.
One positive side effect of this is when you scan a Bitcoin request (QR or NFC) including an amount, you'll immediately see how much that is in your local currency before you press send.
|
|
|
|
|
I yesterday released version 3.09, which - thanks to Matt and Mike's work on bitcoinj 0.9 - calculates transaction fees correctly. For most transactions, that means a fee of 0.0001 rather than the flat 0.0005 which was hardcoded before.
|
|
|
|
|
Pro7bit, thanks for your suggestions!
Regarding the send and request buttons, without labels they were not visible enough (even for experienced users). So for "normal" sized screens, I decided to move them to a bottom action bar so I can label them. On "small" screens I kept them in the top action bar for the exact reason you are showing in your screenshot. Now, the issue is that your phone is classified as "normal" sized rather than "small". This is something your device declares, the app has to rely on that information. If you have installed a custom ROM, you should probably change this - it affects other apps as well.
I planned to reduce the size of the wallet address part together with the introduction of HD wallets. The "from address" will also go away at the same time, its a concept that is not reliable (some even say it does not exist). Basically, with HD wallets I want to switch from "one address per wallet" to "one address per payment" (which is the original idea by Satoshi).
Regarding the blockchain progress, the idea of the changes is that you only should care if there is a problem. A blockchain not up to date is no problem, as long as its in the progress of catching up. So it only shows error states (no network, out of storage, ...). A special case is a replay, during which you cannot/should not send payments. Which is why during a replay, progress is shown.
Mike, there is no such thing as a "7 days" threshold. There is a one hour threshold though, everything below counts as fully up to date.
|
|
|
|
|
Are you on 3.09 or still on 3.08? 3.09 uses bitcoinj 0.9 and calculates fees using Matt's code. I did not change the SendRequest defaults, which typically results in 0.0001 BTC fee. I write about this on the bitcoinj mailing list.
|
|
|
|
Well it obviously worked, but the bounty was never awarded.
Wasn't it? So who's sitting on all the money now? The people who pledged, except some who donated (part of) their share. There was no intermediary involved. |
|
|
|
Will you ever add a sync-on-wifi-only option?
Yes, please! I just tried the Android app and this is the biggest issue I have with it. There seems to be no way to turn it on and off, other than force stopping it. I would love to be able to tell it to only connect to peers and sync up when on Wi-Fi, or better yet, have an option there in the app to let me turn it on and off manually, so that I can have it sync up only if I really want to (and am willing to let it burn through my data plan). Very nice app. I'm also hoping I can move its data storage to the SD card, but it seems to have that option grayed out in the "App Info" screen of the application manager, unfortunately. Is there a way to do this? Data usage of Bitcoin Wallet is negligible. If you want to spare your data plan, you should switch off mobile data and/or roaming in the Android settings. |
|
|
|
|
I have uploaded 3.09 RC into the beta channel.
Main changes are
- Proper calculation of fees. In many cases, this means only 1/5th of the previous fee (0.0001).
- French translation was updated.
- It uses bitcoinj 0.9
If you want to participate in testing, follow the instructions in the original post.
|
|
|
|
I got a Samsung Galaxy S3.
I think the years when iPhone was the clear favourite is over - it's much better than my old iPhone 4 (which my neice will get as a freebie)
+1 (except for the implicit statement that iPhones have ever been favourable :-) |
|
|
|
|
Great to hear! Which phone did you get?
|
|
|
|
I have updated the BlackBerry version to 3.08 last week, you can download the latest version here: http://code.google.com/p/bitcoin-wallet/downloads/listDue to a bug in the BlackBerry AppWorld crappy admin interface, I cannot upload the update to AppWorld for now. Changes: 3.08 * bugfixes 3.07 * make request and send coins action buttons more visible * stay connected a little bit longer if there was transaction activity on the wallet 3.06 * merge peer monitor and block explorer into network monitor * Hebrew translation 3.05 * backup reminder for first-time users 3.01-3.04 * some small improvements and bugfixes |
|
|
|
People pitched in a pretty hefty sum as a bounty to the first working Android app. Perhaps that would be one way to go for Windows Mobile users as well? It's quite a big undertaking to build a mobile wallet, and what better way to reward the developer than with Bitcoins?
Well it obviously worked, but the bounty was never awarded. |
|
|
|
Mobile wallets are badly needed. I am a Bitcoin evangelist and go around and sell small parcels of Bitcoins (like 0.1 BTC ) for no profit just to promote Bitcoin, increase the user base and remove the barrier of entry (which was none for myself but, you know, some people prefer to take baby steps) . My life would have been much easier with mobile wallets on WP and iPhone.
For iOS, we are the wrong people to address. There would have been a wallet for iOS already years ago, but Apple banned them. Tell people they have bought into the wrong platform. For Windows Phone, the user base is still very small and there is no reason it will grow significantly. That's probably the reason some apps do not exist. Windows Phone users are early adopters, similar to several years ago when people were using Android 1.x phones. |
|
|
|
|
It's now in the beta channel. Whoever would like to participate, see the original post that started this thread.
|
|
|
|
|
I'd like to postpone discussions about both the "stalled" and the "progress bar" for now.
First, I'd like to deal only with the fallout from the decision to move blockchain progress away from the bottom of the screen and into the same space wallet balance lives in.
I decided to try out hiding progress entirely if its not a replay. Because in this case it does not really matter to the user, he can send and receive even if the chain is not up to date. Note its possible to watch blockchain progress in detail in the network monitor. The change will go into 3.08, which I will put into the beta channel probably tomorrow morning.
|
|
|
|
I was auto updated.
When exactly did that happen? I'm asking because I promoted the beta to a "staged rollout" for 20% of the users just today, so it isn't clear if you received 3.07 as a beta or a production version if you received it today. The higher visibility of the buttons is useful, but I'm not keen on the change to how "Synchronizing with network" is displayed. It's weird to have the balance not be visible until synced, also, putting the label big up there emphasises its problems. Namely that it tends to show "Synchronization stalled" for a few seconds at the start whilst the network connections are being brought up which is confusing, and there's no obvious indication of progress if your network connection is slow. It should really be using a more standard progress bar type arrangement, and the bottom of the screen was fine for that.
But generally I don't like the way the balance is hidden until sync is done.
Yeah its not ideal. The reason I was putting the message into the same space as the wallet balance is because since some months, I've already hidden wallet balance while replaying, so the space was kind of unused. Sure, updating the blockchain is not always the same as replaying, but its not that far off either. One option to fix this is not showing blockchain progress at all as long as it is no replay. In most cases, it finishes very fast anyway so users won't miss it. Downside is, if you replay your wallet without the app knowing its a replay (e.g. because of an address import) you will see an invalid balance. Another option could be layering the message on top of the balance as long as it's no replay. This way, it would be clear that the balance is probably not correct until the layer on top disappears. Progress bars don't work, and the best indicator is that bitcoin-qt abandoned their old blockchain progress bar in favour of more or less what Bitcoin Wallet does. The "stalled" indicator is an unrelated issue. I could raise the threshold, but then again we could also work on connecting to peers faster. 5 seconds is a long time. |
|
|
|
|
I just uploaded 3.07 RC. If you want to participate, follow the instructions in the original post.
I'd appreciate feedback on any new problems with the app, and also please can you tell me if you previously have subscribed to the betas (3.05 RC and 3.06 RC), did you automatically receive 3.07 RC or do you need to re-subscribe?
Changes for 3.07:
* make request and send coins action buttons more visible
* stay connected a little bit longer if there was transaction activity on the wallet
|
|
|
|
|
Die Idee mit dem read-only wallet verfolge ich seit rund 2 Jahren. Bitcoinj (das Framework auf dem Bitcoin Wallet basiert) kann auch schon seit einiger Zeit mit read-only keys umgehen - ansehen kann man sich das z.B. in MultiBit.
Ich habe read-only wallets dennoch bislang nicht in Bitcoin Wallet implementiert, weil das ohne das Sharen von Keys keinen Sinn macht. Und das Sharen von Keys ist derzeit inhärent unzuverlässig - ich kann davon nur abraten, es sind schon viele Bitcoins dadurch verbrannt worden (übrigens unabhängig vom Client, also auch bitcoin-qt). Die Erfahrung, die pat1900 gemacht hat, ist nur ein Beispiel (wobei ganz erklären kann ich mir das nicht - wenn der Key Birthday korrekt gesetzt ist wird schon die ganze Blockchain berücksichtigt).
Mit HD wallets wird das Sharen eines Wallet möglich, und ich nehme an dass zu diesem Zeitpunkt entsprechende Funktionen zum einfachen und sicheren "Pairing" in alle Clients eingebaut werden. Dann machen auch read-only wallets Sinn.
|
|
|
|
|
@phelix: Watch only wallets are planned exactly for this usecase. However, HD wallets should come first, because sharing keys will only be possible with HD wallets in a reliable way.
@2weiX: For now, I would put the backup file on an USB stick and put that into a safe. HD wallets will make it possible to write down the master key (more secure than printing btw.)
@stan.distortion: Thanks for pointing out the thread, I replied there.
|
|
|
|
|
Show Posts
