### CWI-SEEDNODES - MIGRATION

Hi All,

Yes, I'm actually going to start conversing in my usual constructs and verse. Stop having a heart attack

This post is to update you on the impending FULL migration of the CWI-SeedNode Infrastructure and what the consequences are of this.

A full post is forthcoming and I am sure that a great deal of those involved with us will pant a sigh of relief that this time has actually come. The reason is simple. The current seednodes are in dire need of upgrade. The size of the seednodes; the memory; the processing power.

A number of the seednodes have seized which have caused a great deal of issues for our Partner coins (BERN, DON, EGC, SLG), as well as our Supported Coins (MTR, EMC2 and others). As a number of you know by now, via CWI-Slack as well as Skype and various posts made in our other threads, we have been organizing a full upgrade to our entire backend infrastructure. As such, CWI-InfraStructure is currently undertaking a massive overhaul. Part of this revamp are the CWI-SeedNodes, as well as the CWI-Pool servers, CWI-Stratum and CWIgm. This in turn, will have interruptions with the operation of the seednodes, and as such will temporarily suspend support on a network level for any new adopters of our coins (partner and supported coins included). The interruptions will not be for long, and when the migration is complete, the DNS re-directions will only take 'upto' 24 Hours to complete.

We are aiming to have everything finalized and ready by the weeks end next week, and if all is well, we will have the CWI-Pool system migrated as well to the new powerful servers that are now part of CWI-InfraStructure.

We have taken some time to get to where we are now, and this major revamp has taken a great deal of effort, as well as finances, but we believe that it is all justified. The improvement in the backend, will manifest itself in the frontend when the syncing of our coins, the speed of our stratum, the stability of our systems (especially CWI-Pool) are all working seamlessly with one another.

Thanks,

Just one more thing - for the sake of it.

... ... ...



#crysx

It's normal. Because report hashrate in CWI pool very fast, and hashrate depend on shares/ diff shares. That's why some time you have very high hashrate and some time very low or your worker disappear. I have a worker 350 MH/s, some time I see 800 MH/s, some time he gone in 30 - 60s.
But don't worry, you can see average hashrate and shares on Graphs. Hashrate at the moment not reflect your real hashrate, you have to see the average hashrate at least 24h. Good luck

it means that the job that was sent to you - was already missed for submission ...

the nonce error is not a 'normal' occurrence and we are working on the issues ...

#crysx

I'm negative on my mem and up core to OC and get better rates doing that

Example

-180 mem
+215 core

why OC your mem, is there any advantage?what i know SIGT is core extensive...