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

[rimclaw]

how does a miner get the work for eg every miner gets a block to solve or do all miner get the same block to solve ?
and if every miner gets a block to solve and it stops working and after 1 hour it starts again does it continue with the same block or does it start with a new block to solve ?
sorry for the stupid questions as you can see on the left  NEWBIE , i'm just a welder with a big intrest in pc hardware and i don't know anything about programming

You've been around nearly a year... you've had a few posts talking about pump and dumps, seem to understand how to play with cryptsy, etc.  Not sure how much I believe the claims above .

So... the exceedingly simplified answer is that if you shut down your miner for an hour, when you start it back up it will not be working on the same stuff it was when you shut it down.

you can buy and sell welded pipes , but that doesn't mean you know how to weld them  

anyway thanks for the reply  now i understand it and i can throw away an idea i was thinking about

[PublicP2poolNode]

Just got a message a few minutes ago on bitcoin-qt, v0.8.6-beta "warning: This version is obsolete, upgrade required"

Currently mining here on this pool, if I find a block now will I not receive it? Wondering if I need to cancel my rentals until I upgrade the client.

Thanks

[VirosaGITS]

Just got a message a few minutes ago on bitcoin-qt, v0.8.6-beta "warning: This version is obsolete, upgrade required"

Currently mining here on this pool, if I find a block now will I not receive it? Wondering if I need to cancel my rentals until I upgrade the client.

Thanks

I'm not very familiar with bitcoin-qt but regardless, your priv key is your priv key, the public address that it control is yours forever. Unless you lose your privkey/wallet.dat, it does not matter if you upgrade/downgrade the wallet.

You might even be able to get the privkey and import it to another wallet. Though the best thing to do is just to send the whole balance to a new wallet.

Any blocks found here would be safe. Keep a backup of your wallet.dat. Thats how you secure your BTC in any situation.

[-ck]

Just got a message a few minutes ago on bitcoin-qt, v0.8.6-beta "warning: This version is obsolete, upgrade required"

Currently mining here on this pool, if I find a block now will I not receive it? Wondering if I need to cancel my rentals until I upgrade the client.

Thanks

You'll never lose anything that arrives in the wallet. Bitcoin is sent to a wallet address and your wallet has the private key to unlock it. The version of bitcoin-qt you're running will have no effect on the wallet which you keep across upgrades. Just make sure to back your wallet up before upgrading in case of problems. Your bitcoin-qt doesn't even need to be running as the network is what knows where the money is and you unlock access to the money with your wallet.

Short version - no you don't need to cancel your rentals.

[-ck]

The ONLY competition comes where 2 miners solve the current block at around the same time.

I will add for clarity - 2 miners solve the current block at different pools at around the same time.

[chek2fire]

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 ...

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

[rimclaw]

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

[jonnybravo0311]

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.

[-ck]

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.

[kano]

...
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.

[727miner]

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}

[-ck]

Here's how the bestshare number can depress you -- "bestshare": 60343501782.267929

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.

[727miner]

Here's how the bestshare number can depress you -- "bestshare": 60343501782.267929

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!! 

[philipma1957]

Here's how the bestshare number can depress you -- "bestshare": 60343501782.267929

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!

[727miner]

Here's how the bestshare number can depress you -- "bestshare": 60343501782.267929

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 

[os2sam]

Looks like the 106th block was found.

[-ck]

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

[majestymage]

congratulation to the lucky miner! 

[hedgy73]

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 .

[Cheeseater]

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}

Oh man so damn close. Wish you made it that machine has some mojo