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

[Krak]

I'm currently at 68 shares for the past 3 1/2 days with 0 dead and 0 orphan.

[racerguy]

I changed my bitcoin-qt datadir to E:\Users\xxx\AppData\Roaming\Bitcoin\,

then run:
run_p2pool --datadir E:\Users\xxx\AppData\Roaming\Bitcoin -a myaddress

it returned:
run_p2pool: error: Bitcoin configuration file not found. Manually enter your RPC password.
If you actually haven't created a configuration file, you should create one at C:\Users\xxx\AppData\Roaming\Bitcoin\bitcoin.conf with the text:

server=1
rpcpassword=........

I of course had created the file at E:\Users\xxx\AppData\Roaming\Bitcoin\bitcoin.conf,
so what's the matter?

will anyone help me?

maybe try telling p2pool your rpc user/pass when you launch it, usually it just reads that from your bitcoin.conf when you're running locally but maybe that's not working in your case

[jiyu_shi]

I changed my bitcoin-qt datadir to E:\Users\xxx\AppData\Roaming\Bitcoin\,

then run:
run_p2pool --datadir E:\Users\xxx\AppData\Roaming\Bitcoin -a myaddress

it returned:
run_p2pool: error: Bitcoin configuration file not found. Manually enter your RPC password.
If you actually haven't created a configuration file, you should create one at C:\Users\xxx\AppData\Roaming\Bitcoin\bitcoin.conf with the text:

server=1
rpcpassword=........

I of course had created the file at E:\Users\xxx\AppData\Roaming\Bitcoin\bitcoin.conf,
so what's the matter?

will anyone help me?

RTFM: https://en.bitcoin.it/wiki/P2Pool#Option_Reference
run_p2pool.py -a PayoutAddress PRCUser RPCPass

--datadir is where p2pool data is located, not bitcoind

it runs successfuly with PRCUser and RPCPass, thanks a lot!

[joemde]

this is what it says when you get one yourself:


2012-08-02 21:58:24.766062 GOT BLOCK FROM MINER! Passing to bitcoind! http://blockexplorer.com/block/00000000000006df0e6a59574c068e78835ba652e3aca88c0c35be5940d9ae87


that one was mine =p  you get a bonus when solving a block, i think it's the transaction amt?  I got 1.04 for that last one, and .80 for the block previous

[/quote]


Actually this:

"A subsidy of 0.5% is sent to the node that solved the block in order to discourage not sharing solutions that qualify as a block. (A miner with the aim to harm others could withhold the block, thereby preventing anybody from getting paid. He can NOT redirect the payout to himself.) The remaining 99.5% is distributed evenly to miners based on work done recently."

Which can be found here: https://en.bitcoin.it/wiki/P2Pool

I can verify the actual amount is .25 BTC or 0.5% of 50 BTC

[rav3n_pl]

Not only 50BTC from reward but our full payout = reward+fee and 0,5% form this.
So it can be more than 0,25BTC.

Code:

The block reward (currently 50BTC) [b]and the transaction fees[/b] are combined and apportioned according to these rules: 

[mdude77]

Is it coincidence that the highest pool hash rate in a long time coincides with the longest block in a month?  Going on 48 hours here...

M

[forrestv]

Just started using p2pool again today and I have a quick question. Does the --p2pool-node flag support DNS lookups or can it only do IP addresses? I have a friend nearby that I'd like to be always connected to, but he has a dynamic IP.

DNS lookups should definitely work. If they fail, P2Pool should print an error while starting up. A few of the bootstrap nodes, including mine, use domain names instead of IP addresses.

I changed my bitcoin-qt datadir to E:\Users\xxx\AppData\Roaming\Bitcoin\,

then run:
run_p2pool --datadir E:\Users\xxx\AppData\Roaming\Bitcoin -a myaddress

it returned:
run_p2pool: error: Bitcoin configuration file not found. Manually enter your RPC password.
If you actually haven't created a configuration file, you should create one at C:\Users\xxx\AppData\Roaming\Bitcoin\bitcoin.conf with the text:

server=1
rpcpassword=........

I of course had created the file at E:\Users\xxx\AppData\Roaming\Bitcoin\bitcoin.conf,
so what's the matter?

The problem was that P2Pool is looking on the C: drive, but your Bitcoin files are apparently on the E: drive? Anyway, you already solved it.

[ChanceCoats123]

Is it coincidence that the highest pool hash rate in a long time coincides with the longest block in a month?  Going on 48 hours here...

M

I feel like my shares have bad mojo.

[joemde]

Since the 2+ day block started my mean returned share rate only seems to be about 65% of expected in relation to local hash rate. Has anyone else seen something similar?

[mdude77]

Since the 2+ day block started my mean returned share rate only seems to be about 65% of expected in relation to local hash rate. Has anyone else seen something similar?

The pool hash rate is regularly up above 300g/h now.  That'll make your piece of the pie (and mine) smaller.  Theoretically it should mean more regular blocks which will offset it.

Theoretically.

M

[joemde]

Since the 2+ day block started my mean returned share rate only seems to be about 65% of expected in relation to local hash rate. Has anyone else seen something similar?

The pool hash rate is regularly up above 300g/h now.  That'll make your piece of the pie (and mine) smaller.  Theoretically it should mean more regular blocks which will offset it.

Theoretically.

M

Yea I get that however ...... your local client should still return a local share rate that is reflective of your local hash rate should it not?

[rav3n_pl]

We need change in LTC p2pool:
All links address/block form http://abe.liteco.in/ to http://explorer.litecoin.net/

[organofcorti]

The pool hash rate is regularly up above 300g/h now.  That'll make your piece of the pie (and mine) smaller.  Theoretically it should mean more regular blocks which will offset it.

Theoretically.

M

Yea I get that however ...... your local client should still return a local share rate that is reflective of your local hash rate should it not?

There's a lot of variance, explained here: https://bitcointalk.org/index.php?topic=18313.msg1057860#msg1057860

[joemde]

The pool hash rate is regularly up above 300g/h now.  That'll make your piece of the pie (and mine) smaller.  Theoretically it should mean more regular blocks which will offset it.

Theoretically.

M

Yea I get that however ...... your local client should still return a local share rate that is reflective of your local hash rate should it not?

There's a lot of variance, explained here: https://bitcointalk.org/index.php?topic=18313.msg1057860#msg1057860

Ok I understand that there is variance, but it seems that variance in my particular instance is rather high ~20% or more. Should I be alarmed or do you think it will work itself out over time?

[organofcorti]

The pool hash rate is regularly up above 300g/h now.  That'll make your piece of the pie (and mine) smaller.  Theoretically it should mean more regular blocks which will offset it.

Theoretically.

M

Yea I get that however ...... your local client should still return a local share rate that is reflective of your local hash rate should it not?

There's a lot of variance, explained here: https://bitcointalk.org/index.php?topic=18313.msg1057860#msg1057860

Ok I understand that there is variance, but it seems that variance in my particular instance is rather high ~20% or more. Should I be alarmed or do you think it will work itself out over time?

Did you read the post? Your variance is well within the 95% confidence interval.

[joemde]

Yea I did read it. I apologize for the question but I am clearly not anywhere in your league when it comes to statistics, probability and math. I just keep thinking I need to fix something but I can't find anything to fix. Thank you for taking the time to point me to your explanation.

Edit: Additionally your explanation seems to indicate that the lower your local hash rate the larger the variance is likely to be as reported by P2Pool. I have ~12 GH/s local rate and am only seeing ~10 GH/s reflected in shares although local rate reported by P2Pool is in line with the ~12 GH/s rate.

[organofcorti]

What's your hashrate? I misread the posts and thought it was 300Mhps, but that was the 300Ghps of the pool. If you post your hashrate I'll figure out the the probability of that sort of variance occurring in future.

[joemde]

Post above edited to include local vs reported hash rates.

[organofcorti]

Any idea what difficulty you've been submitting shares at (on average)?

[racerguy]

with my 5770 my expected payout varies between 0.02 and 0.08btc's, I'd say your variance is pretty normal unless you have 50ghash on your own.