I have some dates!
We will be doing a pre-release stress test and aiming for release on Friday. Assuming we are not finding any showstopper bugs. The release should be viewed as a beta release, so it is for a more general feedback for compatibility, usability, etc.
keep in mind this is just the first version and not all the advanced tech is made available via GUI. To access the more advanced tech, you would need to be using something not so easy, as it is via JSON API. But this is the nature of this as first there must be the advanced functions via API, then a GUI that is working but not the most easy to use, then finally a nice looking intuitive GUI that needs no documentation.
I am currently working on finalizing InstantDEX API and we are pushing for an initial GUI release in a week. This is independent from the release above, which is making easy to use multiwallet. And there are also some features available in the v0 GUI that is there, but not in the v1 series.
I hope this is not too confusing, but it is the best process that we could come up with to manage the nature of SuperNET. Some are not sure if the 60,000+ lines of code in
https://github.com/jl777/libjl777/ is making any sense. What the v1 GUI is doing is making about 10,000 of these lines easily accessible. To put it in perspective, I wrote ramchains from scratch starting the new years. I ported the old MGW into realtime MGW, total line count around 10,000. So to go from concept to coded to debugged to production, in this timeframe it is a demonstration. The full SuperNET is much bigger, so I wanted an easy well defined project I can finish quickly.
I hope that this ramchains release puts to ease everybody who is wondering if jl777 can actually write code that works. It is doing a complete blockchain rescan and richlist calculation for BTCD in about 30 milliseconds. But it doesnt even have to do the recalc as it is maintaining in memory current account balances, so all that is needed is a sort, which takes around 1 millisecond.
Now how long will this all take to be finished? This is like asking when linux will be finished. So let us ask a more specific question, when will InstantDEX be finished? I hope to get this done by the end of the month so people can have a much safer place to trade than central exchanges. Next week for test releases and we can get things done faster the more people are testing. This is the standalone InstantDEX, I have no idea the time for it to be finished in the v0 or v1 series GUI.
I want to get InstantDEX prioritized due to the situation with half a dozen exchanges being attacked and not even clear how many will survive. so this will shuffle the schedule a bit, but I think we can all agree it is worth the tradeoff. So I will be concentrating on gettting InstantDEX to be usable for large scale crypto trading. This will include Tradebots, at least default ones with standard functionality. A more advanced tradebot profit sharing will require some website and GUI things.
In parallel, still waiting for some design reviews on the privacy side of the project. I have received invaluable feedback from Come-from-Beyond and we licensed some tech that will really enhance the security of the SuperNET. This will require some time to properly integrate into the codebase, I am estimating about a month and then realistically another month to properly test it. Before all that it will still be possible to use the privacy features, with the caveat that it is not fully validated yet.
So we have the teleport, telepathy and enhanced security all converging to a release in a couple months, but these features will be testable way before it is in the final form.
At this point, I will only have the PrivateBet tech left to complete, and it is possible I can squeeze that in during the privacy improvements. Now I can write a lot of code and I estimate it will end up around 80,000 to 100,000 lines by the time these things are all done. However, I am not the only one coding. There are literally a dozen projects going on and I am not aware of the detailed status on these, but to facilitate others to help with coding, I have added the ability for non-C modules to be dynamically loaded and extend the SuperNET API. Pangea is written in python, so that was the trigger for this, but while adding support for that I realized we can support virtually any other language, so as we get devs who work in a particular language we can extend the SuperNET to support running single instance invocations or even as daemons.
Unfortunately, every person that is taking the task to clearly document all this, well their head seems to explode...
And I must allocate my time to coding and helping the other projects, so I just dont have the time to be making regular updates.
That being said, if there are any specific questions, then I will do my best to answer them.
James
tl:dr releases are happening, tech is being completed, wont happen all at once but it will happen