delegate name: btstools.digitalgaia (Standby | 7.45% votes)
2-core xeon, 4GB RAM, 100Mb/s symmetric, location: FR (hosted at https://www.gandi.net
seed01.digitalgaia.io:1776 (22.214.171.124:1776)chain server:
seed01.digitalgaia.io:1375 (126.96.36.199:1375)bts_tools source code: https://github.com/wackou/bts_toolslast published version:
see last posts in this thread for current updates, official changelog for released versions can be found here: https://github.com/wackou/bts_tools/blob/master/HISTORY.rst
Having learned about Protoshares about a year ago now, I have since then been fascinated by the DAC concept and BitShares in general, which is why I decided to run as delegate since the launch of BitShares (and the dry runs before that), and have been developing some tools in order to maintain my delegate easily. This has been open source since the beginning and the source code can be found here: https://github.com/wackou/bts_tools
What the tools do is that they automate a lot of the tedious tasks needed to properly maintain a delegate, such as building a new version, publishing feeds, not forgetting to update the info of your delegate with the version after an upgrade, monitoring of network connections, etc... and will send you an alert by email or iOS push notifications whenever the client crashes or starts missing blocks.
I have created a 30% paid delegate to fund my development of the tools, and further participate in the BitShares ecosystem (eg: I already provide a seed node too, but would like to provide chain nodes, write howtos about setting up a new node, etc.)Mission
My mission is to enhance the security, stability and overall reliability of the BitShares platform, by making it easier to run a delegate properly, and enforcing good practices. I also have some ideas about making the network more resilient to defects, lack of connectivity and/or directed attacks which I would like to explore if given the opportunity.
These 2 main avenues of development can currently be seen on my delegate website:Short-term roadmap
The roadmap I plan to follow for the short term future is to go on developing the bts_tools, fix bugs and implement feature requests that can be seen in the github issues tracker: https://github.com/wackou/bts_tools/issues
Mainly, I would like the tools to be ultra-reliable (what good is a monitoring tool if it crashes?) and start implementing what is needed in order to monitor specialized nodes (eg: seed nodes, chain nodes, backbone nodes) instead of just delegate nodes.
As for network health, I also pledge to set up and maintain 2 seed nodes / chain nodes in each major geographical region (US, Europe, Asia) for a total of 6 nodes for as long as I am voted in.Long-term roadmap
In the long term, I plan to continue maintaining the delegate tools and make it easy for delegate to perform their duties easily (by writing tutorials, etc.).
Once we know that all delegates are operating in a stable way, I would also like to try to investigate what could be done at higher level in order to ensure that the network functions properly (for instance, I firmly believe that it would be beneficial for the network if it could be ensured that it acts as a small-world network), and would like to build incentives for nodes to coordinate in order to guarantee that, or provide myself nodes that would do that.About me
My name is Nicolas Wack, and I have been developing in C++ for the last 15 years doing mostly audio analysis (main project of fame: http://essentia.upf.edu/
, source at: https://github.com/MTG/essentia
) and python for the last 10 years or so, doing a bit of everything (main projects: https://github.com/wackou/guessit
(active) and https://github.com/wackou/smewt
(retired, for lack of time))
You can see some of my projects on my GitHub account (https://github.com/wackou
), as I am a fervent believer in open source and free software as a better way of developing software.