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

[Aseras]

Also, if NMC is the only one you're merge mining with, ...

Is it possible to add more than just NMC to do merged mining? I thought the only possible option is BTC + NMC. No?

you can do whatever you want, just run thier daemon and change the rpc ports for each whatever you want to mine so they don't conflict and add it to the command line --merged http://user:pass@127.0.0.1:port/

[Smoovious]

Also, if NMC is the only one you're merge mining with, ...

Is it possible to add more than just NMC to do merged mining? I thought the only possible option is BTC + NMC. No?

you can do whatever you want, just run thier daemon and change the rpc ports for each whatever you want to mine so they don't conflict and add it to the command line --merged http://user:pass@127.0.0.1:port/

Your command line could get too long if you're going to merge-mine a lot of daemons, so you could also just include "@c:\usr\bin\p2pool\p2poolBTC.conf" as your command-line option, and put all of your flags in that file instead.

The filename could be any name, doesn't have to be that.

-- Smoov

[Isokivi]

Im experiencing an awful amount of orphans: Shares 185 <17 orphan, 3 dead>. I only have 10 open connections to th network as my Ip changed, I do have the ports forwarded but usually takes me 2 or so days to see more connections. Can this orphan amount be considered as normal or within variance ?

[rav3n_pl]

Try sync your p2pool machine to atomic time, also check the connection lags.
I`m producing only few shares per day and had few orphans too.

[01BTC10]

I started P2Pool with the following command about 3 days ago but the node didn't collect any fee mining at 1.8GH/s.

Code:

~/p2pool/run_p2pool.py  user pass --fee 0.5 --merged http://user:pass@127.0.0.1:7333 --merged http://user:pass@127.0.0.1:8338

I see the thank you message for donation toward the P2Pool project and /fee show 0.5

Did I forget anything?

[Krak]

I started P2Pool with the following command about 3 days ago but the node didn't collect any fee mining at 1.8GH/s.

Code:

~/p2pool/run_p2pool.py  user pass --fee 0.5 --merged http://user:pass@127.0.0.1:7333 --merged http://user:pass@127.0.0.1:8338

I see the thank you message for donation toward the P2Pool project and /fee show 0.5

Did I forget anything?

You do know that the --fee flag is the amount that you get from people that are mining on your node, right? The donation flag is --give-author.

[twmz]

I started P2Pool with the following command about 3 days ago but the node didn't collect any fee mining at 1.8GH/s.

Code:

~/p2pool/run_p2pool.py  user pass --fee 0.5 --merged http://user:pass@127.0.0.1:7333 --merged http://user:pass@127.0.0.1:8338

I see the thank you message for donation toward the P2Pool project and /fee show 0.5

Did I forget anything?

Stupid question, but is someone mining at your node and passing in their own bitcoin address as the miner username?  That's the only time you're going to see a fee taken out.  If no one is mining, there is no fee.  If they are mining, but not overriding the payment address with their username, then they are essentially giving 100% of their mining to you (to the default payment address).

[01BTC10]

Yes, I  only have 1 miner using his BTC address as username that is receiving payments ~. The node BTC address balance stay at 0.

If my command to start P2Pool is right then I should see some fees coming soon.

[Krak]

Yes, I  only have 1 miner using his BTC address as username that is receiving payments. The node BTC address balance stay at 0.

Using a 0.5% fee just means that you'll keep 5 out of every 1,000 shares that's mined through your node. You might not see a payment for a while.

[01BTC10]

Yes, I  only have 1 miner using his BTC address as username that is receiving payments. The node BTC address balance stay at 0.

Using a 0.5% fee just means that you'll keep 5 out of every 1,000 shares that's mined through your node. You might not see a payment for a while.

Great thank's for the info!

[twmz]

Yes, I  only have 1 miner using his BTC address as username that is receiving payments. The node BTC address balance stay at 0.

Using a 0.5% fee just means that you'll keep 5 out of every 1,000 shares that's mined through your node. You might not see a payment for a while.

Great thank's for the info!

Also, it's random (with a probability equal to the percentage you set) that any given share will be redirected to your node's address.  So you'll not necessarily get exactly 5 out of the first 1000.  It'll end up averaging that in the long term, though.

[Shadow383]

Yes, I  only have 1 miner using his BTC address as username that is receiving payments. The node BTC address balance stay at 0.

Using a 0.5% fee just means that you'll keep 5 out of every 1,000 shares that's mined through your node. You might not see a payment for a while.

Great thank's for the info!

Also, it's random (with a probability equal to the percentage you set) that any given share will be redirected to your node's address.  So you'll not necessarily get exactly 5 out of the first 1000.  It'll end up averaging that in the long term, though.

Was wondering why I hadn't seen anything go to the wallet of my 0.1% fee node, then suddenly got payment the other day 
Makes sense now, cheers 

[Frizz23]

Question for the "Blocks found in last day:" section from http://localhost:9332:

* I got credit for some blocks that did not show up in this section.
* I can see those blocks in my local Bitcoin wallet as well as on http://p2pool.info/
* p2pool shows me: Shares: 51 total (0 orphaned, 0 dead)

- I would have expected that this "orphaned" counter would be greater than 0 in cases like this. No?
- How come the local block statistics (http://localhost:9332) are different from the ones on http://p2pool.info/ ?


P.S.
After some weeks of mining for a different pool I'm back to p2pool now - this might explain the bad luck we have recently. I'm sort of hoodoo to p2pool

[Gomeler]

I just redirected a pair of rigs @ p2pool as a trial run to monitor bandwidth consumption and BTC throughput. Does the below output look ok?

2012-05-12 20:39:29.682525 P2Pool: 17410 shares in chain (9724 verified/17414 total) Peers: 10 (0 incoming)
2012-05-12 20:39:29.682617  Local: 4445MH/s in last 10.0 minutes Local dead on arrival: ~2.6% (1-5%) Expected time to share: 11.8 minutes
2012-05-12 20:39:29.682643  Shares: 13 (2 orphan, 0 dead) Stale rate: ~15.4% (4-43%) Efficiency: ~95.2% (64-108%) Current payout: 0.0798 BTC
2012-05-12 20:39:29.682673  Pool: 353GH/s Stale rate: 11.1% Expected time to block: 5.9 hours


Just synced the server running p2pool with ntp and have ntpd running, not sure if that was the cause of the orphans. I think my intensity is set too high(9) on one of my boxes which might explain the stale rate?

[ChanceCoats123]

That seems to be right. The stales will be higher with a higher intensity, but the hashrates will be too. Typically I use a little lower to cut the orphans.

[Krak]

That seems to be right. The stales will be higher with a higher intensity, but the hashrates will be too. Typically I use a little lower to cut the orphans.

I'm pretty sure that a lower intensity doesn't do anything to help lower orphans; it's simply to reduce your DoA rate so that you're not wasting as many hashes.

[Tittiez]

I'm loving this day long round! (Yes, I went there)

[ChanceCoats123]

That seems to be right. The stales will be higher with a higher intensity, but the hashrates will be too. Typically I use a little lower to cut the orphans.

I'm pretty sure that a lower intensity doesn't do anything to help lower orphans; it's simply to reduce your DoA rate so that you're not wasting as many hashes.

I coulda sworn it was the other way around. Oh well. Either way, it helps keep rejects down, and my payrate up.

[mdude77]

Is there any way to identify which rig, or even better which gpu is responsible for my orphans/stales ?

which miner?  cgminer and guiminer both list the accepted and rejected blocks per gpu.

phoenix 2.0 doesn't seem to be as friendly.

[Smoovious]

Is there any way to identify which rig, or even better which gpu is responsible for my orphans/stales ?

which miner?  cgminer and guiminer both list the accepted and rejected blocks per gpu.

phoenix 2.0 doesn't seem to be as friendly.

You could set each miner up with a different deposit address as the username. Then they would show up seperately on the graphs.

-- Smoov