Yeastplume - Progress update thread - Oct 18 - Feb 19

Announcements
26

Update Friday, Jan 11th 2019

A bit sick of writing things at the moment, so this is going to be a fairly short one. Here’s the reason why I’m sick of writing things:

Basically a lot of work getting the wiki filled with some Grin noob guides and a large pass over the wallet user documentation, which I’ve moved out of the source and into the wiki page (where it will be far more useful). Also a bit of work getting the site into a state where it’s better leading newcomers to the information they need. I’m trying to get all eyes towards the Getting Started wiki page, which should contain all the relevant links people need to get up and running with Grin

Some dev work too, mostly quality-of-life things with one major fix:

  • Add the ability to init a wallet from a recovery phrase added after a few users correctly pointed out the previous process was needlessly cumbersome and you should be able to recover a wallet in a single step. (though it’s two steps at the moment, grin wallet init -r followed by grin wallet restore which I believe should stay distinct steps, reasons why some other time)

  • Only update wallet outputs from the node if they’re involved in an outstanding transaction, this should give a large perf. improvement to the wallet under most conditions, as it was previously validating each and every Unspent output in the wallet each and every time to see if it had become spent. Makes sense that a wallet shouldn’t have to check outputs it hasn’t inserted into a transaction.

  • Automate wallet seed recovery process automagically backs up/moves your existing wallet seed file if you’re trying to recover a seed into existing wallet data. Should be useful for those who forget their seed passwords

  • libSecp bug fix Important fix, and very glad this was caught in floonet, as it would have made some outputs under certain conditions hard to recover and cause problems with wallet check and restore.

Oh and renamed check_repair to check, since check_repair sounds like the wallet broke, which is not the case. I very much think the check process should become part of usual wallet operations instead of having to run it manually, just the scanning process is potentially too cumbersome to perform all the time at present (I think we need an incremental scan approach).

And thanks again to everyone who attended the Grin London Meetup! Was great seeing everyone and I hope to be coming out to a few more of these things once the mainnet launch dust settles down.

Speaking of that, Mainnet is launching in 4 days. Enjoy the weekend.

7 Likes