Look up "reproducable build". Its partly possible. Basically, you need to make sure to compile in the same environment for all people participating. Then make sure that all file dates in the APK are the same (zero?). Now, you can compare everything except the signature. The signature itself will always be different.
|
|
|
Currently, it only backs up the addresses you have already created.
In future, it will have BIP32 deterministic wallets. You only need to backup the once, immediately after starting the app for the first time.
That's a shame. I don't like reusing addresses (I.E. change back to the same address, or, multiple payments) for the sake of it being hard for me to manage what payments are what (One address/payment is a lot easier), so, this wallet is unusable for me at it's current state. Hopefully when you come out with this feature it'll be usable. Is there at ETA (Time/version)? Or, is it just in limbo currently? The project is open source and free software. You could have coded the feature already 3 years ago. Heck, you could even have submitted a patch by now! Why didn't you do? It's best to follow progress on HD wallets on the bitcoinj mailing list. Mike has recently estimated "later this summer".
|
|
|
We had to switch away from the textual backup format that was agreed with MultiBit 3 years ago. It doesn't support encrypted keys, HD wallets, read-only keys etc.
I think MultiBit will also switch away or has already done so. They should be able to open the bitcoinj wallet format directly though. Check with Jim if you want to try.
|
|
|
It's the bitcoinj wallet protobuf format. You can access it e.g. with "wallet tool" that comes with bitcoinj.
|
|
|
Currently, it only backs up the addresses you have already created.
In future, it will have BIP32 deterministic wallets. You only need to backup the once, immediately after starting the app for the first time.
|
|
|
I believe there is currently none. Patches welcome! I assume they should go into bitcoinj.
|
|
|
I'm afraid importing wallets/keys is not supported, as this is inherently insecure. I suggest using a standard Bitcoin transaction to move value.
The typical install-time footprint is around 10 MB. The app itself is only 2 MB in size.
|
|
|
Ok, I understand. That feature is planned.
|
|
|
The app updates exchange rates every 10 minutes.
|
|
|
Thanks for your suggestion. To clear things up, can you define "record"?
|
|
|
The altcoin forks likely need forked versions of bitcoinj as well. I suggest reading the build instructíons or asking the author.
|
|
|
Based on the last three years of history your coins are pretty safe. Still the app is not meant as a long-term "store of value". Keeping about 50 EUR in the wallet sounds about right to me, but of course it depends on your personal circumstances.
Thanks for spotting the bug, I just fixed it for the next version.
|
|
|
The limiting factor is not really the total number of transactions. What's more relevant is how many people are being paid by one transaction. A standard Bitcoin transaction only pays you. Mining and gambling payouts tend to pay thousands of people at once, and that is something we didn't really plan for. We're working on it.
|
|
|
The backup format has not changed since 2011. But indeed, it will change in near future. However, you will still be able to import old backups. Even if the app vanishes in a puff of smoke, you can decrypt your backup using openssl and import the private keys into bitcoin core by hand (its using "sipa" format). See the README about the openssl command line.
|
|
|
Follow the checkout instructions on the link I gave you, switch to the "release-0.11" branch or the v0.11.2 tag, then do a "mvn clean install" in that project.
After that, you issue with the bitcoin wallet build should be gone.
|
|
|
Please use "mvn clean install android:deploy" to deploy to your device. Or use ADB, as documented in the README.
I've given up on using the Eclipse "run" target for Android apps a long time ago...
|
|
|
|