So sad but so true I guess..

We need some chinese anti-ant propaganda..

The antpool needs to change its ways or suffer a horrible faith..

Any way for anyone to customize a full bitcoin node so all who would wish could patch their own core full node with patches that would not propagate this type of antshit block hijacking..

I think someone also scored a block with ant s1 about a month or so ago..

Just tested this and can confirm the main server no longer refuses authorization even when its a backup and using DE as main server. First authenticates ok on DE and starts mining and also authenticates fine now with same address.workername on main server which is a backup without any problems..

Seems that bug is crushed, thank you very much -ck.

I have had same problem for a while, not being able to authenticate on the main server, but DE server is authenticating and working fine..

Have not reported it before since DE server is closer to me and did not want to bother thinking it was just me, but I can confirm I have copy pasted same address.worker name and can mine on DE but main SOLO is rejecting my authentication even if I put it as a backup..

Most likely two conditions will have to be met:

1. The blocks those rewards are based on have to have matured

2. Kano needs to be awake

3. ??

The luck is ridiculous today

If I may enquire, any idea which of your Ants scored the block, s1 or s2 ?

An impressive feat anyway nowadays, congrats !!

IPv6 address.

Thanks for the tip, will give those lower values a try as well to see if performance can be even better than with 1000..

Appreciated !

I am sure CKPool handles vardiff  very well, just seems Ant s2s does not, and tries to throw a fit with vardiff at some point, no idea why though..

Hmm while testing as I wanted all things to be "equal" once I set the diff offered on Kano pool to 1000 (the same that solo pool is offering) the Ants2 is way more happy and hash rate has climbed back up  and not getting as many hw errors either.. So no problem with DE node or anything it seems as far as I am considered..

Weird though that ant s2s dont seem to like the 1042 default which is being offered if I left the worker diff setting to 0 and let it auto adjust.. (if anyone knows of a better setting than 1000 please do tell) but yeah, that seemed to do the trick to get it to perform the same as in solo pool..

Will test a bit longer and report back when I have something more substantial

Hmm seems it may be the miner (S2) fault as for some reason when I have Kano DE as primary and Kano USA as secondary, it sometimes hops to the USA server for a second and the S2 does not like that and I start getting more HW errors when it does that until I reboot it.. Also tried removing the secondary option which helped a bit, but still I see I am getting better hashrate on the Solo DE pool compared to what the hashrate was on either the main USA kano server or the new DE kano server.. Weird.. Might be just me though..

Hmm weird, as I am connecting from Finland, and started using DE server since I had way much better ping there, but my hashrate was way down compared to using the main USA server which had 100ms worse ping for me compared to DE server..

For some reason I get much better hashrate using the main server so gonna use that for now..

Edit: Hmm even the main server gives slightly lower hashrate than it used to, no idea why, even though its better than DE.

Have to try mine a bit on solo pool to see if its miner related or not..

Seconded ! DE server brings much improvement to European miners:

PING kano.is (104.194.28.196) 56(84) bytes of data.
64 bytes from u3a196.iporg.org (104.194.28.196): icmp_seq=1 ttl=52 time=215 ms

PING sg.kano.is (139.162.5.112) 56(84) bytes of data.
64 bytes from sg.kano.is (139.162.5.112): icmp_seq=1 ttl=52 time=389 ms

PING de.kano.is (139.162.143.142) 56(84) bytes of data.
64 bytes from li1410-142.members.linode.com (139.162.143.142): icmp_seq=1 ttl=53 time=50.0 ms

Thank you Kano & CK !

No hurries, take your time offcourse as you must have many a more important things to do, main thing is that it was not the miner that was broken as I thought at first

Well atleast did a proper cleanup job on the miner as well Maybe it will be pleased and find a block lol

Edit: cgminer output:  Pool 0 message: Authorised, welcome to ckpool zahzin!
that was fast, thank you very much

Edit2: Woohoo, Holyscott at it blocking another one !! Haha just as was watching the console

Info sent via PM, checked and confirmed that workername is correct now and added the email to whitelist, it had went to gmail spam, sorry again for any inconvenience and thank you for this valuable service !

Hmm seem to have a similar problem then, DE is now working for me as well once I tried 3334 port, 3333 was dead to me too..

As for failing to Kanos pool, that one is dead to my S2 no matter if I use my created username or bitcoin address to mine..

EDIT: Seems port 3333 at DE pool just started working for me.. Still got kanos pool dead though

EDIT2: Spoke too soon, 3333 port on DE not working for me anymore, failed over to 3334..