[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool

[jedimstr]

Another potential stupid question....

Is there any detriment to mining on multiple nodes for the same address?  I know payout level carries over when you failover to another node for backup as you find shares, but that's not the question. I'm talking simultaneously across nodes with the same address.

Here's the use case:
My main set of rigs are in the US East Coast so I use my personal node on the same network to minimize latency.
I also have access to other rigs at other locations across the globe (rentals and other rigs).  Having them all point to my personal node could introduce higher rejects due to latency.
So I've connected them to some closer regional nodes.  They're all using the same address.  Is there any detriment in doing things that way (other than having to jump to the various nodes to see progress of the individual clusters of miners)?  Assuming the shares earned across the globe would raise the payout address' estimated amount as usual right?

[1715041749]

1715041749

[1715041749]

1715041749

[Collider]

No, there is no difference.

All the shares you mine to your address wil be saved in the sharechain.

[jonnybravo0311]

When you look at that block in the blockchain it has a payout address, is that the block finder?

Not sure I follow what you mean there...you can see the newly generated coins if you look at the block I found, along with all the other transactions in the block.  Payout address?

My miner's address (it was one of my S1s that found that block) was 1DLcDRVncY7Zasd91oBw12XrQfLPohtNZP.  As you can see, I earned 0.13024717BTC which is the block finder's reward plus the rewarded coins for shares on the share chain.

[norgan]

Share data

Timestamp: Thu Jun 26 2014 20:00:06 GMT+1000 (AUS Eastern Standard Time) (1403776806)

Difficulty: 1241379.569878876

Minimum difficulty: 1241379.569878876

Payout address: 19TbRwiWSVW4wd4wU1apDzyrhUtL8NcHRE

Donation amount: 0.00%

Last stale: null

Nonce: 55420988

Desired version: 13

That payout address shows on a block. Does that show the miner on p2pool that found the block?

[webiky]

I tried to find out something more about this problem, but I couldn´t.

My problem is, that I don´t get any IN connections.

http://84.42.144.19:9332/static/

Version: 13.4
Pool rate: 292TH/s (17% DOA+orphan) Share difficulty: 1280000
Peers: 8 out, 0 in
Local rate: 8.85GH/s (5.1% DOA) Expected time to share: 7.2 days
Shares: 0 total (0 orphaned, 0 dead) Efficiency: Huh

I use P2Pool release 13.4 for Windows (https://bitcointalk.org/index.php?topic=18313.0)
I have open all ports OUT, and these ports IN: 8333,9332,9333

Thank you in advance for any help.

[phillipsjk]

I tried to find out something more about this problem, but I couldn´t.

My problem is, that I don´t get any IN connections.


I have open all ports OUT, and these ports IN: 8333,9332,9333

Thank you in advance for any help.

It takes time.

I was able to check that you ports are open by accessing you node over the Internet.
Well, I only checked port 9332.

[jacob019]

Are there other indicators in P2Pool when you find a block other than the bonus?  How's the bonus differentiated from other payouts to our P2Pool associated address, now that we're seeing fairly regular donations to P2Pool miners?

Even if it says "Block Found!" on the rolling command line status, I'd have a hard time seeing it (not like I sit here watching it scroll by all day).  Is it in another log or do I have to slog through all my rigs and look at their UI's to see if they found a block (like the S1 Mining Status page)?

windpath - It would be great to have an indicator of blocks found (total and individual blocks highlighted) on the Miner Status pages you provide, including for miners outside your node on CoinCadence.

Alternatively can I add similar functionality to my node's UI.... where to source the data?

In the classic p2pool interface you can inspect the shares of recent blocks.  The shares show the payout address so you know who the blockfinder is.

[windpath]

I tried to find out something more about this problem, but I couldn´t.

My problem is, that I don´t get any IN connections.

http://84.42.144.19:9332/static/

Version: 13.4
Pool rate: 292TH/s (17% DOA+orphan) Share difficulty: 1280000
Peers: 8 out, 0 in
Local rate: 8.85GH/s (5.1% DOA) Expected time to share: 7.2 days
Shares: 0 total (0 orphaned, 0 dead) Efficiency: Huh

I use P2Pool release 13.4 for Windows (https://bitcointalk.org/index.php?topic=18313.0)
I have open all ports OUT, and these ports IN: 8333,9332,9333

Thank you in advance for any help.

It can take some time for incoming connections to show up, first time around it took 3 days for my first incoming connection...

[raskul]

nice run of luck today 

[jedimstr]

Boom... that's 4 Blocks for the last 2 days..  *rubs lucky block erupter keychain*

[jedimstr]

No, there is no difference.

All the shares you mine to your address wil be saved in the sharechain.

Well, I found one difference... or more like realized the difference after the fact.

When you throw the rented/remote/extra miners onto another closer node, you don't have the benefit of their hashpower for your local Merge Mining.  Only the remote node gets that benefit, if they're using it at all.

Oh well... don't know if the merged mining is enough of a benefit to outweigh the lower latencies on the remote miners.

[jonnybravo0311]

No, there is no difference.

All the shares you mine to your address wil be saved in the sharechain.

Well, I found one difference... or more like realized the difference after the fact.

When you throw the rented/remote/extra miners onto another closer node, you don't have the benefit of their hashpower for your local Merge Mining.  Only the remote node gets that benefit, if they're using it at all.

Oh well... don't know if the merged mining is enough of a benefit to outweigh the lower latencies on the remote miners.

That's correct.  It is the node's hash rate that gets applied to merge-mined coins.

Hey windpath... why is your node showing the last block (307942) orphaned?  I've got 6 confirmations on it - shows the same on blockchain.info.



What's your node know that the rest of the network doesn't?

[windpath]

windpath - It would be great to have an indicator of blocks found (total and individual blocks highlighted) on the Miner Status pages you provide, including for miners outside your node on CoinCadence.

Alternatively can I add similar functionality to my node's UI.... where to source the data?

Totally agree, I want to start processing and storing data directly from the share chain, but still  have some other items to finish up first (like global miner stats).

I grab the on-node share data from the p2pool log file and store it in MySQL..

[windpath]

No, there is no difference.

All the shares you mine to your address wil be saved in the sharechain.

Well, I found one difference... or more like realized the difference after the fact.

When you throw the rented/remote/extra miners onto another closer node, you don't have the benefit of their hashpower for your local Merge Mining.  Only the remote node gets that benefit, if they're using it at all.

Oh well... don't know if the merged mining is enough of a benefit to outweigh the lower latencies on the remote miners.

That's correct.  It is the node's hash rate that gets applied to merge-mined coins.

Hey windpath... why is your node showing the last block (307942) orphaned?  I've got 6 confirmations on it - shows the same on blockchain.info.



What's your node know that the rest of the network doesn't?

Haha, nothing... It's a valid block, looks like a bug...

I'm away from the office till Monday, will take a look and see if I can fix it from here, but will most likely not be corrected till Monday...

[sconklin321]

Wow 4 Blocks and we're showing on the pools distibution at blockchain.info again!!!  Nice string of luck, and just before the shares from when my miner got lucky a couple days ago expired too.  I'm very happy with P2Pool today!!!

[norgan]

Wow 4 Blocks and we're showing on the pools distibution at blockchain.info again!!!  Nice string of luck, and just before the shares from when my miner got lucky a couple days ago expired too.  I'm very happy with P2Pool today!!!

Boom! Can anyone say gravy train. Toot toot! Haha I had pointed some rented hashing power at me node during the down time and its all paying out right now.

[sconklin321]

Wow 4 Blocks and we're showing on the pools distibution at blockchain.info again!!!  Nice string of luck, and just before the shares from when my miner got lucky a couple days ago expired too.  I'm very happy with P2Pool today!!!

Boom! Can anyone say gravy train. Toot toot! Haha I had pointed some rented hashing power at me node during the down time and its all paying out right now.

Was a nice gravy train, my 0.02 approximate payout dropped to 0.012 sometime after the 4th block.

[norgan]

Wow 4 Blocks and we're showing on the pools distibution at blockchain.info again!!!  Nice string of luck, and just before the shares from when my miner got lucky a couple days ago expired too.  I'm very happy with P2Pool today!!!

Boom! Can anyone say gravy train. Toot toot! Haha I had pointed some rented hashing power at me node during the down time and its all paying out right now.

Was a nice gravy train, my 0.02 approximate payout dropped to 0.012 sometime after the 4th block.

mine is still up where it should be:
http://www.norgzpool.net.au

[windpath]

That's correct.  It is the node's hash rate that gets applied to merge-mined coins.

Hey windpath... why is your node showing the last block (307942) orphaned?  I've got 6 confirmations on it - shows the same on blockchain.info.



What's your node know that the rest of the network doesn't?

Manually corrected the block for display, will have to dig around next week and see what caused it, for some reason the block height was not recorded correctly...

That block puts our 7 day luck at 118%. not to shabby of a comeback before the impending diff jump

[jonnybravo0311]

That's correct.  It is the node's hash rate that gets applied to merge-mined coins.

Hey windpath... why is your node showing the last block (307942) orphaned?  I've got 6 confirmations on it - shows the same on blockchain.info.



What's your node know that the rest of the network doesn't?

Manually corrected the block for display, will have to dig around next week and see what caused it, for some reason the block height was not recorded correctly...

That block puts our 7 day luck at 118%. not to shabby of a comeback before the impending diff jump

Yeah, I'm quite happy we managed to knock out 4 blocks so quickly before what appears to be somewhere around a 25% diff increase.  From 6/25 until today I made 0.65310308BTC from p2pool with my SP10 and 2 S1s.  I'll take that