der neue Solo-Pool ist online!
hier der Link zum Post von Con:
https://bitcointalksearch.org/topic/m.54428326
EDIT:
Quote
I have no idea if the hashrate is being routed from same place as the nicehash domain, but pinging nicehash.com from the server I get nice low latencies, but IPV4 seems to be faster.
Nicehash seems to be in the same datacentre! But anyway the lesson here is if you're renting hash from nicehash, I suggest you use solo4.ckpool.org:4334
Code:
ping -4 nicehash.com
PING nicehash.com (104.17.254.46) 56(84) bytes of data.
64 bytes from 104.17.254.46 (104.17.254.46): icmp_seq=1 ttl=57 time=1.40 ms
64 bytes from 104.17.254.46 (104.17.254.46): icmp_seq=2 ttl=57 time=1.53 ms
64 bytes from 104.17.254.46 (104.17.254.46): icmp_seq=3 ttl=57 time=1.44 ms
64 bytes from 104.17.254.46 (104.17.254.46): icmp_seq=4 ttl=57 time=1.42 ms
64 bytes from 104.17.254.46 (104.17.254.46): icmp_seq=5 ttl=57 time=1.52 ms
Code:
ping -6 nicehash.com
PING nicehash.com(2606:4700::6811:ff2e (2606:4700::6811:ff2e)) 56 data bytes
64 bytes from 2606:4700::6811:ff2e (2606:4700::6811:ff2e): icmp_seq=1 ttl=56 time=19.6 ms
64 bytes from 2606:4700::6811:ff2e (2606:4700::6811:ff2e): icmp_seq=2 ttl=56 time=19.7 ms
64 bytes from 2606:4700::6811:ff2e (2606:4700::6811:ff2e): icmp_seq=3 ttl=56 time=19.5 ms
64 bytes from 2606:4700::6811:ff2e (2606:4700::6811:ff2e): icmp_seq=4 ttl=56 time=19.5 ms
64 bytes from 2606:4700::6811:ff2e (2606:4700::6811:ff2e): icmp_seq=5 ttl=56 time=18.6 ms
Nicehash seems to be in the same datacentre! But anyway the lesson here is if you're renting hash from nicehash, I suggest you use solo4.ckpool.org:4334
link:
https://bitcointalksearch.org/topic/m.54429356
Das ist natürlich dann Nicehash Amerika!
