Closed GoogleCodeExporter closed 9 years ago
Is this a part of doing support for multiple wallets? I'm not sure that's the
most valuable feature I could want in a mobile app at the moment, but even if
you disagree, removal of wallets isn't supported because multi-wallet support
in bitcoinj in general is quite rough. If you remove a wallet then it can miss
new blocks or transaction broadcasts. When you re-add it, it won't
automatically catch up.
Original comment by hearn@google.com
on 24 Jun 2013 at 8:11
The usecase I described was removing wallets entirely, so missing transactions
would not be an issue.
Yes, I started implementing multi-wallets yesterday, because too many features
depend on it. I'm aware that I cannot currently "close" a wallet and re-open it
later due to the limitation you described but understand based on your earlier
comments that support for this is planned (and we already have
Wallet.lastBlockSeenHeight/Hash).
Original comment by andreas....@gmail.com
on 24 Jun 2013 at 8:23
Planned eventually yes, but I have a list of other things I want to do first
(like the memory improvements). Jim has solved some of these issues in
MultiBit, perhaps he can merge his code upstream?
What features depend on it? I'd really like to see the business map happen at
some point .... I might try and manually run an assurance contract for its
development myself.
Original comment by hearn@google.com
on 24 Jun 2013 at 8:45
This issue was closed by revision 6a39af30c4be.
Original comment by hearn@google.com
on 11 Jul 2013 at 2:32
Original issue reported on code.google.com by
andreas....@gmail.com
on 23 Jun 2013 at 3:07