Author

Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 702. (Read 2591919 times)

hero member
Activity: 1162
Merit: 500
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 Wink


sr. member
Activity: 336
Merit: 250
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  Huh
Makes sense now, cheers  Grin
hero member
Activity: 737
Merit: 500
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.
vip
Activity: 756
Merit: 503
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!
hero member
Activity: 591
Merit: 500
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.
vip
Activity: 756
Merit: 503
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.

hero member
Activity: 737
Merit: 500
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:[email protected]:7333 --merged http://user:[email protected]: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).
hero member
Activity: 591
Merit: 500
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:[email protected]:7333 --merged http://user:[email protected]: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.
vip
Activity: 756
Merit: 503
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:[email protected]:7333 --merged http://user:[email protected]:8338

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

Did I forget anything?
legendary
Activity: 1361
Merit: 1003
Don`t panic! Organize!
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.
hero member
Activity: 910
Merit: 1000
Items flashing here available at btctrinkets.com
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 ?
hero member
Activity: 504
Merit: 500
Scattering my bits around the net since 1980
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
hero member
Activity: 658
Merit: 500
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/
hero member
Activity: 504
Merit: 500
Scattering my bits around the net since 1980
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?
Yes, just add another --merged with another URL for the daemon.

You just have to make sure the block chains are compatable.

BTC and LTC for example, aren't compatable.

BTC, NMC, GG(now dead), are compatable, as well as a few others.

(for compatability, basically means, the same miner works for both)

-- Smoov
hero member
Activity: 682
Merit: 500
 Roll Eyes I still haven't set up merged mining with P2pool. Sad
hero member
Activity: 1162
Merit: 500
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?
hero member
Activity: 504
Merit: 500
Scattering my bits around the net since 1980
Try adding this to your namecoin.conf file: printtoconsole=1

Then you should be able to see P2Pool polling namecoind.

What messages am I looking for in the namecoind logs?
ok, well, first off, in your P2Pool logs, if you are seeing lines like
2012-05-11 05:36:14.828000 > Error while calling merged getauxblock:
2012-05-11 05:36:14.831000 > Traceback (most recent call last):
2012-05-11 05:36:14.833000 > Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 10061: No connection could be made because the target machine actively refuse
d it..

then P2Pool isn't communicating with one of your daemons. Won't say which one, but this comes up when P2Pool doesn't find a daemon at the URL you supplied, nothing is answering the port.

Also, if NMC is the only one you're merge mining with, and you're seeing "Got new merged mining work!" messages, then you should be in good shape.

As for the option above, printtoconsole, I noticed different daemons giving more or less info than bitcoind does, and it looks like with that set, it doesn't give enough, which was my bad for not checking that specific daemon. Looking with the '-debug' command line option enabled, I'm not seeing anything obvious from the namecoind end showing P2P's communication, so I wasn't helpful there, but the P2P messages I've mentioned in this reply should help out.

-- Smoov
hero member
Activity: 1162
Merit: 500
Try adding this to your namecoin.conf file: printtoconsole=1

Then you should be able to see P2Pool polling namecoind.

What messages am I looking for in the namecoind logs?
legendary
Activity: 2912
Merit: 1060
wow never knew about printtoconsole=1
no more stupid blank dos boxes
donator
Activity: 362
Merit: 250
I recently upgraded some of my GPU miners to cgminer 2.4 and the latest p2pool build.  After a day or so I noticed that my overall hash rate was significantly lower than it had been in the past.  I did some testing and found that lowering intensity even further from 7 to (5) 6 on some of my rigs resulted in a ~10%-15% improvement in the hash rate reported by p2pool (but lower in cgminer).  I just thought I'd mention it in case anyone else had a similar experience.  I suspect it is mostly due to upgrading cgminer since I was using a much older version.

The graphs in p2pool were very helpful in identifying trends between my rigs.  Smiley

edit - ran a bit longer to rule out some more variance and determined I may have been a bit optimistic with my initial findings, settled on -I 6
Jump to: