Author

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

-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Hi everyone, noob member here introducing myself for the first time!
Been enjoying mining solo on here for sometime so I figured I'd speak up and say hello.

Also, thank you CK for all that you do and the services you provide this community, very appreciative.

Cheers everyone, have a great day!  Grin
Cheers. Welcome, enjoy and good luck!
newbie
Activity: 5
Merit: 0
Hi everyone, noob member here introducing myself for the first time!
Been enjoying mining solo on here for sometime so I figured I'd speak up and say hello.

Also, thank you CK for all that you do and the services you provide this community, very appreciative.

Cheers everyone, have a great day!  Grin
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
CK, do you plan to setup a second pool for solo mining on Bitcoin Cash (BCH)?  The fork is happening.
No. It will be yet another insignificant fork. There's far too much fuss about it just because of its timing being associated with the real changes to bitcoin. It's irrelevant.
newbie
Activity: 6
Merit: 0
CK, do you plan to setup a second pool for solo mining on Bitcoin Cash (BCH)?  The fork is happening.
member
Activity: 98
Merit: 10
Hi, i wanna try Solo Mining with rented hashrate, How much do i have to Rent and what diff should the rented rig have?

 I think a few blocks have been found here with rental power if you have a look back in the topic.

Good luck.
legendary
Activity: 3500
Merit: 2792
Enjoy 500% bonus + 70 FS
Hi, i wanna try Solo Mining with rented hashrate, How much do i have to Rent and what diff should the rented rig have?
On Nicehash it is usually a little cheaper as on Miningrentals ;-)
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Hi, i wanna try Solo Mining with rented hashrate, How much do i have to Rent and what diff should the rented rig have?
The diff doesn't matter and the hashrate is as much as you are willing to gamble on it. A lot of hashrate for a short period is exactly the same as a little bit of hashrate for a long period. The only difference is whether you get your hashes in before the next diff change, so if network diff is set to rise, you should do more hashrate for less time.
member
Activity: 112
Merit: 10
Hi, i wanna try Solo Mining with rented hashrate, How much do i have to Rent and what diff should the rented rig have?
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Pretty big best share already. That would have been a block a few weeks ago if the diff wasn't going to the moon, or maybe more like Saturn.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Except that there was a disagreement about whether they should roll back their block chain to recover the lost funds...
Most specifically funds that were lost privately and having nothing to do with the chain. Angry
Indeed and there have been other funds lost since yet they didn't do a further rollback. What a sham.
hero member
Activity: 1092
Merit: 552
Retired IRCX God
Except that there was a disagreement about whether they should roll back their block chain to recover the lost funds...
Most specifically funds that were lost privately and having nothing to do with the chain. Angry
member
Activity: 98
Merit: 10
I thought the scary time in bitcoin was over but to be honest.. I was wrong Smiley
Indeed everyone's celebrating the safe landing of segwit without a blockchain split but that was never going to be the worrisome part of segwit2x, it's the 2x part Sad

I sat up and watched the block roll in on tradeblock and watched the price rise I thought it was going to hit all time highs so did about 10,000 other people on youtube celebrating on a live stream.

I thought, Hmm,, wonder if they think 2x willl as smooth let alone even understand it.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
I thought the scary time in bitcoin was over but to be honest.. I was wrong Smiley
Indeed everyone's celebrating the safe landing of segwit without a blockchain split but that was never going to be the worrisome part of segwit2x, it's the 2x part Sad
member
Activity: 98
Merit: 10
Possibly to try combat it in future is one reason I think that its got support because no one wants to go through all that carry on again. But I do see now why mess when with something that's not technically broken!
For the reference I have no problem with a 2MB base block size increase. I have a huge problem with a rushed hard fork without core's support which is the one thing most likely to lead to a split in bitcoin since its inception. November 1 is not far away and I see no reconciliation in sight.

Firmly agree with you on that about the rushing point with the market cap bitcoin has now that's a lot of risk to be rushing changes into a system without its outcomes being fully understood or even challenged.

I thought the scary time in bitcoin was over but to be honest.. I was wrong Smiley
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Possibly to try combat it in future is one reason I think that its got support because no one wants to go through all that carry on again. But I do see now why mess when with something that's not technically broken!
For the reference I have no problem with a 2MB base block size increase. I have a huge problem with a rushed hard fork without core's support which is the one thing most likely to lead to a split in bitcoin since its inception. November 1 is not far away and I see no reconciliation in sight.

This sounds like what they did to ETH.
Except that there was a disagreement about whether they should roll back their block chain to recover the lost funds. There's no such disagreement here that we shouldn't do a block size increase at some time, it's just a matter of how soon. Which means that for the sake of a time frame disagreement we're looking at a blockchain split :\
legendary
Activity: 2702
Merit: 1030
Yes I am a pirate, 300 years too late!
Possibly to try combat it in future is one reason I think that its got support because no one wants to go through all that carry on again. But I do see now why mess when with something that's not technically broken!
For the reference I have no problem with a 2MB base block size increase. I have a huge problem with a rushed hard fork without core's support which is the one thing most likely to lead to a split in bitcoin since its inception. November 1 is not far away and I see no reconciliation in sight.

This sounds like what they did to ETH.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Possibly to try combat it in future is one reason I think that its got support because no one wants to go through all that carry on again. But I do see now why mess when with something that's not technically broken!
For the reference I have no problem with a 2MB base block size increase. I have a huge problem with a rushed hard fork without core's support which is the one thing most likely to lead to a split in bitcoin since its inception. November 1 is not far away and I see no reconciliation in sight.
member
Activity: 98
Merit: 10
Block #477392 solved by 1MEq97jjRKrmSwgVLJirB1ZcrEvnURUAhj

 Grin congratulation
I second that! Congrats!

https://www.blocktrail.com/BTC/block/0000000000000000012288cec644c7ab65fcce61adaf30316ce1ccfcc99791f9


Code:
[2017-07-24 12:59:47.557] Possible block solve diff 968803270026.079346 ! 
[2017-07-24 12:59:47.652] BLOCK ACCEPTED!
[2017-07-24 12:59:47.670] Solved and confirmed block 477392 by 1MEq97jjRKrmSwgVLJirB1ZcrEvnURUAhj.r35192
[2017-07-24 12:59:47.670] User 1MEq97jjRKrmSwgVLJirB1ZcrEvnURUAhj:{"hashrate1m": "405T", "hashrate5m": "400T", "hashrate1hr": "383T", "hashrate1d": "87.2T", "hashrate7d": "118T"}
[2017-07-24 12:59:47.670] Worker 1MEq97jjRKrmSwgVLJirB1ZcrEvnURUAhj.r35192:{"hashrate1m": "318T", "hashrate5m": "310T", "hashrate1hr": "296T", "hashrate1d": "40.5T", "hashrate7d": "50.2T"}
[2017-07-24 12:59:47.673] Block solved after 113994199677 shares at 14.2% diff

Lucky block  Smiley It was only 12 seconds after the block before it.

Code:
2017-07-24 17:59:35.610026 UpdateTip: new best=000000000000000001290cd8f91689506ce1f38e05acdf1ec1d3fcdcc52c6535 height=477391 version=0x20000002 log2_work=86.817537 tx=241568059 date='2017-07-24 17:59:27' progres
s=1.000000 cache=617.8MiB(303646tx)
2017-07-24 17:59:47.648430 UpdateTip: new best=0000000000000000012288cec644c7ab65fcce61adaf30316ce1ccfcc99791f9 height=477392 version=0x20000002 log2_work=86.817573 tx=241570404 date='2017-07-24 17:59:35' progres
s=1.000000 cache=618.2MiB(305602tx)
Interestingly enough the block wasn't even full because the pool's bitcoind memory pool was almost completely empty after that block because it was so close to the one before it. Makes one wonder about what the urgency is for 2 capacity increases in the blockchain now that the transaction spam has ended...

Possibly to try combat it in future is one reason I think that its got support because no one wants to go through all that carry on again. But I do see now why mess when with something that's not technically broken!

Congratulations to the block finders!

-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Block #477392 solved by 1MEq97jjRKrmSwgVLJirB1ZcrEvnURUAhj

 Grin congratulation
I second that! Congrats!

https://www.blocktrail.com/BTC/block/0000000000000000012288cec644c7ab65fcce61adaf30316ce1ccfcc99791f9


Code:
[2017-07-24 12:59:47.557] Possible block solve diff 968803270026.079346 ! 
[2017-07-24 12:59:47.652] BLOCK ACCEPTED!
[2017-07-24 12:59:47.670] Solved and confirmed block 477392 by 1MEq97jjRKrmSwgVLJirB1ZcrEvnURUAhj.r35192
[2017-07-24 12:59:47.670] User 1MEq97jjRKrmSwgVLJirB1ZcrEvnURUAhj:{"hashrate1m": "405T", "hashrate5m": "400T", "hashrate1hr": "383T", "hashrate1d": "87.2T", "hashrate7d": "118T"}
[2017-07-24 12:59:47.670] Worker 1MEq97jjRKrmSwgVLJirB1ZcrEvnURUAhj.r35192:{"hashrate1m": "318T", "hashrate5m": "310T", "hashrate1hr": "296T", "hashrate1d": "40.5T", "hashrate7d": "50.2T"}
[2017-07-24 12:59:47.673] Block solved after 113994199677 shares at 14.2% diff

Lucky block  Smiley It was only 12 seconds after the block before it.

Code:
2017-07-24 17:59:35.610026 UpdateTip: new best=000000000000000001290cd8f91689506ce1f38e05acdf1ec1d3fcdcc52c6535 height=477391 version=0x20000002 log2_work=86.817537 tx=241568059 date='2017-07-24 17:59:27' progres
s=1.000000 cache=617.8MiB(303646tx)
2017-07-24 17:59:47.648430 UpdateTip: new best=0000000000000000012288cec644c7ab65fcce61adaf30316ce1ccfcc99791f9 height=477392 version=0x20000002 log2_work=86.817573 tx=241570404 date='2017-07-24 17:59:35' progres
s=1.000000 cache=618.2MiB(305602tx)
Interestingly enough the block wasn't even full because the pool's bitcoind memory pool was almost completely empty after that block because it was so close to the one before it. Makes one wonder about what the urgency is for 2 capacity increases in the blockchain now that the transaction spam has ended...
legendary
Activity: 2483
Merit: 1482
-> morgen, ist heute, schon gestern <-
Block #477392 solved by 1MEq97jjRKrmSwgVLJirB1ZcrEvnURUAhj

 Grin congratulation
Jump to: