Topic: [∞ YH] solo.ckpool.org 2% fee solo mining USA/DE 255 blocks solved! - page 322. (Read 1514894 times)
October 11, 2015, 05:31:39 AM
When I find some hardware in Australia I will definitely be giving this a go!
October 11, 2015, 05:21:33 AM
Here's how the bestshare number can depress you -- "bestshare": 60343501782.267929
Found with my s4p this morning
Found with my s4p this morning
That's so fucking sad. Even the pool noticed it.
Code:
[2015-10-10 11:57:29.076] Possible block solve diff 60343501782.267929 !
[2015-10-10 11:57:29.141] SUBMIT BLOCK RETURNED: high-hash
[2015-10-10 11:57:29.141] Submitted, but rejected block 378262
[2015-10-10 11:57:29.141] SUBMIT BLOCK RETURNED: high-hash
[2015-10-10 11:57:29.141] Submitted, but rejected block 378262
Ckpool submits anything 99%+ just in case there's a rounding error somewhere and it's a block solve... and it wasn'
Damn, so close!!
Wow missed it by that much!
Looks like 3 seconds behind Slush.
October 11, 2015, 04:27:23 AM
Here's how the bestshare number can depress you -- "bestshare": 60343501782.267929
Found with my s4p this morning
Found with my s4p this morning
That's so fucking sad. Even the pool noticed it.
Code:
[2015-10-10 11:57:29.076] Possible block solve diff 60343501782.267929 !
[2015-10-10 11:57:29.141] SUBMIT BLOCK RETURNED: high-hash
[2015-10-10 11:57:29.141] Submitted, but rejected block 378262
[2015-10-10 11:57:29.141] SUBMIT BLOCK RETURNED: high-hash
[2015-10-10 11:57:29.141] Submitted, but rejected block 378262
Ckpool submits anything 99%+ just in case there's a rounding error somewhere and it's a block solve... and it wasn'
Damn, so close!!
Wow missed it by that much!
Looks like 3 seconds behind Slush.
October 11, 2015, 03:00:32 AM
I added to the pool, let's see if I have a little luck 
October 10, 2015, 10:29:04 PM
Here's how the bestshare number can depress you -- "bestshare": 60343501782.267929
Found with my s4+ this morning
{"hashrate1m": "2.21T", "hashrate5m": "2.26T", "hashrate1hr": "2.53T", "hashrate1d": "2.53T", "hashrate7d": "1.35T", "lastupdate": 1444482600, "shares": 273981867, "bestshare": 60343501782.267929}
Found with my s4+ this morning
{"hashrate1m": "2.21T", "hashrate5m": "2.26T", "hashrate1hr": "2.53T", "hashrate1d": "2.53T", "hashrate7d": "1.35T", "lastupdate": 1444482600, "shares": 273981867, "bestshare": 60343501782.267929}
Oh man so damn close. Wish you made it that machine has some mojo
I know!! I'm just going to leave it alone and not reboot it or mess with it. It has been banging away for 2+ weeks uninterrupted and maybe it will go bigger next time
October 10, 2015, 05:41:15 PM
Here's how the bestshare number can depress you -- "bestshare": 60343501782.267929
Found with my s4+ this morning
{"hashrate1m": "2.21T", "hashrate5m": "2.26T", "hashrate1hr": "2.53T", "hashrate1d": "2.53T", "hashrate7d": "1.35T", "lastupdate": 1444482600, "shares": 273981867, "bestshare": 60343501782.267929}
Found with my s4+ this morning
{"hashrate1m": "2.21T", "hashrate5m": "2.26T", "hashrate1hr": "2.53T", "hashrate1d": "2.53T", "hashrate7d": "1.35T", "lastupdate": 1444482600, "shares": 273981867, "bestshare": 60343501782.267929}
Oh man so damn close. Wish you made it that machine has some mojo
October 10, 2015, 04:39:38 PM
congratulation to the lucky miner! 
Yes very much so congratulations to block finder
. Gonna throw 200TH at the pool for a 4 hours, feeling lucky . 
October 10, 2015, 04:33:31 PM
congratulation to the lucky miner!
October 10, 2015, 04:24:11 PM
Code:
[2015-10-10 21:05:59.822] Possible block solve diff 65767357175.105324 !
[2015-10-10 21:06:00.867] BLOCK ACCEPTED!
[2015-10-10 21:06:00.869] Solved and confirmed block 378328 by 1NsBhqV24cvcccT5dMnpQV5LYvJ7rupRg9.125
https://www.blocktrail.com/BTC/block/000000000000000010b7cb08e6913246f7ec8cb7a86d2db7235c40c9c574fa21
October 10, 2015, 04:20:13 PM
Looks like the 106th block was found.
October 10, 2015, 08:26:08 AM
Here's how the bestshare number can depress you -- "bestshare": 60343501782.267929
Found with my s4p this morning
Found with my s4p this morning
That's so fucking sad. Even the pool noticed it.
Code:
[2015-10-10 11:57:29.076] Possible block solve diff 60343501782.267929 !
[2015-10-10 11:57:29.141] SUBMIT BLOCK RETURNED: high-hash
[2015-10-10 11:57:29.141] Submitted, but rejected block 378262
Ckpool submits anything 99%+ just in case there's a rounding error somewhere and it's a block solve... and it wasn'
Damn, so close!!
Wow missed it by that much!
Yeah, if it was 2 weeks ago that would've been a solve
October 10, 2015, 08:17:16 AM
Here's how the bestshare number can depress you -- "bestshare": 60343501782.267929
Found with my s4p this morning
Found with my s4p this morning
That's so fucking sad. Even the pool noticed it.
Code:
[2015-10-10 11:57:29.076] Possible block solve diff 60343501782.267929 !
[2015-10-10 11:57:29.141] SUBMIT BLOCK RETURNED: high-hash
[2015-10-10 11:57:29.141] Submitted, but rejected block 378262
Ckpool submits anything 99%+ just in case there's a rounding error somewhere and it's a block solve... and it wasn'
Damn, so close!!
Wow missed it by that much!
October 10, 2015, 08:12:44 AM
Here's how the bestshare number can depress you -- "bestshare": 60343501782.267929
Found with my s4p this morning
Found with my s4p this morning
That's so fucking sad. Even the pool noticed it.
Code:
[2015-10-10 11:57:29.076] Possible block solve diff 60343501782.267929 !
[2015-10-10 11:57:29.141] SUBMIT BLOCK RETURNED: high-hash
[2015-10-10 11:57:29.141] Submitted, but rejected block 378262
Ckpool submits anything 99%+ just in case there's a rounding error somewhere and it's a block solve... and it wasn't.
Damn, so close!!
October 10, 2015, 08:11:46 AM
Here's how the bestshare number can depress you -- "bestshare": 60343501782.267929
Found with my s4p this morning
Found with my s4p this morning
That's so fucking sad. Even the pool noticed it.
Code:
[2015-10-10 11:57:29.076] Possible block solve diff 60343501782.267929 !
[2015-10-10 11:57:29.141] SUBMIT BLOCK RETURNED: high-hash
[2015-10-10 11:57:29.141] Submitted, but rejected block 378262
Ckpool submits anything 99%+ just in case there's a rounding error somewhere and it's a block solve... and it wasn't.
October 10, 2015, 08:10:19 AM
Here's how the bestshare number can depress you -- "bestshare": 60343501782.267929
Found with my s4+ this morning
{"hashrate1m": "2.21T", "hashrate5m": "2.26T", "hashrate1hr": "2.53T", "hashrate1d": "2.53T", "hashrate7d": "1.35T", "lastupdate": 1444482600, "shares": 273981867, "bestshare": 60343501782.267929}
Found with my s4+ this morning
{"hashrate1m": "2.21T", "hashrate5m": "2.26T", "hashrate1hr": "2.53T", "hashrate1d": "2.53T", "hashrate7d": "1.35T", "lastupdate": 1444482600, "shares": 273981867, "bestshare": 60343501782.267929}
October 08, 2015, 05:33:13 PM
...
what i don't get is i was in a pool that has 3400thps and i solved or found a block with my 2 antminers s1's in 10 hours
or is this just luck to find it and badluck to be in a pool .
...
Also note that because you find a block mining with one configuration (solo, pool, whatever) if you had been mining with a different configuration (different pool, different solo address etc) you would not have found the same block and may have found more or less blocks, but the amount directly unrelated to how many you did find. what i don't get is i was in a pool that has 3400thps and i solved or found a block with my 2 antminers s1's in 10 hours
or is this just luck to find it and badluck to be in a pool .
...
October 08, 2015, 03:14:30 PM
what i don't get is i was in a pool that has 3400thps and i solved or found a block with my 2 antminers s1's in 10 hours
or is this just luck to find it and badluck to be in a pool .
It's just luck. or is this just luck to find it and badluck to be in a pool .
October 08, 2015, 12:39:55 PM
To solve the most blocks, you need the most hashing power. You as a miner want to have a decently good network connection from your miner(s) out to the internet, and a low ping to the pool on which you're mining. This is because you want to obtain new work from the pool as quickly as possible, and submit work you've completed to the pool as quickly as possible.
October 08, 2015, 12:28:42 PM
so in order to solve the most blocks you need a fast connection like fiberoptic to be the first and minimize the lag
and ofcorse the hashpower
what i don't get is i was in a pool that has 3400thps and i solved or found a block with my 2 antminers s1's in 10 hours
or is this just luck to find it and badluck to be in a pool .
height created duration work diff cdf pool thps type made
375440 2015-09-21 07:11 10h 01m 27,561,551,168 59,335,351,233 37.2% 3,278.7 BTC rimclaw confirmed
and ofcorse the hashpower
what i don't get is i was in a pool that has 3400thps and i solved or found a block with my 2 antminers s1's in 10 hours
or is this just luck to find it and badluck to be in a pool .
height created duration work diff cdf pool thps type made
375440 2015-09-21 07:11 10h 01m 27,561,551,168 59,335,351,233 37.2% 3,278.7 BTC rimclaw confirmed
October 08, 2015, 06:56:10 AM
Or in miner terms
Every 30s you get new work to add to what you are doing - that you switch to for all new hashing you do.
Every network block change you get new work that invalidates all work you are currently doing, that you switch to immediately.
Each new work item is unique per miner instance - which of course it must be otherwise people would be duplicating hashes.
i.e. everyone on the internet is effectively always trying to solve a different block header - they just happen to have the same previous block hash and the same block number.
The ONLY competition comes where 2 miners solve the current block at around the same time.
The question then is who's network distribution of their block solution is the best to give the best chance of their block being confirmed by the NEXT block.
Or in 'pool' terms: does the pool you are mining to handle block changes fast or does it suck in terms of block change handling ...
Every 30s you get new work to add to what you are doing - that you switch to for all new hashing you do.
Every network block change you get new work that invalidates all work you are currently doing, that you switch to immediately.
Each new work item is unique per miner instance - which of course it must be otherwise people would be duplicating hashes.
i.e. everyone on the internet is effectively always trying to solve a different block header - they just happen to have the same previous block hash and the same block number.
The ONLY competition comes where 2 miners solve the current block at around the same time.
The question then is who's network distribution of their block solution is the best to give the best chance of their block being confirmed by the NEXT block.
Or in 'pool' terms: does the pool you are mining to handle block changes fast or does it suck in terms of block change handling ...
and this is the real big problem about the big mb block. If we have an increase of mb in each block the pool that will solved will go ahead from others to solve the next block because of the network lag to transmit the previous blog
Jump to: