[∞ YH] solo.ckpool.org 2% fee solo mining USA/DE 255 blocks solved! - page 267.

hurricandave

legendary

Activity: 966

Merit: 1003

Quote from: o_solo_miner on December 18, 2015, 07:59:32 PM

Hi con, looks like we are on the ~~same~~ a near Host:

Code:

PING 84.200.2.30 (84.200.2.30) 56(84) bytes of data.
64 bytes from 84.200.2.30: icmp_req=1 ttl=57 time=0.857 ms
64 bytes from 84.200.2.30: icmp_req=2 ttl=57 time=0.819 ms
64 bytes from 84.200.2.30: icmp_req=3 ttl=57 time=0.856 ms
64 bytes from 84.200.2.30: icmp_req=4 ttl=57 time=0.831 ms

Code:

HOST: xxxxxx.de Loss% Snt Last Avg Best Wrst StDev
1.|-- vh256-9019.1blu.de 0.0% 10 0.0 0.0 0.0 0.1 0.0
2.|-- te0-0-1.g2.blubone.net 0.0% 10 0.3 1.3 0.3 10.8 3.2
3.|-- te0-0-3.g1.blubone.net 0.0% 10 0.4 0.4 0.3 1.3 0.0
4.|-- te1-4.c1.mk.de 0.0% 10 0.4 5.8 0.3 32.4 10.6
5.|-- xe0-0-0.5.e3.mk.de 0.0% 10 0.4 0.4 0.3 0.5 0.0
6.|-- decix.accelerated.de 0.0% 10 0.8 0.7 0.7 0.9 0.0
7.|-- fra1.accelerated.de 0.0% 10 1.1 4.1 0.8 31.1 9.5
8.|-- 84.200.84.203 0.0% 10 0.8 0.9 0.8 1.0 0.0
9.|-- 84.200.2.30 0.0% 10 0.8 0.9 0.8 1.2 0.0

I am actualy setting up my VServer for the company....
Well i got some space.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Just bounced the tube proxy on port 3335 again for updates in case anyone was watching that.

o_solo_miner

legendary

Activity: 2483

Merit: 1482

-> morgen, ist heute, schon gestern <-

Hi con, looks like we are on the ~~same~~ a near Host:

Code:

PING 84.200.2.30 (84.200.2.30) 56(84) bytes of data.
64 bytes from 84.200.2.30: icmp_req=1 ttl=57 time=0.857 ms
64 bytes from 84.200.2.30: icmp_req=2 ttl=57 time=0.819 ms
64 bytes from 84.200.2.30: icmp_req=3 ttl=57 time=0.856 ms
64 bytes from 84.200.2.30: icmp_req=4 ttl=57 time=0.831 ms

Code:

HOST: xxxxxx.de Loss% Snt Last Avg Best Wrst StDev
1.|-- vh256-9019.1blu.de 0.0% 10 0.0 0.0 0.0 0.1 0.0
2.|-- te0-0-1.g2.blubone.net 0.0% 10 0.3 1.3 0.3 10.8 3.2
3.|-- te0-0-3.g1.blubone.net 0.0% 10 0.4 0.4 0.3 1.3 0.0
4.|-- te1-4.c1.mk.de 0.0% 10 0.4 5.8 0.3 32.4 10.6
5.|-- xe0-0-0.5.e3.mk.de 0.0% 10 0.4 0.4 0.3 0.5 0.0
6.|-- decix.accelerated.de 0.0% 10 0.8 0.7 0.7 0.9 0.0
7.|-- fra1.accelerated.de 0.0% 10 1.1 4.1 0.8 31.1 9.5
8.|-- 84.200.84.203 0.0% 10 0.8 0.9 0.8 1.0 0.0
9.|-- 84.200.2.30 0.0% 10 0.8 0.9 0.8 1.2 0.0

I am actualy setting up my VServer for the company....
Well i got some space.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: -ck on December 16, 2015, 06:23:58 PM

I've had a think about it and I figure what I will do is if the de pool solves a block, that will pay for commissioning a better VPS for it and then I'll deploy a more powerful version of it. The only downside to this is that what's really happening is miners are leaving solo.ckpool.org and going to de.ckpool.org so that even though de is proving instantly popular, the solo pools combined will still only be solving the same total number of blocks.

As a followup to this, it appears the combined hashrates of solo and de ARE somewhat more than solo was alone. So I'll keep my promise of creating a more powerful node in DE if it solves a block. The best thing about it is I investigated where I'd be rolling out the more powerful server and it's very close to the existing server so even after migration, those of you are on the DE server will be getting basically identical ping times to what the current server is getting you.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: wmtomlinso on December 18, 2015, 04:20:13 PM

Con,

How much could a dishonest pool operator influence who gets awarded a solo block? is it even possible at all?

I am in NO WAY implying anything about CKpool. I am just curious about other altcoin solo pools coming online now. Can they be trusted?

Realistically you are implicitly putting your trust 100% in the pool operator when you are mining at their pool. It is actually not that hard for them to direct your hashes at whatever they want to direct them to and solve blocks of whatever they want. HOWEVER, since I put block solve detection in cgminer a very long time ago, it is impossible to hide the fact that miners have solved a block and miners tend to notice when they've solved a block - which often leads to confusion if the pool they're mining on is merged mining and solving random altcoin shit blocks which register as block solves on cgminer when people are thinking bitcoin blocks. If miners note a discrepancy in their block solves and the pool's solved blocks they should - and usually do - start shouting loudly. Miners must be eternally vigilant for the implied trust in pool operators is extreme. But this is only vaguely on topic for this thread.

wmtomlinso

member

Activity: 117

Merit: 10

Con,

How much could a dishonest pool operator influence who gets awarded a solo block? is it even possible at all?

I am in NO WAY implying anything about CKpool. I am just curious about other altcoin solo pools coming online now. Can they be trusted?

loshia

legendary

Activity: 1610

Merit: 1000

Quote from: -ck on December 18, 2015, 03:17:38 PM

Quote from: loshia on December 18, 2015, 02:57:07 PM

Con,
Would you be so kind to explain what is the story with this commit.

Don't use persistent connections to bitcoind
https://bitbucket.org/ckolivas/ckpool/commits/d2d5a5daaad5d6e2f969d8479b6752ef667e4b06

I never had an issue with presistent connections to BTCD and lo-127.0.0.1. In my understanding it will take longer to reopen tcp on each rpc call or I am missing something.......

Thanks

Newer bitcoind keeps dropping out during the rpc calls meaning they needed to be reopened and repeated and I needed a workaround - I couldn't find out why it started doing this. In my benchmarking, reopening the connection every time added less than 1ms to rpc calls when the rpc calls themselves take up to 100s of milliseconds but stopped them dropping out in the middle of the rpc calls.

Thank you very much that makes sense.
Best

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: loshia on December 18, 2015, 02:57:07 PM

Con,
Would you be so kind to explain what is the story with this commit.

Don't use persistent connections to bitcoind
https://bitbucket.org/ckolivas/ckpool/commits/d2d5a5daaad5d6e2f969d8479b6752ef667e4b06

I never had an issue with presistent connections to BTCD and lo-127.0.0.1. In my understanding it will take longer to reopen tcp on each rpc call or I am missing something.......

Thanks

Newer bitcoind keeps dropping out during the rpc calls meaning they needed to be reopened and repeated and I needed a workaround - I couldn't find out why it started doing this. In my benchmarking, reopening the connection every time added less than 1ms to rpc calls when the rpc calls themselves take up to 100s of milliseconds but stopped them dropping out in the middle of the rpc calls.

loshia

legendary

Activity: 1610

Merit: 1000

Con,
Would you be so kind to explain what is the story with this commit.

Don't use persistent connections to bitcoind
https://bitbucket.org/ckolivas/ckpool/commits/d2d5a5daaad5d6e2f969d8479b6752ef667e4b06

I never had an issue with presistent connections to BTCD and lo-127.0.0.1. In my understanding it will take longer to reopen tcp on each rpc call or I am missing something.......

Thanks

zOU

hero member

Activity: 728

Merit: 500

★ these are stars ★

360Ths !!! Shocked

Gws24

hero member

Activity: 537

Merit: 524

Quote from: -ck on December 17, 2015, 10:58:03 PM

Code:

[2015-12-18 01:00:03.933] Possible block solve diff 81971938658.699142 !
[2015-12-18 01:00:04.280] BLOCK ACCEPTED!
[2015-12-18 01:00:04.281] Solved and confirmed block 388950 by 1ASM3Rj5FkyGY7hNZBHbkmSf6sj1suDnaC
[2015-12-18 01:00:04.281] User 1ASM3Rj5FkyGY7hNZBHbkmSf6sj1suDnaC:{"hashrate1m": "361T", "hashrate5m": "372T", "hashrate1hr": "386T", "hashrate1d": "101T", "hashrate7d": "19T"}
[2015-12-18 01:00:04.281] Worker 1ASM3Rj5FkyGY7hNZBHbkmSf6sj1suDnaC:{"hashrate1m": "361T", "hashrate5m": "372T", "hashrate1hr": "386T", "hashrate1d": "101T", "hashrate7d": "19T"}

https://www.blocktrail.com/BTC/block/00000000000000000d69be8e223cf97fbffd050d2f099c8de17ddcdd0136e9d6

And I'd like to point out that block was only 3 minutes after the previous block but was still a full block.

Now I'll be restarting the pool as I discussed earlier.

EDIT: Restart complete. Mine on!

Woot! Nice christmas present Grin

Left you something as well Con. Thanks for making this pool and keep up the good work!

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Just dicking with the tube proxy on port 3335 at the moment so you may notice some up and down action.

EDIT: The dicking is over, tube proxy back online working as it was previously.

P4ndoraBox7

sr. member

Activity: 336

Merit: 250

www.DonateMedia.org

Quote from: 727miner on December 17, 2015, 11:36:33 PM

Quote from: P4ndoraBox7 on December 17, 2015, 11:23:56 PM

I think ill join the flow in january with an S4 and S5.

Never a better time than now Wink

Here we go...Just joined. S4 + S5, little overclocking, 3,600 GH/s.

Edit ; changed my mind. I prefer to wait in january.

727miner

hero member

Activity: 543

Merit: 500

Quote from: P4ndoraBox7 on December 17, 2015, 11:23:56 PM

I think ill join the flow in january with an S4 and S5.

Never a better time than now Wink

P4ndoraBox7

sr. member

Activity: 336

Merit: 250

www.DonateMedia.org

I think ill join the flow in january with an S4 and S5.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: nix_on on December 17, 2015, 08:12:52 PM

And the next one Grin

Quote from: 727miner on December 17, 2015, 08:13:10 PM

Congrats to 1ASM3Rj5FkyGY7hNZBHbkmSf6sj1suDnaC Grin

Quote from: madmartyk on December 17, 2015, 08:25:07 PM

Quote from: 727miner on December 17, 2015, 08:13:10 PM

Congrats to 1ASM3Rj5FkyGY7hNZBHbkmSf6sj1suDnaC Grin

Congrats!!!

Code:

[2015-12-18 01:00:03.933] Possible block solve diff 81971938658.699142 !
[2015-12-18 01:00:04.280] BLOCK ACCEPTED!
[2015-12-18 01:00:04.281] Solved and confirmed block 388950 by 1ASM3Rj5FkyGY7hNZBHbkmSf6sj1suDnaC
[2015-12-18 01:00:04.281] User 1ASM3Rj5FkyGY7hNZBHbkmSf6sj1suDnaC:{"hashrate1m": "361T", "hashrate5m": "372T", "hashrate1hr": "386T", "hashrate1d": "101T", "hashrate7d": "19T"}
[2015-12-18 01:00:04.281] Worker 1ASM3Rj5FkyGY7hNZBHbkmSf6sj1suDnaC:{"hashrate1m": "361T", "hashrate5m": "372T", "hashrate1hr": "386T", "hashrate1d": "101T", "hashrate7d": "19T"}

https://www.blocktrail.com/BTC/block/00000000000000000d69be8e223cf97fbffd050d2f099c8de17ddcdd0136e9d6

And I'd like to point out that block was only 3 minutes after the previous block but was still a full block.

Now I'll be restarting the pool as I discussed earlier.

EDIT: Restart complete. Mine on!

madmartyk

legendary

Activity: 2702

Merit: 1030

Yes I am a pirate, 300 years too late!

Quote from: 727miner on December 17, 2015, 08:13:10 PM

Congrats to 1ASM3Rj5FkyGY7hNZBHbkmSf6sj1suDnaC Grin

Congrats!!!

727miner

hero member

Activity: 543

Merit: 500

Congrats to 1ASM3Rj5FkyGY7hNZBHbkmSf6sj1suDnaC Grin

nix_on

full member

Activity: 164

Merit: 100

And the next one Grin

o_solo_miner

legendary

Activity: 2483

Merit: 1482

-> morgen, ist heute, schon gestern <-

and i hope it is my Wallet no. on your screen Wink

Topic: [∞ YH] solo.ckpool.org 2% fee solo mining USA/DE 255 blocks solved! - page 267. (Read 1514780 times)