### CWI-POOLShi all ...
as most of you know - we have been working very heavily in the backend of the cwi infrastructure ...
a great deal of work has been put into the design and stability of the backend - and the solidity of the infrastructure itself ...
part of this has been the cwi pool system ... which i will focus on in this post ...
new servers - with new pools - and a new cwi custom built stratum for the backend mining have been built ...
this means that there will be teething issues that will need to be resolved ...
the servers are solid dedicated servers that are not just vps instances ... they are physical systems that are situated in physical datacenters - that have redundancy built into the datacenter itself ...
since the build has grown quite some - a need for a set of protocols was required which would help the expansion of the cwi-pool system ... one of those protocols was the implementation of a set of specified ports ( port scope ) to which certain algos may be implemented and not deviate from - while another was the implementation of the single sign on ( sso ) system per server - whereby the credentials of the profile are shared across the various pools database for ease of use for the user ...
what we have here is just that ...
http://pool.chainworksindustries.com/ ...
now this will be integrated into the new cwi-website - but for the time being it is based entirely on its own ... which is one of the reasons this page is a simple landing page to jump to the various cwi-pools ...
we have asked a few communities to be helpful enough to test some of the pools in order to bring it out of 'alpha' designation and colour ( blue ) to 'beta' designation and colour ( cyan ) ... but we have been having a few issues ...
the testing that some of the community members have done has just been fantastic - but not without issues ... it seems that a few have been subject to rejections from the pools while trying to mine ... and tanx to the help these people have given us ( and pmed me personally ) - we seem to have found the issue - and a resolve ...
the issue ...
the issue is not sso itself - nor the pool itself - nor the stratum itself ...
sso works - and works well ... so for the setup of the pool profiles and workers - sso works well for all the pools credentials to be shared across all the pools on any individual server ...
the cwi-stratum works - and works extremely well ... so for the stratum to be running as efficiently as it does - the build for the stratum is deemed good ... this code and development has made this stratum a solid and robust mining system ...
the issue is bringing the cwi-pools with sso - together with the cwi-stratum ... the stratum was built with a single database in mind and will work on that one specified database ( ie - pool / coin database ) efficiently and usually without issue ...
what the cwi-stratum doesnt do is recognise any of the 'shared' credentials that sso brings into play with the cwi-pools ... as with any custom code - it requires tweaking at times and at other times a rewrite ...
we had two options here ...
1 - undo sso on all cwi-pools and have the cwi-pools work separately until this can be resolved ...
2 - rewrite portions of the cwi-stratum code to allow for the shared credentials to be recognised ...
both of these options have their pros and cons ...
point 1 would mean the cwi-pools become IMMEDIATELY active ( pro ) - but would mean that if you wanted to mine on more than one pool with any of the miners you own - you would have to re-register on every one of the cwi-pools and redo / reassign every worker for each of the cwi-pools you want to mine with ( con ) ...
point 2 would mean that the cwi-pools would NOT become fully active right away and would require 'xxx' amount of time to resolve the issues while the stratum was rebuilt ( con ) - but would mean that after that period of time was over and the cwi-stratum was recoded - we would have the pools active WITH sso intact ( pro ) ...
we opted for the second option as we believe that is the best action to take ... rather 'band-aid' ( or temporarily patch ) the cwi-stratum - we opted to 'fix' it no matter how long it took ... patience truly is a virtue ...
as of time of writing this post - the cwi-stratum has been recoded - and a few changes need to take place in the configuration and setup of the cwi-stratum so that testing can begin once again ... this will be completed within the next couple of hours and hopefully will be fully functional ... your testing will provide the results of that
...
when this part of the test is completed successfully - the pools will have the 'beta' designation and change colour to reflect that ( cyan ) ...
as always - please let us know what it is that you are experiencing and any issues that need to be rectified ... had it not been for the feedback we have been receieving from thread posts and direct email / pm - we would not have been able to rectify the issues with the sso / stratum as quickly as we have ...
any feedback would be very much appreciated also - as that is what drives us to create a better system ... and as part of the cwi ecosystem - we want it rock solid ...
tanx for you patience - and if you wish to throw some hash across to test in the coming couple of hours - please do ...
now on with the change in setup - and testing ...
#crysx
