Bitcoin Forum
December 11, 2016, 01:48:55 PM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 434 435 436 437 438 439 440 441 442 443 444 445 446 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 ... 744 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2035747 times)
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
July 15, 2014, 12:15:31 AM
 #9661

My M's Pool Monitor can do the monitoring/alerting for you.  (see sig)

If you're using your own private node, then you can use whatever name you want for each worker, and it'll all go to the same address.

If it's a public node, it's not quite so simple.

M

Hmm.. Yes, I am using public nodes.  I'll have to figure something out
I may have to join a pool that lists the hash rates publicly like http://61.219.119.37:9332/static/dashboard/miner.html?id=1Fgn9Q9GiV6QtuNegAog1wYpWXDAkt1z6o and use kimonifyto create an API for me out of it

Thanks

All nodes should list miner hashrates.

The simple solution is to use a different address for each miner.

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.
1481464135
Hero Member
*
Offline Offline

Posts: 1481464135

View Profile Personal Message (Offline)

Ignore
1481464135
Reply with quote  #2

1481464135
Report to moderator
1481464135
Hero Member
*
Offline Offline

Posts: 1481464135

View Profile Personal Message (Offline)

Ignore
1481464135
Reply with quote  #2

1481464135
Report to moderator
1481464135
Hero Member
*
Offline Offline

Posts: 1481464135

View Profile Personal Message (Offline)

Ignore
1481464135
Reply with quote  #2

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

Posts: 1481464135

View Profile Personal Message (Offline)

Ignore
1481464135
Reply with quote  #2

1481464135
Report to moderator
1481464135
Hero Member
*
Offline Offline

Posts: 1481464135

View Profile Personal Message (Offline)

Ignore
1481464135
Reply with quote  #2

1481464135
Report to moderator
bryonp
Member
**
Offline Offline

Activity: 77


View Profile
July 15, 2014, 01:40:11 AM
 #9662

My M's Pool Monitor can do the monitoring/alerting for you.  (see sig)

If you're using your own private node, then you can use whatever name you want for each worker, and it'll all go to the same address.

If it's a public node, it's not quite so simple.

M

Hmm.. Yes, I am using public nodes.  I'll have to figure something out
I may have to join a pool that lists the hash rates publicly like http://61.219.119.37:9332/static/dashboard/miner.html?id=1Fgn9Q9GiV6QtuNegAog1wYpWXDAkt1z6o and use kimonifyto create an API for me out of it

Thanks

We provide an estimated hashrate for each p2pool miner address here under the active miners tab: http://minefast.coincadence.com/p2pool-stats.php (estimate subject to variance/luck)

We also provide more detailed info per address/miner here: http://minefast.coincadence.com/miner.php

Hope it helps...


And I thank you as I always use your pages for that info on myself!!!
abdullahadam
Sr. Member
****
Offline Offline

Activity: 285


View Profile
July 15, 2014, 03:35:43 AM
 #9663


We provide an estimated hashrate for each p2pool miner address here under the active miners tab: http://minefast.coincadence.com/p2pool-stats.php (estimate subject to variance/luck)

We also provide more detailed info per address/miner here: http://minefast.coincadence.com/miner.php

Hope it helps...


awesome, thanks. will give it a try
norgan
Sr. Member
****
Offline Offline

Activity: 308

Decentralize your hashing - p2pool - Norgz Pool


View Profile WWW
July 15, 2014, 09:41:18 AM
 #9664

Over 1Ph/s!

Miner, tech geek, operator of NorgzPool - Sydney Australia P2Pool Node creator of p2pool fancy front end

Tips: 1NorganBbymShTN2MMpfGzRYJF8mcPeXjv Exchange BTC locally in Australia or Donate to p2pool miners
jonnybravo0311
Legendary
*
Offline Offline

Activity: 1008


Mine at Jonny's Pool


View Profile WWW
July 15, 2014, 12:13:40 PM
 #9665

Over 1Ph/s!
We've been flirting with the 1PH/s rate over the past week.  I've seen it go up to 1.1PH/s, then down to 450TH/s.  Right now, I show 743TH/s.  What really needs to happen is that the pool rate drops to like 50TH/s... the share difficulty drops to like 250k... I get about 1000 shares... then we shoot up to 2PH/s and solve 10 blocks in a row Smiley

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.
norgan
Sr. Member
****
Offline Offline

Activity: 308

Decentralize your hashing - p2pool - Norgz Pool


View Profile WWW
July 15, 2014, 12:16:58 PM
 #9666

Over 1Ph/s!
We've been flirting with the 1PH/s rate over the past week.  I've seen it go up to 1.1PH/s, then down to 450TH/s.  Right now, I show 743TH/s.  What really needs to happen is that the pool rate drops to like 50TH/s... the share difficulty drops to like 250k... I get about 1000 shares... then we shoot up to 2PH/s and solve 10 blocks in a row Smiley
Haha but the value of each share is adjusted anyway when that happens right?

Miner, tech geek, operator of NorgzPool - Sydney Australia P2Pool Node creator of p2pool fancy front end

Tips: 1NorganBbymShTN2MMpfGzRYJF8mcPeXjv Exchange BTC locally in Australia or Donate to p2pool miners
jonnybravo0311
Legendary
*
Offline Offline

Activity: 1008


Mine at Jonny's Pool


View Profile WWW
July 15, 2014, 12:49:35 PM
 #9667

Over 1Ph/s!
We've been flirting with the 1PH/s rate over the past week.  I've seen it go up to 1.1PH/s, then down to 450TH/s.  Right now, I show 743TH/s.  What really needs to happen is that the pool rate drops to like 50TH/s... the share difficulty drops to like 250k... I get about 1000 shares... then we shoot up to 2PH/s and solve 10 blocks in a row Smiley
Haha but the value of each share is adjusted anyway when that happens right?
Yeah... The shares are weighted.  It would be much better to find above average number of shares at the current difficulty.

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.
abdullahadam
Sr. Member
****
Offline Offline

Activity: 285


View Profile
July 15, 2014, 09:33:08 PM
 #9668

Someone explain this to me please

P2pool Luck Thirty Days    142.57%
according to http://minefast.coincadence.com/p2pool-stats.php

Does this mean on average you would have earned around 50% more on this pool than on say btcguild (which has 95.209% average for 30 days)?

abdullahadam
Sr. Member
****
Offline Offline

Activity: 285


View Profile
July 15, 2014, 09:39:36 PM
 #9669



Is this also what BTCGuild is reporting?
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
July 15, 2014, 09:40:43 PM
 #9670

Someone explain this to me please

P2pool Luck Thirty Days    142.57%
according to http://minefast.coincadence.com/p2pool-stats.php

Does this mean on average you would have earned around 50% more on this pool than on say btcguild (which has 95.209% average for 30 days)?

Every pool has variance.  Right now p2pool appears to be on the positive side of luck.

That said, I'm not sure this number is right.  According to http://p2pool.info/, it's 127.4%.

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.
abdullahadam
Sr. Member
****
Offline Offline

Activity: 285


View Profile
July 15, 2014, 09:42:43 PM
 #9671


Every pool has variance.  Right now p2pool appears to be on the positive side of luck.

That said, I'm not sure this number is right.  According to http://p2pool.info/, it's 127.4%.

M

You are right. I pm'd windpath about this.  It's off by 20% or so from p2pool.info

abdullahadam
Sr. Member
****
Offline Offline

Activity: 285


View Profile
July 15, 2014, 11:21:23 PM
 #9672

Can someone help me understand this please?

Calculator says 1TH = ~0.03 BTC per day
This Difficulty
per Day   0.02900884 BTC   $18.06


This 1TH miner here is generating around 0.07 BTC per day
http://minefast.coincadence.com/miner.php?id=15TiNiu2ZUjrYKskn9AsbznAgtab19KH84

This guy has more power (1.4TH) and is making less?
http://minefast.coincadence.com/miner.php?id=1Po4Fa4drFtaDZ2Rr51mVs26L9bADJqZBG

I'm confused
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
July 15, 2014, 11:39:21 PM
 #9673

Can someone help me understand this please?

Calculator says 1TH = ~0.03 BTC per day
This Difficulty
per Day   0.02900884 BTC   $18.06


This 1TH miner here is generating around 0.07 BTC per day
http://minefast.coincadence.com/miner.php?id=15TiNiu2ZUjrYKskn9AsbznAgtab19KH84

This guy has more power (1.4TH) and is making less?
http://minefast.coincadence.com/miner.php?id=1Po4Fa4drFtaDZ2Rr51mVs26L9bADJqZBG

I'm confused

There are all sorts of things that can affect expected payout.  One is luck.  Another is how long that user has been here.  If both users are past the 3 day PPLNS period, then the numbers are probably caused by luck, but could also be an error on the website.

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.
jedimstr
Hero Member
*****
Offline Offline

Activity: 784



View Profile
July 15, 2014, 11:42:52 PM
 #9674

Can someone help me understand this please?

Calculator says 1TH = ~0.03 BTC per day
This Difficulty
per Day   0.02900884 BTC   $18.06


This 1TH miner here is generating around 0.07 BTC per day
http://minefast.coincadence.com/miner.php?id=15TiNiu2ZUjrYKskn9AsbznAgtab19KH84

This guy has more power (1.4TH) and is making less?
http://minefast.coincadence.com/miner.php?id=1Po4Fa4drFtaDZ2Rr51mVs26L9bADJqZBG

I'm confused

There are all sorts of things that can affect expected payout.  One is luck.  Another is how long that user has been here.  If both users are past the 3 day PPLNS period, then the numbers are probably caused by luck, but could also be an error on the website.

M

Another possibility is that the "smaller" miner is actually spread across multiple nodes with the same address.  I do that with rigs pointed at my personal node in the US or ones in EU or Asia depending depending on lowest latency and distance.  Also failover nodes factor in too.  So 1TH may not actually be just 1TH, but instead just 1TH on Coincadence.

abdullahadam
Sr. Member
****
Offline Offline

Activity: 285


View Profile
July 15, 2014, 11:44:22 PM
 #9675

Sorry what is this 3 day PPLNS period?  Is that how p2pool works?
windpath
Legendary
*
Offline Offline

Activity: 938


View Profile WWW
July 15, 2014, 11:56:08 PM
 #9676


Every pool has variance.  Right now p2pool appears to be on the positive side of luck.

That said, I'm not sure this number is right.  According to http://p2pool.info/, it's 127.4%.

M

You are right. I pm'd windpath about this.  It's off by 20% or so from p2pool.info

Hey guys, I did post the formula I'm using earlier to have someone take a look at it... No one gave any feedback.

Here is another shot with the source that calculates 30 day luck:

I store blocks as they are found, hashrate is collected every minute, I added some comments to explain what numbers are being used...

Code:
function getThirtyDayLuck($crud, $diff)  {
// get 30 day average time between blocks
$blocks_query = $crud->rawSelect("SELECT COUNT(*) FROM found_blocks WHERE time > DATE_SUB(NOW(), INTERVAL 30 DAY) ORDER BY time DESC");
$blocks = $blocks_query->fetch(PDO::FETCH_ASSOC);
$block_count = $blocks['COUNT(*)'];
$avg_elapsed_seconds = 2592000 / $block_count; // 2592000 seconds = 30 days
// get 30 day hashrate average
$hash_query = $crud->rawSelect("SELECT AVG(global_rate) FROM pool_stats WHERE id > DATE_SUB(NOW(), INTERVAL 30 DAY)");
$hash_avg = $hash_query->fetch(PDO::FETCH_ASSOC);
$hashrate = $hash_avg['AVG(global_rate)'];
// 30 day expected time to block
        // Difficulty * 2**32 / hashrate  = expected number of seconds to find a block
$thirty_day_expected = round($diff * pow(2, 32) / $hashrate);
// Get luck as %
return percentage($thirty_day_expected, $avg_elapsed_seconds, '2')."%";
}

I'm relatively certain this is accurate, but am open to any suggestion as always....

mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
July 16, 2014, 12:33:14 AM
 #9677

Hey guys, I did post the formula I'm using earlier to have someone take a look at it... No one gave any feedback.

You're right.  I glossed over it, as it didn't look immediately decipherable to me.  Sad  Looking at it now..

Quote
Here is another shot with the source that calculates 30 day luck:

I store blocks as they are found, hashrate is collected every minute, I added some comments to explain what numbers are being used...

Code:
function getThirtyDayLuck($crud, $diff)  {
// get 30 day average time between blocks
$blocks_query = $crud->rawSelect("SELECT COUNT(*) FROM found_blocks WHERE time > DATE_SUB(NOW(), INTERVAL 30 DAY) ORDER BY time DESC");
$blocks = $blocks_query->fetch(PDO::FETCH_ASSOC);
$block_count = $blocks['COUNT(*)'];
$avg_elapsed_seconds = 2592000 / $block_count; // 2592000 seconds = 30 days
// get 30 day hashrate average
$hash_query = $crud->rawSelect("SELECT AVG(global_rate) FROM pool_stats WHERE id > DATE_SUB(NOW(), INTERVAL 30 DAY)");
$hash_avg = $hash_query->fetch(PDO::FETCH_ASSOC);
$hashrate = $hash_avg['AVG(global_rate)'];
// 30 day expected time to block
        // Difficulty * 2**32 / hashrate  = expected number of seconds to find a block
$thirty_day_expected = round($diff * pow(2, 32) / $hashrate);
// Get luck as %
return percentage($thirty_day_expected, $avg_elapsed_seconds, '2')."%";
}
I'm relatively certain this is accurate, but am open to any suggestion as always....

The immediate problem that jumps out at me is the difficulty changes at least twice a month, closer to three.  You need to store some value for each block as it happens, and then calculate it across your range when you display it.  This is what I do for Eligius:

For each block, store:
- average solve time
- actual solve time
- timestamp of the block

then some SQL:

for last 10 blocks:

SELECT sum(AvgSolveTime) / sum(ActualSolveTime)
FROM Luck
where Height >=
(select min(Height) from
(SELECT top 10 Height from Luck where Height <> 0 order by blocktimestamp desc));

for last 12 hours:

Select Sum(Luck.AvgSolveTime) / Sum(Luck.ActualSolveTime)
FROM Luck
Where BlockTimeStamp > (Now - 12 hours);

And so forth.  You can see the code in github for M's Pool Monitor.

M

EDIT: Then do a sanity check against a presumably known good source, like p2pool.info. Smiley

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
July 16, 2014, 12:38:30 AM
 #9678

Sorry what is this 3 day PPLNS period?  Is that how p2pool works?

Yes, that's how p2pool works.  The sharechain counts the previous 8640 shares for payment when a block is solved.  Every share is about 30 seconds, so that's where the 3 days comes from.

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.
windpath
Legendary
*
Offline Offline

Activity: 938


View Profile WWW
July 16, 2014, 12:43:33 AM
 #9679


You're right.  I glossed over it, as it didn't look immediately decipherable to me.  Sad  Looking at it now..

The immediate problem that jumps out at me is the difficulty changes at least twice a month, closer to three.  You need to store some value for each block as it happens, and then calculate it across your range when you display it.  This is what I do for Eligius:

For each block, store:
- average solve time
- actual solve time
- timestamp of the block

then some SQL:

for last 10 blocks:

SELECT sum(AvgSolveTime) / sum(ActualSolveTime)
FROM Luck
where Height >=
(select min(Height) from
(SELECT top 10 Height from Luck where Height <> 0 order by blocktimestamp desc));

for last 12 hours:

Select Sum(Luck.AvgSolveTime) / Sum(Luck.ActualSolveTime)
FROM Luck
Where BlockTimeStamp > (Now - 12 hours);

And so forth.  You can see the code in github for M's Pool Monitor.

M

EDIT: Then do a sanity check against a presumably known good source, like p2pool.info. Smiley

Yea, considered diff changes when writing the collector code (before adding the p2pool stats page...) Right now it bases it on current diff, would not be hard to add historical and store future back to beginning of luck calculations...

I assume the 30 day average diff would be most accurate?

Also, how best to calculate diff changes when a block spans 2 diffs? Is it the average of the 2 diffs, or the diff when block was found...

Quote
- average solve time

When is this calculated from?

mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
July 16, 2014, 01:23:04 AM
 #9680

Yea, considered diff changes when writing the collector code (before adding the p2pool stats page...) Right now it bases it on current diff, would not be hard to add historical and store future back to beginning of luck calculations...

I assume the 30 day average diff would be most accurate?

I don't think so.  You have to use the difficulty at each block.  Just like you have to use the pool hash rate at each block.

Quote
Also, how best to calculate diff changes when a block spans 2 diffs? Is it the average of the 2 diffs, or the diff when block was found...

It would be when the block is found.  I think if you were to average, it'd have to be a weighted average, if you will.  So if you had 24 hours at one difficulty, and 12 hours at the next, the 24 hours would "weigh" more in the average.  While I think it's not technically 100% correct (Organ, are you here? Smiley), it's a lot easier just to use the difficulty at the time it was solved.

Quote
Quote
- average solve time

When is this calculated from?

That's how long, on average, it should take for the block to be solved, at the pool hashrate at that time and current difficulty.  Something like:

network_difficulty * 2^32 / pool_hashrate

So if you know how long it should take (in seconds), and you know how long it really did take (in seconds), then it's simple division to see if your luck was good or bad:

AvgSolveTime / ActualSolveTime

If both are equal, you're at 100% luck.
If AvgSolveTime is higher, then you're above 100% luck.
If AvgSolveTime is lower, then you're below 100% luck.

To span across blocks, you divide the sum of one by the other:

SELECT sum(AvgSolveTime) / sum(ActualSolveTime)


Disclaimer: as far as I know my numbers are right, and they jive with the more limited info Eligius shows.

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 ... 434 435 436 437 438 439 440 441 442 443 444 445 446 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 ... 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!