Pre-Dev-Update Thread! Yay! :D

Development Updates
449

Ok Here is where we are tonight (again)

Good news

  • Tcp hole punching has been very successful.
  • Tried from China which worked perfectly well
  • Automatic nat_traversal seems very good
  • We are not using any more resource in Udp and variants now as the Tcp nat_traversal is much better than we thought.
  • Much of logging is now improved, info for user facing logs and debug level for more information such as numbers of messages, amounts of data per vault. Should be interesting for people, but especially for devs.
  • Service discovery switched back on (no need for config files)
  • Overall design for network dashboard agreed and log messages being altered to suit (think old visualiser with much more user facing data).
  • Many client updates to prevent abuse of self encryption (it was inefficient)
  • significant reduction in data passed during churn
  • Network full tested and works fine, adding more resource lifts client block when network is full.
  • automatic deployment of vaults on publishing a github tag (release). Platforms so far X86 Win/Linux: X64 Win/Linux/Osx
  • Docker containers in final test stage for auto deployment
  • ARM (yes @happybeing) is already building (we do need to PR a 3rd party repo though) and will be added to auto deployment. There is a bug at runtime and Adam is on that right now. Looking good for ARM though

current blockages

Only one really, which is we have still seen machines being overwhelmed somehow to the point heartbeat messages fail to arrive. This causes nodes to restart and network instability. We are benchmarking parts of the system tonight to see if we can see just where this is. Tomorrow will see us try and squash this one. That should make way for test2 which I feel sure everyone will see a huge improvement with. The reason I am so delighted is now we can test on the network and now can demonstrate how quickly we can react to wishes and any bugs we find. It is a significant improvement.

So lets see where we get tomorrow and then get this test going.

For the folks wondering about releases we are moving towards Alpha and this will be the MVP. It will iterate though a few Alpha versions till we are happy to call it Beta. At Beta we will add messaging and test-safecoin. Then release and safecoin. I hope that describes the process we are following. MVP is a huge milestone and it’s around the corner as anyone can see and we can demonstrate. Just as soon as we squash this message processing issue we spotted this afternoon.

46 Likes