Thanks for your reply Jim - My thoughts exactly. Regarding Android clients (on topic), I was curious if an alternative approach to your (pending, proper) solution would be useful for Android wallet developers.
I may be implementing my simpler approach for the SatoshiRoller app (using cipher streams).
It would be only of limited use. Bitcoin Wallet updates the blockchain in the background, while the app is not "running". It would need to ask for a passphrase just for that.
|
|
|
Jouke, can you report bugs in the issue tracker? Otherwise, chances are that they get lost in the noise.
|
|
|
Bitcoin Wallet uses bitcoinj 0.6 which includes bitseed.xf2.org in the list of hosts to query. Is your issue reproducable? Can you look up in the log for "DNS lookup for xxx failed." messages?
I just tried the app again with a wireshark monitoring session on the router.. its definitely only querying the 3 domains listed in my original post.. bitseed.xf2.org is not being used. Of the three it is trying it is getting back failure on two and response of 0.0.0.0 for the other. I suspect Mike is correct, it could have something to do with ipv6 addresses in the response. Would be nice if I could specify my local node (desktop) as a startup node and get further nodes from there. Did you also look for the messages in the log? If it is not even querying bitseed.xf2.org, how can it choke on an ipv6 answer (no request => no response)? Perhaps it would be best to open a ticket on the bitcoinj bugtracker: http://code.google.com/p/bitcoinj/issues/list
|
|
|
Will you send Bitcoin Wallet to BlackBerry App World?
At some time I will (although I've got no idea if they accept payment apps into their store). But before that happens, a testing process for not yet released versions needs to be established. So I wonder if someone was able to install the .bar I put up on the downloads page, and how he did it. Unlike Android, I've only very little knowledge about BlackberryOS.
|
|
|
We need to make bitcoinj use hard-coded seed nodes and addr broadcasts. It's a known issue that it's too reliant on DNS seeding to get started.
For several months I have sitting on a private branch a modification that persists node addresses across restarts. However, I never switched it live because the current bitcoinj API restricts too much how the querying works.
|
|
|
After doing some network traffic inspection it appears the app is using 3 of the 4 DNS seeds listed on the wiki:
dnsseed.bluematt.me seed.bitcoin.sipa.be dnsseed.bitcoin.dashjr.org
But not bitseed.xf2.org
Bitcoin Wallet uses bitcoinj 0.6 which includes bitseed.xf2.org in the list of hosts to query. Is your issue reproducable? Can you look up in the log for "DNS lookup for xxx failed." messages?
|
|
|
I'm not sure if this has been addressed, but I think I accidentally sent bitcoins to an old address I had with this app. I have the prodnet.wallet fileand I was wondering how I can import the keys now that it uses a different wallet file.
If your wallet file is really named like you said, the wallet was not created by Bitcoin Wallet but by a different app ( Bitcoin Android). It's not being maintained any more and uses a very old version of bitcoinj. You can try this guide to extract your private key(s): http://gary-rowe.com/agilestack/2011/12/28/how-to-recover-lost-bitcoins-from-an-android-wallet/
|
|
|
Maybe a nice feature would be to be able to import private keys trough qr-codes This is a planned feature. However for this to be secure, I need to integrate the QR code scanner into the app rather than relying on an external app plus the Android Intent system to securely transmit data. I'm working on it. Also, can you give me examples of existing Bitcoin apps/web pages that export private keys via QR? Which format(s) do they use?
|
|
|
What are the timestamps in the keys-file? Are they necessary?
The timestamps are the date of the private key created, or the first appearance of the corresponding address in the block chain. They are optional and are meant only for the importer to be able to catch-up the blockchain faster. If you leave it out, the whole blockchain needs to be scanned for the imported key(s).
|
|
|
Very nice project! If this hardware would be designed as an ADK (Android Accessory Development Kit) device, it could be connected to virtually every phone with at least Android 2.3.3 installed and be used with Bitcoin Wallet. I think ADK support is optional, so the same device could be connected to a PC as originally intended. I'd be happy to implement the necessary software support on the Android side!
|
|
|
I just released 2.31 final to market. So key import/export is now available to everyone. Well mostly everyone. I had to raise the minimum requirement to Froyo (Android 2.2) and above.
|
|
|
Well, the problem is that I use Windows (XP). Exporting the key to SD Card is no problem. The program also asks for a password to encrypt the private key thus exported. The point is: what should I do when I copy this encrypted private key to my Windows machine? I don't think that a bash with openssl commands will be at my disposal in windows.
There is OpenSSL for Windows. However, I can't help you with that since I use Windows only for gaming. You can try importing the file into Multibit, it's also available for Windows. Background: as with 2.23, I am having some trouble with 2.3 to get a fully updated blockchain in the Android app. Updating the chain is flacky (also after full reset of blockchain). It took me all day today to get it updated by restarting the app and numerous FC's. Now that it is updated, not all transactions are shown (compared to blockchain.info). Don't worry, your e-mail inbox is probably full with my crash reports Your device only assigns very little memory (32 MB) to each app. Thus, you are experiencing lots of out of memory errors. Try uninstalling all apps you don't really need. It is still the most gorgeous UI I have seen for an Android app so I hope the wrinkles will be ironed out in the future.
The plan is that memory requirement will be lowered considerably by receiving only transactions that are relevant to your wallet. However, this is still some time in the future (needs enhancements of protocol and upgrades of Satoshi clients), so your best bet is upgrading to a decent phone like the Galaxy Nexus.
|
|
|
Is there a guide on how to work with imported/exported keys? For instance, what can I do with an exported key, how does the password relate to that (the private key is encrypted when exporting it from the Bitcoin Wallet app, etc). Will be useful for n00bs like me I added a little bit of info to the README (see FILES section). The main use case is backups, which should not need much explanation. On devices with SD card, export to your SD card directly or if external storage is in fact internal, pull your backup via USB cable. Importing is the other way round (-: For many people, the usecase will be a wallet shared between two devices. However, I advise against such a setup (due to the risk of creating invalid transactions). For this reason, I have not documented it.
|
|
|
- Cannot say about installs with actual BTC in them, as I would feel myself bad eavesdropping on peoples "bank accounts".
Adding a report-balance functionality to Bitcoin Wallet would indeed be more than rude so I hope that what you actually meant to say is that you do not have these numbers. Yes, I don't have these numbers and no reason to collect them.
|
|
|
@gizmo Instawallet is added twice to the poll.
|
|
|
Thanks for your numbers. Here are Bitcoin Wallet numbers: - Total installs to date: 18016 (plus several hundreds from the downloads page)
- Active device installs: 5513
- Cannot say about installs with actual BTC in them, as I would feel myself bad eavesdropping on peoples "bank accounts".
|
|
|
what IP do you get for code.google.com?
code.l.google.com 173.194.69.113 Are you able to clone other repos? And other repos from different services (e.g. github)?
|
|
|
Bitcoin Wallet 2.23 fixes bugs and is based on bitcoinj 0.6. The main user-facing feature is pictured in the image. You can watch pending transactions propagate through the network. As peers report the transaction, a grey circle grows. Finally, it is replaced by the well-known green block chain confirmation indication. For the sender, this helps determining if a transaction was actually sent. For the receiver, confidence in the validity of the transaction builds, as each peer should validate each transaction. However, this is just an indication. Nothing beats the validation power of the block chain. Install/Upgrade Bitcoin Wallet from Google Play: https://play.google.com/store/apps/details?id=de.schildbach.wallet
|
|
|
Works at my place. Just try again?
|
|
|
|