Bitcoin Forum
December 07, 2016, 04:24:17 PM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 [497] 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 ... 744 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2032446 times)
kgb2mining
Member
**
Offline Offline

Activity: 112


View Profile
August 07, 2014, 02:22:48 PM
 #9921

/#+# should only be needed if your running on a node that has other miners on it that are not yours. Otherwise it may be best to let it autoadjust...i.e. don't use it.
Removing this from my miners now, to see if there's any noticeable difference after running them with the /+ for a few days.  Since I'm now on my own node it should also hopefully not matter as was pointed out.
1481127857
Hero Member
*
Offline Offline

Posts: 1481127857

View Profile Personal Message (Offline)

Ignore
1481127857
Reply with quote  #2

1481127857
Report to moderator
1481127857
Hero Member
*
Offline Offline

Posts: 1481127857

View Profile Personal Message (Offline)

Ignore
1481127857
Reply with quote  #2

1481127857
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481127857
Hero Member
*
Offline Offline

Posts: 1481127857

View Profile Personal Message (Offline)

Ignore
1481127857
Reply with quote  #2

1481127857
Report to moderator
1481127857
Hero Member
*
Offline Offline

Posts: 1481127857

View Profile Personal Message (Offline)

Ignore
1481127857
Reply with quote  #2

1481127857
Report to moderator
1481127857
Hero Member
*
Offline Offline

Posts: 1481127857

View Profile Personal Message (Offline)

Ignore
1481127857
Reply with quote  #2

1481127857
Report to moderator
dlasher
Sr. Member
****
Offline Offline

Activity: 468



View Profile WWW
August 07, 2014, 07:59:51 PM
 #9922



Any quick fix for getting pypy happy with twisted on Ubuntu 14 LTS? python-twisted is installed, python runs p2pool just fine, but trying to run it with pypy errors:

Quote
bitcoind@p2pool:~/p2pool$ pypy run_p2pool.py
Traceback (most recent call last):
  File "app_main.py", line 72, in run_toplevel
  File "/home/bitcoind/p2pool/run_p2pool.py", line 3, in <module>
    from p2pool import main
  File "/home/bitcoind/p2pool/p2pool/main.py", line 17, in <module>
    from twisted.internet import defer, reactor, protocol, tcp
ImportError: No module named twisted
ceslick
Full Member
***
Offline Offline

Activity: 161

digging in the bits... now ant powered!


View Profile WWW
August 07, 2014, 08:31:39 PM
 #9923

Variance is being a bi@tch... no shares in over 30hours on 800GHS!! Expected payouts dropped form 0.02 to 0.003!!!

May the God's of Share smile upon me again!

http://www.integratedideas.net  - Home of Rock Solid Miners
NZ Based BTC P2Pool: http://www.integratedideas.net/p2pool-btc/  -  NZ Based DOGE P2Pool: http://www.integratedideas.net/p2pool-doge/
Cloud mining with CEX.IO: https://cex.io/r/2/ceslicknz/0/
kebabman
Hero Member
*****
Offline Offline

Activity: 532


You wan chili saus?


View Profile
August 07, 2014, 10:52:11 PM
 #9924

So, my local node is up and running all happy, and I have a couple miners pointed to it.  All I have to say is - Holy good DOA Batman!  Local node DOA rates so far are well under 2%, hovering around 1.1-1..2% pretty consistently, for around 2.6Th/s.  Will see how things progress over time and if all stays good I'll point all my miners to it.

Right now have 6 outbound peers, 0 in until we get the DMZ openings done.  Seems to be working fine without opening it so far.

So, silly n00b P2Pool question - if I use the same mining address as I switch pools, will the share history cross over?  I've been mining on coincadence and have obviously much share history there, will it transfer so I don't have any gaps in my earnings?

What was your DOA on Coincadence? New to p2pool and trying to work out what a "good" effiency for a node is, I see Coincadence runs about 90%, what does your local node run at?

Can you also let us know what your earnings are like on local node vs your time on Coincadence please, I'm debating setting up my own node, but want to know it's worth the effort first. Thanks! Smiley
contactlight
Full Member
***
Offline Offline

Activity: 168


View Profile
August 07, 2014, 11:01:51 PM
 #9925

So, my local node is up and running all happy, and I have a couple miners pointed to it.  All I have to say is - Holy good DOA Batman!  Local node DOA rates so far are well under 2%, hovering around 1.1-1..2% pretty consistently, for around 2.6Th/s.  Will see how things progress over time and if all stays good I'll point all my miners to it.

Right now have 6 outbound peers, 0 in until we get the DMZ openings done.  Seems to be working fine without opening it so far.

So, silly n00b P2Pool question - if I use the same mining address as I switch pools, will the share history cross over?  I've been mining on coincadence and have obviously much share history there, will it transfer so I don't have any gaps in my earnings?

What was your DOA on Coincadence? New to p2pool and trying to work out what a "good" effiency for a node is, I see Coincadence runs about 90%, what does your local node run at?

Can you also let us know what your earnings are like on local node vs your time on Coincadence please, I'm debating setting up my own node, but want to know it's worth the effort first. Thanks! Smiley

I get about 5-6% DOA on Coincadance but anything below the global P2Pool DOA is good enough. The lower the better obviously.

When I set up my node, my DOA was around 2-3%. It was consistently lower than Coincadance but I like the user interface there.
CartmanSPC
Legendary
*
Offline Offline

Activity: 1148



View Profile WWW
August 07, 2014, 11:33:33 PM
 #9926

Having looked into the effect of using /# on BTC it appears that the p2pool hash rate is so large that most miners are already running at the minimum p2pool share diff. Unless you are on a node that has over 1.6% (something like that) of the hash rate for p2pool you should be getting the lowest possible share diff....so for BTC it shouldn't really matter if you use /# unless you are on an extreamly large node.

The problem is that the lowest possible share diff is so large that miners with lower hashrate are missing blocks since they are not getting shares into the chain in a timely manner...hence the scalability issue. Will only get worse for the smaller miners as more hashrate is added to p2pool.

For example this guy with 143 Gh/s is estimated to get a share every 1d 18h and already has the lowest possible p2pool share diff.



Expected Time to Block on p2pool is 0d 12h 19m 11s so they are missing payments on blocks due to not being able to get a share in time.



Again, after seeing that the minimum p2pool share diff has gotten so high I don't think /# will make a difference unless you are on a "public" node with more than 1.6% of the p2pool hashrate.

+# is a different story but I'll leave that for another time  Smiley

How's that saying go, damn if you do; damned if you don't. It appears that the larger p2pool gets the worse it is for smaller miners....quite the dilemma since it needs to keep getting bigger to stay relevant.

squashpile
Full Member
***
Offline Offline

Activity: 125


View Profile WWW
August 08, 2014, 12:36:58 AM
 #9927

lol no doubt.. miner with lowest hashrate with twice the expected payout on my pool ATM. Some crappy ass luck on my S3's lately lol

Haa.. few min after I posted, but yeah.
2014-08-07 19:40:02.847245 GOT SHARE!

Variance is being a bi@tch... no shares in over 30hours on 800GHS!! Expected payouts dropped form 0.02 to 0.003!!!

May the God's of Share smile upon me again!

SquashPool - 0% Fee - Dedicated P2Pool VPS - Atlanta, GA - SSD - Gig uplink
kgb2mining
Member
**
Offline Offline

Activity: 112


View Profile
August 08, 2014, 02:18:24 AM
 #9928

What was your DOA on Coincadence? New to p2pool and trying to work out what a "good" effiency for a node is, I see Coincadence runs about 90%, what does your local node run at?

Can you also let us know what your earnings are like on local node vs your time on Coincadence please, I'm debating setting up my own node, but want to know it's worth the effort first. Thanks! Smiley
Cliff notes - IMHO if you have the resources to do it, I would recommend it.  It's an easy enough setup and I am now a firm believer that latency really counts for a lot when dealing with P2Pool.  For full explanation, read on... Wink

DOA over there was on average 8-10%, with it recently staying in the low teens for a good amount of time.  Right now I seem to be hovering between 2-4% on average, a marked improvement.  I'm about 36 hours up on my node, and I have 34 shares, 3 dead, 1 orphan, 105.1% efficiency so far.  I've been up as high as 112.4% earlier today, but I've seen no lower than 98%.

I've split my miners into 4 separate groups with separate addresses.  I have 3 groups of 12 S1's, and a group of 2 Terraminers for a total of just around 9.2TH.  This was done for a couple reasons, but mainly to try to keep the hashrates for each "miner" similar so there wouldn't be too much share diff variance.  I believe it's not supposed to matter if it's your own node, but it's working out well so far having it this way.

For earnings, honestly at the moment I'm not sure because the default interface is extremely hard to read, plus I don't have a long enough run with all my mining groups to really have it stable, the payouts are still normalizing.  I "think" my earnings are better so far but I'm having a hard time telling from these graphs.

I have to say the work windpath has done on his interface is phenomenal, it's so much better than the default it's not even funny.  His interface makes all of the information you want to see very well organized and easy to look and tell within seconds of looking at the interface.  If I wasn't seeing such an improvement in the DOA and efficiency numbers, I would go back to mining there just for the interface.
contactlight
Full Member
***
Offline Offline

Activity: 168


View Profile
August 08, 2014, 02:49:05 AM
 #9929

What was your DOA on Coincadence? New to p2pool and trying to work out what a "good" effiency for a node is, I see Coincadence runs about 90%, what does your local node run at?

Can you also let us know what your earnings are like on local node vs your time on Coincadence please, I'm debating setting up my own node, but want to know it's worth the effort first. Thanks! Smiley
Cliff notes - IMHO if you have the resources to do it, I would recommend it.  It's an easy enough setup and I am now a firm believer that latency really counts for a lot when dealing with P2Pool.  For full explanation, read on... Wink

DOA over there was on average 8-10%, with it recently staying in the low teens for a good amount of time.  Right now I seem to be hovering between 2-4% on average, a marked improvement.  I'm about 36 hours up on my node, and I have 34 shares, 3 dead, 1 orphan, 105.1% efficiency so far.  I've been up as high as 112.4% earlier today, but I've seen no lower than 98%.

I've split my miners into 4 separate groups with separate addresses.  I have 3 groups of 12 S1's, and a group of 2 Terraminers for a total of just around 9.2TH.  This was done for a couple reasons, but mainly to try to keep the hashrates for each "miner" similar so there wouldn't be too much share diff variance.  I believe it's not supposed to matter if it's your own node, but it's working out well so far having it this way.

For earnings, honestly at the moment I'm not sure because the default interface is extremely hard to read, plus I don't have a long enough run with all my mining groups to really have it stable, the payouts are still normalizing.  I "think" my earnings are better so far but I'm having a hard time telling from these graphs.

I have to say the work windpath has done on his interface is phenomenal, it's so much better than the default it's not even funny.  His interface makes all of the information you want to see very well organized and easy to look and tell within seconds of looking at the interface.  If I wasn't seeing such an improvement in the DOA and efficiency numbers, I would go back to mining there just for the interface.


I wish he opensourced the interface.
ftoole
Member
**
Offline Offline

Activity: 118


View Profile
August 08, 2014, 02:51:43 AM
 #9930

What was your DOA on Coincadence? New to p2pool and trying to work out what a "good" effiency for a node is, I see Coincadence runs about 90%, what does your local node run at?

Can you also let us know what your earnings are like on local node vs your time on Coincadence please, I'm debating setting up my own node, but want to know it's worth the effort first. Thanks! Smiley
Cliff notes - IMHO if you have the resources to do it, I would recommend it.  It's an easy enough setup and I am now a firm believer that latency really counts for a lot when dealing with P2Pool.  For full explanation, read on... Wink

DOA over there was on average 8-10%, with it recently staying in the low teens for a good amount of time.  Right now I seem to be hovering between 2-4% on average, a marked improvement.  I'm about 36 hours up on my node, and I have 34 shares, 3 dead, 1 orphan, 105.1% efficiency so far.  I've been up as high as 112.4% earlier today, but I've seen no lower than 98%.

I've split my miners into 4 separate groups with separate addresses.  I have 3 groups of 12 S1's, and a group of 2 Terraminers for a total of just around 9.2TH.  This was done for a couple reasons, but mainly to try to keep the hashrates for each "miner" similar so there wouldn't be too much share diff variance.  I believe it's not supposed to matter if it's your own node, but it's working out well so far having it this way.

For earnings, honestly at the moment I'm not sure because the default interface is extremely hard to read, plus I don't have a long enough run with all my mining groups to really have it stable, the payouts are still normalizing.  I "think" my earnings are better so far but I'm having a hard time telling from these graphs.

I have to say the work windpath has done on his interface is phenomenal, it's so much better than the default it's not even funny.  His interface makes all of the information you want to see very well organized and easy to look and tell within seconds of looking at the interface.  If I wasn't seeing such an improvement in the DOA and efficiency numbers, I would go back to mining there just for the interface.


I wish he opensourced the interface.
He is releasing it in November he stated in one of his posts.
flound1129
Hero Member
*****
Offline Offline

Activity: 798


www.multipool.us


View Profile
August 08, 2014, 02:53:54 AM
 #9931


How's that saying go, damn if you do; damned if you don't. It appears that the larger p2pool gets the worse it is for smaller miners....quite the dilemma since it needs to keep getting bigger to stay relevant.

It would be great if someone could take p2pool over and make it perform better and address the issues.  I would move Multipool's ~250TH back to BTC p2pool in a heartbeat if it could handle the load.

Multipool - Always mine the most profitable coin - Scrypt, X11 or SHA-256!
tf315
Jr. Member
*
Offline Offline

Activity: 59


View Profile
August 08, 2014, 03:44:41 AM
 #9932


I wish he opensourced the interface.


Try this one:
https://github.com/johndoe75/p2pool-node-status

Its similar to the one from coincadence at the node level. In fact he links to it at the bottom of the node page (click "Node Stats Front-end" to see it). I use it in a subdirectory of the regular extended one and it works just fine.
fire000
Member
**
Offline Offline

Activity: 98


View Profile
August 08, 2014, 10:55:08 AM
 #9933

I have sat back and read a few pages now of this....   I going to add my bit here lol....   I will start of saying I use to mine on p2pool with s1 ants...  It used to be good when the share diff was around 1mil use to hit a few each day...

But I left the p2pool set up when the diff shoot up to 2.5 mil as was not hitting share often enough vs a normal bitcoin pool and found the normal bitcoin pools were out doing the p2 earning wise....  

Now after sitting back for the last 2 days and watching the ants vs the diff of the p2 of 5 mil I would of hit a total of 1 shares for the 2 days on 3 ants so glad I moved the ants off P2 when I did a couple months back Smiley......    

Unless you are running 1th rigs forgot p2pool as you will earn no where the amount you would on a normal pool...

A few may want to try this experment above on their rigs and take note of ya best shares vs the p2 share diff and it will wake a few up to why ya not hitting shares....   As I said here unless ya running 1th + rigs these days p2 will hurt ya earnings wise from my testing over the last couple days.

Ps by 1th rigs I mean 1th rigs eg s2 ants knc eg   and not 4-5 s1 ants or 2-3 s3's to get that 1th figure
fire000
Member
**
Offline Offline

Activity: 98


View Profile
August 08, 2014, 11:07:25 AM
 #9934

also further to this current talk in here lol the /0 command sets to the bear min of the share diff on the miner as per the node diff so if the diff is 5mil for example it set the diff to 5mil   if it 7mil it sets to 7mil....      

But on saying this that /0 command can be used to set a diff higher than the min diff only for example if the diff was 5mil    you can set ya rig to a diff via the / number command to say 7.5 mil   eg /7500000   if this set under the current share diff on the nodes it defaults to the min diff on the node eg if you set it for 2.5 mil for example and the current diff was 5mil for a share it would default to the min diff of 5mil as that 2.5mil setting is below the current diff of 5mil
 
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
August 08, 2014, 12:03:03 PM
 #9935


How's that saying go, damn if you do; damned if you don't. It appears that the larger p2pool gets the worse it is for smaller miners....quite the dilemma since it needs to keep getting bigger to stay relevant.

It would be great if someone could take p2pool over and make it perform better and address the issues.  I would move Multipool's ~250TH back to BTC p2pool in a heartbeat if it could handle the load.

What do you mean by handle the load?  It's at 1.81PH/s right now, share difficulty is at 6.5 million.  If you've got hardware that works with p2pool, this is as good as it gets right now.

M

MMinerMonitor author, monitor/auto/schedule reboots/alerts/remote/MobileMiner for Ants and Spondoolies! Latest (5.2). MPoolMonitor author, monitor stats/workers for most pools, global BTC stats (current/nxt diff/USD val/hashrate/calc)! Latest (v4.2) 
Buyer beware of Bitmain hardware and services.
fire000
Member
**
Offline Offline

Activity: 98


View Profile
August 08, 2014, 12:16:05 PM
 #9936


How's that saying go, damn if you do; damned if you don't. It appears that the larger p2pool gets the worse it is for smaller miners....quite the dilemma since it needs to keep getting bigger to stay relevant.

It would be great if someone could take p2pool over and make it perform better and address the issues.  I would move Multipool's ~250TH back to BTC p2pool in a heartbeat if it could handle the load.

What do you mean by handle the load?  It's at 1.81PH/s right now, share difficulty is at 6.5 million.  If you've got hardware that works with p2pool, this is as good as it gets right now.

M


I think what flound getting at here is the diff issue as that hash rate goes up the diff will also keep rising and knocking more and more rigs off the face the earth of hitting shares unless ya running mining farms.....     Think of it in terms of the BTC diff the more hash added the faster the blocks are found the higher the diff rises....    The same issue applies here to P2POOL as that hash rate keeps rising that share diff will keep going up as the find times will be faster....     What someone needs to do somewhere down the line is change the amount of shares from what is is 3000 odd per block   to a larger number eg 12000 odd per block to match the rise in the hash rate on the network to bring it back down diff wise on the shares to gave the smaller miner a chance of hitting the shares as they once were able to do when the hash rate was low..... And in flound case been multipool they would have a mix of rigs in that 250 ths from small to large and if the s1 and s3 can not hit shares now and they make up alot of the network harsh rate on the btc what it going to be like in a pool double the hash it is today.

eg 3.6 ph   that would mean a diff off 13 mill +
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
August 08, 2014, 12:24:52 PM
 #9937


How's that saying go, damn if you do; damned if you don't. It appears that the larger p2pool gets the worse it is for smaller miners....quite the dilemma since it needs to keep getting bigger to stay relevant.

It would be great if someone could take p2pool over and make it perform better and address the issues.  I would move Multipool's ~250TH back to BTC p2pool in a heartbeat if it could handle the load.

What do you mean by handle the load?  It's at 1.81PH/s right now, share difficulty is at 6.5 million.  If you've got hardware that works with p2pool, this is as good as it gets right now.

M


I think what flound getting at here is the diff issue as that hash rate goes up the diff will also keep rising and knocking more and more rigs off the face the earth of hitting shares unless ya running mining farms.....     Think of it in terms of the BTC diff the more hash added the faster the blocks are found the higher the diff rises....    The same issue applies here to P2POOL as that hash rate keeps rising that share diff will keep going up as the find times will be faster....     What someone needs to do somewhere down the line is change the amount of shares from what is is 3000 odd per block   to a larger number eg 12000 odd per block to match the rise in the hash rate on the network to bring it back down diff wise on the shares to gave the smaller miner a chance of hitting the shares as they once were able to do when the hash rate was low.....

How do that has been hashed and re-hashed here.  If you decrease the share difficulty, you increase the time between job restarts.  Right now it's at 30 seconds, which I believe is what causes the problem with S2s and likely other ASIC hardware.  Those that have been with p2pool for a while will remember that it used to be 10 seconds, and it was changed to 30 seconds because 10 seconds was way too short for ASICs.

I don't believe this "more hashrate means higher share difficulty means harder for smaller miners" problem is solvable with the current p2pool design.

That's why I suggested a new design not that long ago.  If I was single, didn't have two kids, and wasn't working on moving across the country I'd try to code my design a proof of concept, and maybe become the new p2pool author. 

Alas, I barely have time to do what I need to do anymore, let alone what I'd like to do. Sad

M

MMinerMonitor author, monitor/auto/schedule reboots/alerts/remote/MobileMiner for Ants and Spondoolies! Latest (5.2). MPoolMonitor author, monitor stats/workers for most pools, global BTC stats (current/nxt diff/USD val/hashrate/calc)! Latest (v4.2) 
Buyer beware of Bitmain hardware and services.
jonnybravo0311
Legendary
*
Offline Offline

Activity: 1008


Mine at Jonny's Pool


View Profile WWW
August 08, 2014, 12:31:43 PM
 #9938

also further to this current talk in here lol the /0 command sets to the bear min of the share diff on the miner as per the node diff so if the diff is 5mil for example it set the diff to 5mil   if it 7mil it sets to 7mil....      

But on saying this that /0 command can be used to set a diff higher than the min diff only for example if the diff was 5mil    you can set ya rig to a diff via the / number command to say 7.5 mil   eg /7500000   if this set under the current share diff on the nodes it defaults to the min diff on the node eg if you set it for 2.5 mil for example and the current diff was 5mil for a share it would default to the min diff of 5mil as that 2.5mil setting is below the current diff of 5mil
 
Show me the proof in the code that it does so.  I have linked multiple places in the code that completely contradict this statement.  All I've gotten back so far is, "based on my personal experience" and other anecdotal evidence.  As is the saying, "Show me the money!" Someone show me where setting the address to /0 sets share difficulty to p2pool minimum share difficulty by quoting the actual CODE from p2pool (and not some modified version of the code like the vardiff patch or some scrypt coin) from forrestv github.

As I wrote a number of times a few pages back, manually setting the share difficulty only makes sense if you're mining on a node where there is a very large discrepancy between your hash rate and the total hash rate of the node.  For example, if you were to bring a 180GH/s miner to a node with 10TH/s, set that S1s difficulty manually.  The same holds true going the other way.  If you're bringing 10TH/s to a node with 1TH/s, set your share difficulty HIGHER than the default p2pool share value.  I even provided a way for you to calculate what you should set it to to get an average of 1 share an hour.

Regarding your comments on the minimum requirements to join p2pool, you've hit it pretty much dead on accurate.  If you want to ensure you've got a good chance of having a share on the chain for every block found, that means you're going to need enough hardware to find a share every 12 hours or so.  Currently the share difficulty is 6.5M.  So, to find 2 shares a day, you'd need just about 650GH/s.

Your statement about the hardware to bring to the party is incorrect, though.  It's not like a dragon or an S2 is somehow better at finding shares than an S1 is.  Hash rate is hash rate, no matter how you get there.

Jonny's Pool - Mine with us and help us grow!  Support a pool that supports Bitcoin, not a hardware manufacturer's pockets!  No SPV cheats.  No empty blocks.
bryonp
Member
**
Offline Offline

Activity: 77


View Profile
August 08, 2014, 12:39:41 PM
 #9939


How's that saying go, damn if you do; damned if you don't. It appears that the larger p2pool gets the worse it is for smaller miners....quite the dilemma since it needs to keep getting bigger to stay relevant.

It would be great if someone could take p2pool over and make it perform better and address the issues.  I would move Multipool's ~250TH back to BTC p2pool in a heartbeat if it could handle the load.

What do you mean by handle the load?  It's at 1.81PH/s right now, share difficulty is at 6.5 million.  If you've got hardware that works with p2pool, this is as good as it gets right now.

M


I think what flound getting at here is the diff issue as that hash rate goes up the diff will also keep rising and knocking more and more rigs off the face the earth of hitting shares unless ya running mining farms.....     Think of it in terms of the BTC diff the more hash added the faster the blocks are found the higher the diff rises....    The same issue applies here to P2POOL as that hash rate keeps rising that share diff will keep going up as the find times will be faster....     What someone needs to do somewhere down the line is change the amount of shares from what is is 3000 odd per block   to a larger number eg 12000 odd per block to match the rise in the hash rate on the network to bring it back down diff wise on the shares to gave the smaller miner a chance of hitting the shares as they once were able to do when the hash rate was low..... And in flound case been multipool they would have a mix of rigs in that 250 ths from small to large and if the s1 and s3 can not hit shares now and they make up alot of the network harsh rate on the btc what it going to be like in a pool double the hash it is today.

eg 3.6 ph   that would mean a diff off 13 mill +


This is running 16 s-1's
Version: unknown 7032706f6f6c2d6e2d6d6173746572

Pool rate: 1.67PH/s (13% DOA+orphan) Share difficulty: 6520000

Node uptime: 2.8 days Peers: 6 out, 0 in

Local rate: 3.99TH/s (6.6% DOA) Expected time to share: 2.0 hours

Shares: 44 total (4 orphaned, 0 dead) Efficiency: 104.5%

Payout if a block were found NOW: 0.0698682 BTC to xxxxxxxxxxxxxxxxxxxxxxxxxxx. Expected after mining for 24 hours: 0.0691 BTC per block.

Current block value: 25.084773600000002 BTC Expected time to block: 14.1 hours
_______________________________________________________________________________ __________________________

Any opinions?Huh
I think I am finding a good amount of shares, its just that the blocks are not paying enough.
If we had a few more blocks it would be better?Huh?
But we really are not.

1 month ago my payouts were 0.14xxxxxxx
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
August 08, 2014, 12:44:22 PM
 #9940

Any opinions?Huh
I think I am finding a good amount of shares, its just that the blocks are not paying enough.
If we had a few more blocks it would be better?Huh?
But we really are not.

1 month ago my payouts were 0.14xxxxxxx

As more hashpower is added to the pool, payouts amounts will decrease in size, but payout frequency will increase.  It should balance out.  Also keep in mind overall Bitcoin difficulty keeps increasing, although not quite as much per jump as it used to.

M

MMinerMonitor author, monitor/auto/schedule reboots/alerts/remote/MobileMiner for Ants and Spondoolies! Latest (5.2). MPoolMonitor author, monitor stats/workers for most pools, global BTC stats (current/nxt diff/USD val/hashrate/calc)! Latest (v4.2) 
Buyer beware of Bitmain hardware and services.
Pages: « 1 ... 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 [497] 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 ... 744 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!