Would be cool if we can see the total pool hashrate when in our user dashboard.
Done
Refresh page. 
Topic: [∞ YH] solo.ckpool.org 2% fee solo mining 256 blocks solved! - page 212. (Read 91394 times)
Done
Refresh page.
Would be cool if we can see the total pool hashrate when in our user dashboard.
You can change theme by appending "theme=light" in URL. Eg. http://35.226.27.67:3000/d/_afS1cRMk/ckpool-home?theme=light . I am looking if I can somehow make this more user friendly. I can make light default, if majority like the light theme more (I personally prefer dark theme).
I prefer the dark theme as well.
You can change theme by appending "theme=light" in URL. Eg. http://35.226.27.67:3000/d/_afS1cRMk/ckpool-home?theme=light . I am looking if I can somehow make this more user friendly. I can make light default, if majority like the light theme more (I personally prefer dark theme).
I am going to donate some of my free time, instead of satoshis. Currently I am working on dashboards for CKpool.
You can see current progress here: http://35.226.27.67:3000/d/_afS1cRMk/ckpool-home
There are two dashboards:
It is in development state, so there can be some downtime. If anyone have any suggestion, if there is something missing, redundant, or some bug, feel free to tell.
You can see current progress here: http://35.226.27.67:3000/d/_afS1cRMk/ckpool-home
There are two dashboards:
- Global pool stats
- User stats - You can add your pool address at top right link Add address to dashboard
It is in development state, so there can be some downtime. If anyone have any suggestion, if there is something missing, redundant, or some bug, feel free to tell.
Dude black background is too dark for my tired old eyes.
I can't see how to go to a white background.
Other then that it looks nice.
I like it
I am going to donate some of my free time, instead of satoshis. Currently I am working on dashboards for CKpool.
You can see current progress here: http://35.192.6.83:3000/d/_afS1cRMk/ckpool-home
There are two dashboards:
It is in development state, so there can be some downtime. If anyone have any suggestion, if there is something missing, redundant, or some bug, feel free to tell.
//EDIT: Moved to another server - http://35.192.6.83:3000/
You can see current progress here: http://35.192.6.83:3000/d/_afS1cRMk/ckpool-home
There are two dashboards:
- Global pool stats
- User stats - You can add your pool address at top right link Add address to dashboard
It is in development state, so there can be some downtime. If anyone have any suggestion, if there is something missing, redundant, or some bug, feel free to tell.
//EDIT: Moved to another server - http://35.192.6.83:3000/
philipma1957, is it possible to make a donation through you via paypal?
I received $150 donation direct to my PayPal.
I will send 150 in btc to
https://btc1.trezor.io/address/1F8JWHPVt2FzxeAyPDUP4hmeRPweJZEFYj
edit here is tx id it is confirmed.
https://btc1.trezor.io/tx/c1a056bf37c0aec66e9af5682f620c49d06dc5525e8771f64b303980af45d782
we have 0.0348215 in the wallet
most is in
0.02546 is here. of which edit : all is confirmed .
https://btc1.trezor.io/address/1F8JWHPVt2FzxeAyPDUP4hmeRPweJZEFYj
0.0093615 is here this is all confirmed
17JgeZrjHtz******************so7YUFp
0.0348215 is well on the way for a second 6 months of payment for the server.
every little bit helps.
1F8JWHPVt2FzxeAyPDUP4hmeRPweJZEFYj
thank you to all that put in.
goal is to send six more months of server fees. which will mean 1 year was paid by us miners.
The remaining funds will be held as rainy day coins. I will send 0.01 to the lost block miner once we have paid in enough for 1 year of server fees.
Hold other coin in case a a lost block or down the road about May of next year pay for more server costs.
Quick question. 
The pool stat's say
{"diff": 115.0, "accepted": 18489486887172,}
Are we still at 115 diff even after the lost block?
Are the stat's off now because of the lost block.
It only resets if the block is confirmed. The stats are right, we still haven't found a successful block. It's all up to interpretation, and that's how I see it. The pool stat's say
{"diff": 115.0, "accepted": 18489486887172,}
Are we still at 115 diff even after the lost block?
Are the stat's off now because of the lost block.
Quick question.
The pool stat's say
{"diff": 115.0, "accepted": 18489486887172,}
Are we still at 115 diff even after the lost block?
Are the stat's off now because of the lost block.
Thanks in advance!
The pool stat's say
{"diff": 115.0, "accepted": 18489486887172,}
Are we still at 115 diff even after the lost block?
Are the stat's off now because of the lost block.
Thanks in advance!
philipma1957, is it possible to make a donation through you via paypal?
pm sent
yes
offtopic @-ck: in your sig you still advertise the normal ckpool. Might want to remove or edit it to reflect the closure.
Nice choice ping looks great!
Now it's time to....
Now it's time to....
Amazing! great work CK and great work to the community showing Con the support.
CK could you ping MRR to see what the ping is like from there I'm more of a MRR fan than Nicehash would be interesting to know where there ping to the server.
Mine on everyone! Good Luck!
Sure thing. Looks like I picked a VERY popular datacentre lol.CK could you ping MRR to see what the ping is like from there I'm more of a MRR fan than Nicehash would be interesting to know where there ping to the server.
Mine on everyone! Good Luck!
Code:
PING miningrigrentals.com(2606:4700:20::681a:3d (2606:4700:20::681a:3d)) 56 data bytes
64 bytes from 2606:4700:20::681a:3d (2606:4700:20::681a:3d): icmp_seq=1 ttl=57 time=1.38 ms
64 bytes from 2606:4700:20::681a:3d (2606:4700:20::681a:3d): icmp_seq=2 ttl=57 time=1.25 ms
64 bytes from 2606:4700:20::681a:3d (2606:4700:20::681a:3d): icmp_seq=3 ttl=57 time=1.16 ms
64 bytes from 2606:4700:20::681a:3d (2606:4700:20::681a:3d): icmp_seq=4 ttl=57 time=1.27 ms
64 bytes from 2606:4700:20::681a:3d (2606:4700:20::681a:3d): icmp_seq=5 ttl=57 time=1.44 ms
Code:
PING miningrigrentals.com (104.26.0.61) 56(84) bytes of data.
64 bytes from 104.26.0.61 (104.26.0.61): icmp_seq=1 ttl=57 time=1.44 ms
64 bytes from 104.26.0.61 (104.26.0.61): icmp_seq=2 ttl=57 time=1.27 ms
64 bytes from 104.26.0.61 (104.26.0.61): icmp_seq=3 ttl=57 time=1.34 ms
64 bytes from 104.26.0.61 (104.26.0.61): icmp_seq=4 ttl=57 time=1.30 ms
64 bytes from 104.26.0.61 (104.26.0.61): icmp_seq=5 ttl=57 time=1.32 ms
Both are insanely fast, and seem to be in the same datacentre again! So just use the solo.ckpool.org address and let the routing choose automatically what to use if it supports IPV6 (most default to 6 and drop to 4 if they can't route through IPV6).
Amazing! great work CK and great work to the community showing Con the support.
CK could you ping MRR to see what the ping is like from there I'm more of a MRR fan than Nicehash would be interesting to know where there ping to the server.
Mine on everyone! Good Luck!
CK could you ping MRR to see what the ping is like from there I'm more of a MRR fan than Nicehash would be interesting to know where there ping to the server.
Mine on everyone! Good Luck!
I've taken the testnet pool down. No need to run anything at all on the server that's not needed so that it's a lean mean block finding machine.
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
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.
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
philipma1957, is it possible to make a donation through you via paypal?
Wow...
That was fast
Thanks -ck!
That was fast
Thanks -ck!
SURPRISE
You've all been transparently migrated to the new server without any interruption to your mining thanks to the magic of cgminer and ckpool's inbuilt redirection support.
All statistics have been carried over to the new server. No change to any configuration is required by any miners. This server is massively overqualified for the task now and has extremely fast block changes, propagation, and bandwidth.
In addition, as per the last pool, it supports both IPV4 and IPV6.
As noted on the new pool home page though:
Mine on, and let those blocks fall!
You've all been transparently migrated to the new server without any interruption to your mining thanks to the magic of cgminer and ckpool's inbuilt redirection support.
All statistics have been carried over to the new server. No change to any configuration is required by any miners. This server is massively overqualified for the task now and has extremely fast block changes, propagation, and bandwidth.
In addition, as per the last pool, it supports both IPV4 and IPV6.
As noted on the new pool home page though:
Code:
Note that solo.ckpool.org supports both IPV4 and IPV6 transparently.
You may wish to find which is lower latency for you and specify one or the other directly.
IPV4 is solo4.ckpool.org
IPV6 is solo6.ckpool.org
Mine on, and let those blocks fall!
+ Merit and thanks a lot, that was really fast, respect!
to all solo miners:
in our new Solo Mining Runs (rentals from NiceHash), we support the Solo Pool always with a 0,005 BTC donation.
If you want to have the opportunity to win a block and support the Solo Pool at the same time, jump in
--> https://bitcointalksearch.org/topic/canceld-bitcoin-group-mining-let-us-burn-a-block-10-phs-reloaded-16-5248106
Super Fast migration, thanks con.
Nice! will use the coin to make a real solo attempt then 
Jump to: