Author

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

legendary
Activity: 1500
Merit: 1002
Mine Mine Mine
hmmm . . .

Age 0d 0h 36m 20s
Found 2015-08-21 10:02:59   
Block # 0    
Block Hash 0000000000000000111beccb385466b36c2850ad0b0f5bd9c43ed3c0e1905289   
Reward 25.15033780   
Miners 251   
Share e1905289
Luck 0.01%   -

YaY ! a block Wink

BITCOIN BLOCK FOUND by 1ibw1GDfJBMkdZtPqaXuwhmzpzsjykDHS! Est hashrate 1041.22 GH/s

https://blockchain.info/block/0000000000000000111beccb385466b36c2850ad0b0f5bd9c43ed3c0e1905289


the estimated hashrate seems to be out ? comments on that windpath ? it does jumps up & down quite a bit recently.

sr. member
Activity: 266
Merit: 250
Has there been any word from forrestv as to weather this new "XT" client is actually compatible with p2pool with it's different block size params?
legendary
Activity: 1258
Merit: 1027

Interesting feature, P2Pool requires -rpcpassword to be explicitly set, so it will have no effect.


Don't think so. I don't use it. I'm pretty sure it reads it from bitcoin.conf if it's not set explicitly.

Code:
  BITCOIND_RPCUSERPASS  bitcoind RPC interface username, then password, space-
                        separated (only one being provided will cause the
                        username to default to being empty, and none will
                        cause P2Pool to read them from bitcoin.conf)


You know, you may be right, I've never tried it without the user and pass....

For me starting p2pool looks something like this:

Code:
python ./run_p2pool.py RPC_USER RPC_PASS

RPC user and pass always set, it may work without it on localhost, will give it a try when I get a chance.
legendary
Activity: 2576
Merit: 2267
1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k

Interesting feature, P2Pool requires -rpcpassword to be explicitly set, so it will have no effect.


Don't think so. I don't use it. I'm pretty sure it reads it from bitcoin.conf if it's not set explicitly.

Code:
  BITCOIND_RPCUSERPASS  bitcoind RPC interface username, then password, space-
                        separated (only one being provided will cause the
                        username to default to being empty, and none will
                        cause P2Pool to read them from bitcoin.conf)
legendary
Activity: 1258
Merit: 1027
Just ran across this and wanted to make sure any developer was aware. It's not likely to affect me but could save some tears...

rpc: Implement random-cookie based authentication
https://github.com/bitcoin/bitcoin/pull/6388

Interesting feature, P2Pool requires -rpcpassword to be explicitly set, so it will have no effect.

From the commit:
Quote
When no -rpcpassword is specified, use a special 'cookie' file for authentication.
legendary
Activity: 2576
Merit: 2267
1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k
Just ran across this and wanted to make sure any developer was aware. It's not likely to affect me but could save some tears...

rpc: Implement random-cookie based authentication
https://github.com/bitcoin/bitcoin/pull/6388
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
Those are two different and separate parameters, with different functions.  The "+" is the pseudo-share difficulty.  It's primary function is to provide you with feedback.  If you look at your miner logs, you'll only see accepts for shares greater than the value you use here.  The lower the number, the more shares you submit, the smoother the graphs become.

The "/" parameter is actual share difficulty, and its functionality is as I described in my previous post.
hero member
Activity: 518
Merit: 500
Thank you for the information everyone.  At the moment I am using a +4096 difficulty on the end of my BTC address.  Is this a good idea or should I perhaps try the /1 as suggested?  Would there be a huge difference?
legendary
Activity: 1512
Merit: 1012
Example with orphans (shares, you have ... reward, you doesn't ...)

legendary
Activity: 1512
Merit: 1012
Not that I know of...

that's why you MUST run your node on a local machine to view the prodution ... not use a remote P2Pool node that it count only the shares produces ...



legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
my payouts were a solid .03 to .086 per block,  now dropped to .006?  exactly same hashrate. Colour me confused....
Have you been finding less shares?

Your payout may change based on the amount of shares you find, and the variation of the pools hashrate.  If the pool hashrate goes down, the pools [share] difficulty goes down and you will earn a little more due to finding more shares.  If the pools hashrate increases, you will earn less.  The other side of this is as the pools hashrate increases, more blocks should be found; and as the pools hashrate decreases less blocks would be found. 

So your payout may change based on the pools hashrate, if your hashrate stays the same.
Typically when your expected payout drops way down, it's because you're either finding fewer than expected shares (variance) or the shares you are finding are orphaned or DOA.  Also, take a look at the node on which you're mining.  If the node's hash rate will lead it to finding a lot of shares, the node will adjust the share difficulty up to compensate.  You can counteract this by using the "/" parameter in your miner user name:
Code:
BTC_ADDRESS/1
This will tell the node that no matter what it determines the share difficulty to be, you want it to accept shares of minimum network difficulty from you.
newbie
Activity: 58
Merit: 0
my payouts were a solid .03 to .086 per block,  now dropped to .006?  exactly same hashrate. Colour me confused....
Have you been finding less shares?

Your payout may change based on the amount of shares you find, and the variation of the pools hashrate.  If the pool hashrate goes down, the pools [share] difficulty goes down and you will earn a little more due to finding more shares.  If the pools hashrate increases, you will earn less.  The other side of this is as the pools hashrate increases, more blocks should be found; and as the pools hashrate decreases less blocks would be found. 

So your payout may change based on the pools hashrate, if your hashrate stays the same.
hero member
Activity: 518
Merit: 500
my payouts were a solid .03 to .086 per block,  now dropped to .006?  exactly same hashrate. Colour me confused....

did you stop hashing or continuously ?

Not that I know of...
legendary
Activity: 1500
Merit: 1002
Mine Mine Mine
my payouts were a solid .03 to .086 per block,  now dropped to .006?  exactly same hashrate. Colour me confused....

did you stop hashing or continuously ?
hero member
Activity: 518
Merit: 500
my payouts were a solid .03 to .086 per block,  now dropped to .006?  exactly same hashrate. Colour me confused....
legendary
Activity: 2576
Merit: 2267
1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k
Under controlled conditions, no league of legend ping time problems. Must have been Comcast being crappy.
legendary
Activity: 1258
Merit: 1027
recent block got a no entry sign on it with 0.01% ?
http://minefast.coincadence.com/p2pool-stats.php

i got paid....

It's fixed, thanks for the heads up.
legendary
Activity: 2576
Merit: 2267
1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k
YaY! Another 2 blocks within 24 hours........ Grin

Dang. Curse League of Legends.
legendary
Activity: 1500
Merit: 1002
Mine Mine Mine
recent block got a no entry sign on it with 0.01% ?
http://minefast.coincadence.com/p2pool-stats.php

i got paid....
sr. member
Activity: 266
Merit: 250
YaY! Another 2 blocks within 24 hours........ Grin
Jump to: