Save and load private keys about sia HOT 1 CLOSED

I am working on the wallet code and will handle this.

The wallet code has changed in a very, very substantial way. It's been tough to design and we ended up with more features than we needed, but most of them were by consequence of already needing other things.

• Calling CoinAddress() will give you a new coin address every time. The wallet will be able to remember which outputs belong to it.
• Calling FreezeCoins() (now renamed AddTimelockedRefund()) will remember how to spend the coins and add them back to the balance once the timelock runs out. FreezeCoins will also generate it's own keypair, unique from all the others to help with privacy a bit.
• Wallet no longer needs a State, it just needs a list of blocks that have been added and removed since the last call. This does mean that there's some redundant storage in the outputs, but it should be pretty minimal because the Wallet will only be storing outputs that it understands how to spend
• All mutexes for the wallet are handled internally, no need to ask for mutexes on the wallet.
• wallet complexity has gone up a substantial amount. There's a chain of really heavily nested for loops (for blocks; for transactions; for inputs & outputs;).

But from a cryptographic perspective, our new wallet is actually moderately passable as a secure thing, whereas before I don't think it could be considered that.

from sia.