Happy Days!!  Thanks Hurricanedave.. Seems you have some lucky machines:) Much appreciated!! Best Regards d57heinz I want to know what rigs he is using? What diff he has set manually on particular rigs, if any? etc. All of us could share these type of things with one another to possibly increase our odds of maybe finding more blocks as a pool. Im not sure if there is anything to this and im sure kano will shed some light on this. But here is what i was thinking.. if you have a pool server that is capable of handling a vast amount of shares per second.> Wouldnt it be advantageous to send the miners more shares per second with each one of them having an equal chance of finding a block.. So i guess what im trying to say is if you send s4 diff 2000 shares and it can send one share a second.. vs sending your rig 1k diff shares at 2 per second.. Wouldnt that give the machine a twice as much chance at finding a block.. Im prolly way off on my thinking here. what you all think? Best Regards d57heinz No, it doesn't work like that. The machine doesn't have any better or worse chance of finding a block by submitting a diff 1 share or a diff 1,000,000,000 share. The diff setting is there simply for the pool to reduce the amount of traffic it receives and the amount of data it must store. Ahh ok.. Thanks for straightening me out.. Appreciate that. Edit.. but the time the machine takes to submit that diff one share is much faster than the diff 1 billion share.. Correct.. its a time issue then .. You want to submit as many chances as possible. not sure im cleared up just yet lol Best Regards d57heinz Yes, statistically submitting a share with a 1G difficulty would take longer than submitting a share with a 1 difficulty. That's why pools try to target a given shares per second rate. Kano's pool targets 18 shares per minute, so it'll adjust your share difficulty accordingly to get as close to that target as possible. |
|
|
|
Happy Days!! Thanks Hurricanedave.. Seems you have some lucky machines:) Much appreciated!! Best Regards d57heinz I want to know what rigs he is using? What diff he has set manually on particular rigs, if any? etc. All of us could share these type of things with one another to possibly increase our odds of maybe finding more blocks as a pool. Im not sure if there is anything to this and im sure kano will shed some light on this. But here is what i was thinking.. if you have a pool server that is capable of handling a vast amount of shares per second.> Wouldnt it be advantageous to send the miners more shares per second with each one of them having an equal chance of finding a block.. So i guess what im trying to say is if you send s4 diff 2000 shares and it can send one share a second.. vs sending your rig 1k diff shares at 2 per second.. Wouldnt that give the machine a twice as much chance at finding a block.. Im prolly way off on my thinking here. what you all think? Best Regards d57heinz No, it doesn't work like that. The machine doesn't have any better or worse chance of finding a block by submitting a diff 1 share or a diff 1,000,000,000 share. The diff setting is there simply for the pool to reduce the amount of traffic it receives and the amount of data it must store. |
|
|
|
Good luck! I hope to be able to award the prize  |
|
|
|
|
That would be great if it was indeed your s3 that found it!
|
|
|
|
Absolutely. The p2pool code will attempt to prevent this by forcing a higher and higher difficulty onto miners on the node; however, it can be overridden by the miner providing it manually.
You can override the difficulty higher on a node but you can't force it lower than p2pool demands. Correct. The lowest you can set it is to the p2pool minimum share difficulty. The problem with that approach is that with a giant hash rate, you're going to flood the share chain. P2Pool will eventually adapt to the added hash rate by increasing the share minimum difficulty, but it still won't compensate if you're a majority of the pool's hash. This will lead directly to what kano posited earlier: everyone else's shares will be orphaned if you've got >51% of the pool's total hash rate. As a "nice actor" you would allow your node to dynamically adjust your share rate, or you would manually set it to something high enough not to cause the situation previously listed. |
|
|
|
|
Definitely not a block of BTC... share value is too low.
|
|
|
|
|
That's a very cool site, o_solo_miner. Thanks for the link!
|
|
|
|
|
Luck most certainly can and will change that amount. Just like good luck means you'll make more than expectations, bad luck means the opposite.
|
|
|
|
Poor little lonely prize BTC. Sitting all alone in a wallet. No friends. No one to play with. Help this poor coin find a home. Find a block and take him home with you. |
|
|
|
wouldn't the sharechain have the same problem as the BTC blockchain orphaning everyone else's blocks if > 51% and often if close to that?
Absolutely. The p2pool code will attempt to prevent this by forcing a higher and higher difficulty onto miners on the node; however, it can be overridden by the miner providing it manually. |
|
|
|
|
That it is. Statistically we are still well in the good luck territory at 53%. Also remember the holiday promotion is still going, so if anyone hits a block before the new year you get 1BTC bonus from me.
I'm quite hopeful we hit a block this week and somebody gets the prize!
|
|
|
|
Well, nobody hit the Christmas bonus... so we move on to hoping somebody brings the new year in with a bang! I hope everyone's Christmas was filled with cheer and that Santa brought you everything on your lists. I'm sorry Santa Satoshi didn't stop by as well  |
|
|
|
Ultimately, the choice is yours. You certainly seem to have done some research. I would stay away from the big pools - not only because they're big, but because the top couple use SPV mining. Mining on any pool with any payout other than PPS will mean you suffer from variance. The pool gets lucky, you get lucky. The pool is unlucky, so are you. Obviously, the smaller the pool, the more profound that effect will be. I'd love to see your hash at my own pool, but since the variance at a pool with 3PH scares you, well... you're certainly welcome to come on over. I suggest diversifying your hash. Point it to multiple pools. If you like bitminter, kano and Eligius, then go for it. You've got nearly 30TH/s... so point 10 at each of them . |
|
|
|
|
Well my rental ran out during the night with no luck. I'll probably do another one next week. I'm really hoping somebody gets lucky and wins the prize!
Hope everyone is having a great Christmas!
|
|
|
|
|
Happy first birthday to your boy!
|
|
|
|
LOL... I was holding a glass of bourbon while I was writing it and that was the inspiration for the analogy I used In other news, we're still holding strong at over 500TH. Let's crack that block today so I can give somebody a nice little Christmas bonus! |
|
|
|
LOL... skills as a pool operator have nothing to do with it . Christmas miracle? Far more likely explanation  . Personally, I love it when some tiny hash finds a block. Folks rent petahash all the time with no luck, then some guy with an S5 hits. I'm still waiting for one my of old U2 sticks to hit a block... my own gear has only ever hit 1 block. An S1 I had hit early in 2014 on p2pool. Nothing since then. Rented hash, I've hit a couple (1 on Nexious - and uncovered his con and 1 on my pool). |
|
|
|
|
That sounds fun, too!
All of these things we're thinking about doing when normally it's, "I've got to shovel the damn walkway again!" or "Hey, the high is supposed to be 30 degrees tomorrow, it's a heat wave!"
|
|
|
|
|
Congrats on your first block solve... and absolutely absurd good luck, too. Only 364,375,814 shares. That's 0.38%.
|
|
|
|
|
Show Posts
