Discussion in 'Testnet / Development' started by XTRABYTES, Nov 18, 2017.
Test Net status and what currently is in progress will be posted here.
Yes, we have been delayed due to solving explorer issues. This was a soft deadline that we hoped to be up and running by yesterday but as we always say, we don't do deadlines. Its not possible to know if issues will come when trying to get things prepared, but the other side of this is to not give any indication that something is coming and that is not good either.
This is always a work in progress folks and we do our best to get things done asap. It was early morning when we were still working on the explorer and some issues with the server where discovered. These issues could actually solve the minor irregularities the team has been trying to sort out. So, perhaps this is the silver lining...
Our apologies for the delay. Hopefully when Broz gets back online we will get something started.
Think that's just the nature of a project of this scope, so many moving parts to keep in check plus new things are being added all the time it a huge undertaking. Glad to hear some issues were sorted out and getting the explorers online for the testnet is a good idea so everyone can see what is happening and keep track of things.
We experienced some major issues with the server (RAM related problems), we where unable to finish Block explorer for an XFUEL. Now the issue with memory is (hopefully) resolved, so, work in progress.
Currently we experiencing some compatibility issues with current version of Red Hat Enterprise Linux based OS (CentOS 7.4) installed on our web server, It's causing the delays to fix this issues, and to make and addopt an XFUEL block explorer.
We came to the conclusion, and we ordered a second VPS server, dedicated to our Block explorers, static node lists, other apps etc., It will be operated under Debian based OS, and will help to keep the main web server (it's where current forums and site is hosted) without interruptions and errors.
We will be using the VERY early release (its probably bare) of the XCITE platform. You guys are the first to hear about this, outside of a few people we shared with the other night.
XCITE is the XTRABYTES Consolidated Interactive TErminal which has multiple functionality, including: wallets for XBY and XFUEL, access to core modules, access to 3rd party DApps and modules and access to important places like our forum, Slack, BCT forum and other marketing portals which may be of use.
This will eventually be a full page browser with all these functions and this is one of the first jobs we will be posting. We need people to start the wireframes and start helping to put this together.
This is the spacer page until the xcite explorer is done
The first xcite.exe will be available shortly
and the next and next until we get a usable version
the first xcite.exe will be a self destruct test
everyone needs to start this and need keep it online
Then Borz will execute the kill script and we all need to exit and then he creates the killer block
this is a special block and this will be required a few times by the sounds of it.
(This is loosely translated from Borz)
So, my understanding is that when the .exe is ready, we will not see this spacer page any more.
A quick test has started using the Xcite client. Details can be found here if you want to take part:
The 100 Block test has now concluded and has flagged a some things that need attention. Thank you to everyone who took part and stay tuned for the next one.
We will try and get a more detailed post together on the test, what was achieved, the results of the test, any issues, etc.
Again many thanks for your participation.
A new test has begun with an updated XCITE wallet, this will be to Block 200 to see if the bug from the previous test has been fixed. Details can be found here:
Borz has confirmed that the 200 Block year was a complete success.
Now we can move on to the next test. Details to follow as soon as it becomes available.
We have just finished running a preliminary small test with STATIC and PoSign... After about 70 blocks were mined, Borz restarted because there was a couple minor bugs identified that were specific to the test.
Borz is going to simplify this for us by the looks of it. New version incoming with Key Conversion Panel
I will create one conversion tool where possible converting the different private keys
and import from this tool without using the debug console
If there are any other issues you can identify, please let us know now so he can include this in the updated XCITE.exe
This is posted by Seb59 in the Slack testnet group:
Seb59 12:15 AM
ok it sgood but a lot of time out in debug file
2017-11-20 12:11:56 trying connection 126.96.36.199:1111 lastseen=15.1hrs
2017-11-20 12:12:01 connection timeout
2017-11-20 12:12:02 trying connection 188.8.131.52:1111 lastseen=3.4hrs
2017-11-20 12:12:07 connection timeout
2017-11-20 12:12:07 trying connection 184.108.40.206:1111 lastseen=6.2hrs
2017-11-20 12:12:12 connection timeout
2017-11-20 12:12:13 trying connection 220.127.116.11:1111 lastseen=6.2hrs
2017-11-20 12:12:18 connection timeout
2017-11-20 12:12:18 trying connection 18.104.22.168:1111 lastseen=15.5hrs
2017-11-20 12:12:23 connection timeout
2017-11-20 12:12:24 trying connection [2001:0:9d38:6ab8:3c24:49e3:53c7:fb3e]:1111 lastseen=2.3hrs
2017-11-20 12:12:29 connection timeout
2017-11-20 12:12:29 trying connection 22.214.171.124:1111 lastseen=4.5hrs
2017-11-20 12:12:34 connection timeout
2017-11-20 12:12:35 trying connection 126.96.36.199:1111 lastseen=14.5hrs
2017-11-20 12:12:40 connection timeout
2017-11-20 12:12:41 trying connection 188.8.131.52:1111 lastseen=3.7hrs
2017-11-20 12:12:46 connection timeout
2017-11-20 12:12:47 trying connection 184.108.40.206:1111 lastseen=18.3hrs
2017-11-20 12:12:52 connection timeout
2017-11-20 12:12:53 trying connection 220.127.116.11:1111 lastseen=18.3hrs
2017-11-20 12:12:58 connection timeout
2017-11-20 12:12:58 trying connection 18.104.22.168:1111 lastseen=2.3hrs
2017-11-20 12:13:03 connection timeout
2017-11-20 12:13:04 trying connection 22.214.171.124:1111 lastseen=2.3hrs
I passed this on to Borz and here is his response:
this is normal
try connected to other nodes
and the node is offline or unavailable or don't accept the more connection etc...
each node accept limited number of connection from others
sometime drop one existing connection and try it reconnect to other
this is normal operating mode
So, onward and upward... the tests are running and we will continue to gather information.
Please feel free to post your comments either in the Slack or here on the Community Forum or on the BCT forum.
TestNet is going strong, we are at block 1430 Heavy transaction tests will be performed soon, please join TestNet! We need more people
A dedicated server for Block Explorers is ready and running Debian 8.9, admin panel installed and tuned, server is ready to host explorers.
Additional (backup) explorer for xrabytes is installed and running, XFUEL explorer is installed, but needs some work (in progress).
Made a sheet for people to put their public addresses on so they can start sending/receiving Test XBY:
Extra lite little test, and - 324 transactions in one block: http://xcite.xtrabytes.services/?9667ffb723e9b75d064875f4cfba5bad98cc6e67ef872e8ad34f41b740d8d47f
Just to give everyone an update on where we are in regards to the testnet and when the next one will start.
The testnets so far have gone very well so thank you everyone who participated and helped out with them.
The next testnet is taking longer to get ready as we have been able to accelerate plans on one of the core modules for XTRABYTES and are eager to try it out as soon as possible. As such the decision has been taken to include it in the next phase so we are working very hard to get that up and running as quick as possible so we can do two tests in one. We also believe that including this module to try out will bring a lot more people to the testnet so it will be a win win in that regard.
As frustrating as it is please sit tight and we will get this out to everyone as soon as we possibly can as we are just as eager to get things going as all of you are i’m sure.
Thanks again for all your help and support as well as your patience and understanding.
Block explorer still doesnt work. It is showing : RPC Ace error: failed to connect - node not reachable, or user/pass incorrect
Separate names with a comma.