1. Bug report: The wallet may stop response when the Bitcoin info window is open. This usually happens in minutes when synchronizing, and takes much longer when the block chain is up to date.
2. Suggest: General user (except the claimer, the miner, the exchange platform) who do not need very high safety level could use a option to completely do not synchronize with Bitcoin block chain. In such condition, the transaction outputs with Credits claimed from Bitcoin (or atomic swapped from Bitcoin in future version of Credits) should be marked immature before enough conformations of the claim transaction, for example, 1000 conformations.
Of course, I do think the current optimization on disk usage and block parsing speed should be on the highest priority.
Thank you very much for the input.
1. Very good that you report on this. I'll keep my eyes open for signs of that type of locking in the new (unreleased) version.
2. Good idea. I've been thinking about it myself, just not sure exactly how it should be solved, since full validation of the Credits blockchain requires the Bitcoin blockchain as well. But maybe a flag to disable that whole part of the validation. I will consider it and try to find a good way to implement it.