These updates are consistently packed with progress and goodies. 
Amazing work everyone. Such a great team and community to be a part of, and especially now we’re trundling towards the launchpad 
Any chance of seeing, or better playing with the fruits of Benno’s WebSockets support?
Or if not, a description of what has been achieved using it so far. I think it was tricky so am curious - it seems like a valuable capability that opens up many possibilities.
Can’t wait for WP and Branding 
Great update as always! Really looking forward to tomorrow/next week with the WP and interested how the rebranding is set out. Maybe it is said before, but will it be accompanied with a new webpage and other marketing deliverables?
Lets launch!!!
Currently it’s automatically generated, but this PR is just the start for backup / restore feature (which will allow entering your own mnemonic). I try to keep each PR fairly small to make it easier to review. Once this is in I’ll start on the backup / restore etc.
Awesome 
These are pronounced as “SeeyashNotes”, right? 
Seeing as many folk will be asking what a DAG is going forward.
I think this is a pretty good explanation.
Thanks for sharing! Great explanation!
There is this sticky situation with AutoNAT just dragging on so close to finish line. It seems it would be ready very soon, but I could see it still dragging on for some indefinite time. My understanding of the situation is:
Code seems to be ready, but:
It is not tested.
There is a slight unclarity about if it can be used because of a licence issue.
The main guys leading the development are not working anymore in the organization.
I could see all of these summing up into a situation, where every small step forward has so much friction, that the process gets very slow. On the other hand, this might resolve quite quickly too. But who knows?
If I read our Roadmap right, we should have AutoNAT working around May to keep us on schedule. If the current process at Protocol Labs just keeps on keeping on, what can we do? Could Maidsafe hire someone to make a custom implementation for them, for example?
Another thing:
Are we going to have some TPS numbers in the whitepaper? Or are those figures something that we are going to find out by testing? It seems to me we would need two numbers:
Have I gotten it right?
This is driven by network size. More groups, more TPS.
As long as this is sub second we are fine. You can have many clients.
David it’s 6 AM in Scotland right now. Go back to bed! 
As we see in the testnets this is fast since every chunk stored has 2 payment transactions occurring. And in the testnets even with a relatively small number of nodes the total TPS of the network is handling everyone uploading with 2 transactions per chunk.
I know it’s fast. I was more wondering if we are going to get some numbers to give people who will be asking.
As you suggested, testing will help provide this. I would expect the testnets are too small to come up with a figure other than fast.
It could even take a coordinated effort with much larger networks to try and measure this because the transactions are happening in a random way and without knowing what other people’s nodes are doing you cannot even work out the size.
I hope as well we can get an estimate for the low end of the TPS.
How can i swap my maid coins for emaid?