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

[rav3n_pl]

Try move lines

Code:

rpcuser=xxxx
rpcpass=yyy

to the top of bitccoin.conf file

Looks like you have some syntax error on it that kill p2pool parser.

[Proofer]

Try move lines

Code:

rpcuser=xxxx
rpcpass=yyy

to the top of bitccoin.conf file

Looks like you have some syntax error on it that kill p2pool parser.

Thanks; before I moved the lines, I noticed the error:  all the lines starting with the first one that p2pool complained about have a leading space.  That didn't cause a problem with bitcoind.  This bitcoin.conf was originated on an OS X system by the OS X bitcoin app months ago.  I've replaced it with one not having leading spaces and that solves the problem.

[mdude77]

I'm playing with p2pool again.

I'm seeing this a lot in the output for all 3 of my miners.  When I say a lot, I can sit and watch the visual output and it happens enough for me to see it regularly within a few minute period.

2012-07-05 16:49:49.262000 > Worker miner1 @ 192.168.0.110 submitted share more than once!

All the miners have different names.  The one with the most power seems to get the message the most, sometimes 2x back to back.  Two miners are on cgminer 2.4.4; one has 4 GPUs behind it, one has 1 GPU behind it.  The third miner is on phoenix 2.0.0, with 4 GPUs behind it.

I'm using the latest p2pool for windows, 3.1.

I posted this in cgminer before I got confirmation this is coming from my phoenix miner as well.

Any thoughts?

M

[mdude77]

How's this possible? 

2012-07-07 07:02:28.254000 New work for worker! Difficulty: 0.999985 Share difficulty: 639.252514 Total block value: 63.655207 BTC including 219 transactions

I've never seen blocks above 51 btc, including transactions.  If p2pool doing something to make up for the 20 hours we've been without a block?

M

[Smoovious]

How's this possible? 

2012-07-07 07:02:28.254000 New work for worker! Difficulty: 0.999985 Share difficulty: 639.252514 Total block value: 63.655207 BTC including 219 transactions

I've never seen blocks above 51 btc, including transactions.  If p2pool doing something to make up for the 20 hours we've been without a block?

M

No, all rewards at the current time are 50btc... anything over that, is including transaction fees...

My guess, is there are a LOT of small inputs in those 219 transactions, totalling over 13 btc worth of fees...

I suppose there could be someone out there intentionally adding on a much higher than required fee... nothing stopping people from doing so, but unlikely.

-- Smoov

[organofcorti]

How's this possible? 

2012-07-07 07:02:28.254000 New work for worker! Difficulty: 0.999985 Share difficulty: 639.252514 Total block value: 63.655207 BTC including 219 transactions

I've never seen blocks above 51 btc, including transactions.  If p2pool doing something to make up for the 20 hours we've been without a block?

M

Lots of blocks have been worth more than 51 btc, unless I'm reading this chart wrong:

http://blockchain.info/charts/transaction-fees

[rav3n_pl]

How's this possible? 

2012-07-07 07:02:28.254000 New work for worker! Difficulty: 0.999985 Share difficulty: 639.252514 Total block value: 63.655207 BTC including 219 transactions

I've never seen blocks above 51 btc, including transactions.  If p2pool doing something to make up for the 20 hours we've been without a block?

M

Lots of blocks have been worth more than 51 btc, unless I'm reading this chart wrong:

http://blockchain.info/charts/transaction-fees

This is per day fees, not per block.
If you run p2pool long enough w/o deleting log file you can grep that information
Most are very close to 50, some about 51, more are very rare.
When mining price will down and where will be more transactions all that fees will pump up p2pool because all pools are taking fee away + get % from base value....

[mdude77]

How's this possible? 

2012-07-07 07:02:28.254000 New work for worker! Difficulty: 0.999985 Share difficulty: 639.252514 Total block value: 63.655207 BTC including 219 transactions

I've never seen blocks above 51 btc, including transactions.  If p2pool doing something to make up for the 20 hours we've been without a block?

M

Lots of blocks have been worth more than 51 btc, unless I'm reading this chart wrong:

http://blockchain.info/charts/transaction-fees

This is per day fees, not per block.
If you run p2pool long enough w/o deleting log file you can grep that information
Most are very close to 50, some about 51, more are very rare.
When mining price will down and where will be more transactions all that fees will pump up p2pool because all pools are taking fee away + get % from base value....

So p2pool was doing it?  Every block I saw on the console was in that range.  We just got a block (finally!), and now it's back down to what I am used to:

2012-07-07 07:28:57.648000 New work for worker! Difficulty: 0.999985 Share difficulty: 655.441211 Total block value: 50.064550 BTC including 140 transactions

M

[Smoovious]

How's this possible?  

2012-07-07 07:02:28.254000 New work for worker! Difficulty: 0.999985 Share difficulty: 639.252514 Total block value: 63.655207 BTC including 219 transactions

I've never seen blocks above 51 btc, including transactions.  If p2pool doing something to make up for the 20 hours we've been without a block?

M

Lots of blocks have been worth more than 51 btc, unless I'm reading this chart wrong:

http://blockchain.info/charts/transaction-fees

This is per day fees, not per block.
If you run p2pool long enough w/o deleting log file you can grep that information
Most are very close to 50, some about 51, more are very rare.
When mining price will down and where will be more transactions all that fees will pump up p2pool because all pools are taking fee away + get % from base value....

So p2pool was doing it?  Every block I saw on the console was in that range.  We just got a block (finally!), and now it's back down to what I am used to:

2012-07-07 07:28:57.648000 New work for worker! Difficulty: 0.999985 Share difficulty: 655.441211 Total block value: 50.064550 BTC including 140 transactions

M

rav3n was referring to the blockchain.info link that he was replying to, showing per-day stats.

What you see on the console, reflects the pending transactions your node knows about, that may be included in the next block _you_ find. They might not all make it into the block, but it gives you an idea of what it could potentially be worth.

Over the past few minutes I've seen my # of transactions fluctuate between 50 and 250, and my block value staying within 50 and 51.5 range, so, perhaps you know about a high-fee transaction waiting to go in, or your cache is a little messed up.

edit: Sharky in the channel, just said the last block we found was good, and that it included 13.71570659 BTC in fees. I haven't confirmed it, but you should see your total block value drop back down to the typical range any time now.

-- Smoov

[organofcorti]

Lots of blocks have been worth more than 51 btc, unless I'm reading this chart wrong:

http://blockchain.info/charts/transaction-fees

This is per day fees, not per block.

I'm reading this chart wrong.

Derp.

[mdude77]

So p2pool was doing it?  Every block I saw on the console was in that range.  We just got a block (finally!), and now it's back down to what I am used to:

2012-07-07 07:28:57.648000 New work for worker! Difficulty: 0.999985 Share difficulty: 655.441211 Total block value: 50.064550 BTC including 140 transactions

M

rav3n was referring to the blockchain.info link that he was replying to, showing per-day stats.

What you see on the console, reflects the pending transactions your node knows about, that may be included in the next block _you_ find. They might not all make it into the block, but it gives you an idea of what it could potentially be worth.

Over the past few minutes I've seen my # of transactions fluctuate between 50 and 250, and my block value staying within 50 and 51.5 range, so, perhaps you know about a high-fee transaction waiting to go in, or your cache is a little messed up.


-- Smoov

According to my math, my ~5 g/h is worth about .8 to .9 btc per block (assuming 50btc/block).  That's what it leveled out to yesterday after 24 hours of running.  30 minutes ago when I saw EVERY block in the low 60btc, my share went up 1.2.  And when we found the last block, I got a payout of 1.22.  Now every block is back down where I've always seen it (before the 60 incident), between 50 and 51, and my share is slowly decreasing, currently down to 0.9684.

I doubt my p2pool node is special, but unless I'm misreading the replies, I have yet to see a reasonable explanation as to why the blocks were in the 60s, then we found a block, now it's back down between 50-51.  

M

[Smoovious]

According to my math, my ~5 g/h is worth about .8 to .9 btc per block (assuming 50btc/block).  That's what it leveled out to yesterday after 24 hours of running.  30 minutes ago when I saw EVERY block in the low 60btc, my share went up 1.2.  And when we found the last block, I got a payout of 1.22.  Now every block is back down where I've always seen it (before the 60 incident), between 50 and 51, and my share is slowly decreasing, currently down to 0.9684.

I doubt my p2pool node is special, but unless I'm misreading the replies, I have yet to see a reasonable explanation as to why the blocks were in the 60s, then we found a block, now it's back down between 50-51.

It went back down because those transactions are no longer pending.

A significant number of those transactions were from satoshi-dice (I looked through the block a bit ago) which many pools have begun to either ignore, or throttle how many they will include.

In any event, one of us found the block, and we got all those fees, which is what bumped up your payout.

Now those transactions are no longer pending, and are no longer included in your next block value estimate.

-- Smoov

[mdude77]

According to my math, my ~5 g/h is worth about .8 to .9 btc per block (assuming 50btc/block).  That's what it leveled out to yesterday after 24 hours of running.  30 minutes ago when I saw EVERY block in the low 60btc, my share went up 1.2.  And when we found the last block, I got a payout of 1.22.  Now every block is back down where I've always seen it (before the 60 incident), between 50 and 51, and my share is slowly decreasing, currently down to 0.9684.

I doubt my p2pool node is special, but unless I'm misreading the replies, I have yet to see a reasonable explanation as to why the blocks were in the 60s, then we found a block, now it's back down between 50-51.

It went back down because those transactions are no longer pending.

A significant number of those transactions were from satoshi-dice (I looked through the block a bit ago) which many pools have begun to either ignore, or throttle how many they will include.

In any event, one of us found the block, and we got all those fees, which is what bumped up your payout.

Now those transactions are no longer pending, and are no longer included in your next block value estimate.

-- Smoov

That makes sense.  Basically what you're saying is p2pool is more likely to process satoshi-dice transactions, so if the bits align right, p2pool users get a lot of transactions in their block?

M

[Smoovious]

That makes sense.  Basically what you're saying is p2pool is more likely to process satoshi-dice transactions, so if the bits align right, p2pool users get a lot of transactions in their block?

Well, I don't know if p2pool distributes the transactions themselves or not, so this is just a guess... but I believe it depends on your bitcoind, and what it is set up to accept or reject.

I believe that your p2pool instance, is reporting the transactions your bitcoind knows about, and will include in the solved block.

-- Smoov

[mdude77]

That makes sense.  Basically what you're saying is p2pool is more likely to process satoshi-dice transactions, so if the bits align right, p2pool users get a lot of transactions in their block?

Well, I don't know if p2pool distributes the transactions themselves or not, so this is just a guess... but I believe it depends on your bitcoind, and what it is set up to accept or reject.

I believe that your p2pool instance, is reporting the transactions your bitcoind knows about, and will include in the solved block.

-- Smoov

So... that implies that bitcoind is providing the work, and all the connections in p2pool (I have 32 atm) are for distributing what's found?  I think p2pool can feed bitcoind as well, which means overall the more connections on bitcoind and p2pool the better.

Yes?

M

[rav3n_pl]

No.
P2pool is getting work form bitcoind. Each node do the same, but not all the nodes have exact same work because not all txes are in all places of bitcoin network at same time.
So if your node will found a block it will be closed in way your bitcoind see it. Then your "block found" and your closing tx is spread across p2pool nodes.
So it IS possible, that you see block value 61 and I see same block @ 55 and s1 else only 50.

[mdude77]

No.
P2pool is getting work form bitcoind. Each node do the same, but not all the nodes have exact same work because not all txes are in all places of bitcoin network at same time.
So if your node will found a block it will be closed in way your bitcoind see it. Then your "block found" and your closing tx is spread across p2pool nodes.
So it IS possible, that you see block value 61 and I see same block @ 55 and s1 else only 50.

Good info, thanks.

What still puzzles me a little is why I consistently saw blocks in the low 60s.  It wasn't a one time deal, it stayed that one until we found a block, then it dropped.  And it was that way long enough for my payout to increase from .9 to 1.2, and as we know, the payout doesn't change rapidly.  I don't know how long it takes this info to propagate across the network.  That implies there's something wrong with my logic, or propagation is pretty slow.

BTW, I'm still regularly getting dupe submission messages.  I just saw this (biggest one I've seen so far):

2012-07-07 09:29:47.581000 > Worker q6600 @ 127.0.0.1 submitted share more than once!
2012-07-07 09:29:47.897000 > Worker miner1 @ 192.168.0.110 submitted share more than once!
2012-07-07 09:29:49.355000 > Worker miner1 @ 192.168.0.110 submitted share more than once!
2012-07-07 09:29:50.915000 > Worker miner1 @ 192.168.0.110 submitted share more than once!
2012-07-07 09:29:51.948000 > Worker miner1 @ 192.168.0.110 submitted share more than once!

M

[Smoovious]

What still puzzles me a little is why I consistently saw blocks in the low 60s.  It wasn't a one time deal, it stayed that one until we found a block, then it dropped.  And it was that way long enough for my payout to increase from .9 to 1.2, and as we know, the payout doesn't change rapidly.  I don't know how long it takes this info to propagate across the network.  That implies there's something wrong with my logic, or propagation is pretty slow.

Because other pools that found blocks, either weren't seeing the Tx's your bitcoind was seeing, or were rejecting them.

They could have been rejecting them based on their priority rating, fee amount, or simply the fact that many of them were Satoshi-Dice Tx's. Some people mining, reject all Tx's too.

If a Tx hasn't been included in a block, it stays available until someone includes it.

This is likely why you kept seeing the amount you were for as long as you were.

-- Smoov

[twmz]

That block had a high reward because of these three transactions:

http://blockchain.info/tx-index/11490303/e287eb27bb543a82ce9bcad780583de9f7da4e2e1abef55395a97c931f6aa4cb
http://blockchain.info/tx-index/11490313/34b90a85b7e625f0a60ff1e3b3bdfd735d79393930e8515f9d8188dd72f638b9
http://blockchain.info/tx-index/11490553/e35818bec399da75796e7ff8235cf1fb2bfb2897f161dc4d1d17b2a8ef79bed2

The first has a 7.5 BTC fee attached, the second has a 3.1 BTC fee attached, and the third has a 2.9 BTC fee attached.

So 13.5 BTC fees between them and resulted in the block being worth 50 + 13.5 + some other small fees.

You p2pool console showed a 60+ BTC block reward for as long as these three transactions were sitting pending.  No other pool claimed them for some reason and when we eventually found a block, they were included in our block and we got the reward. As soon as we included them in a block, the estimated block reward in your p2pool console dropped back down to the normal 50ish BTC.

[rav3n_pl]

I posted a script in this thread that used git to autoupdate p2pool. Including it in the cron jobs of p2pcoin (and any Linux-based install) might be worth it.

For it to work, you must have :
- a p2pool checkout with git in a directory from which p2pool will be run,
- git...
- screen to run p2pool

If anyone's interested and can't find it I'll dig it up.

Yeah, if you can dig that up, let me know.  I'll include it in p2pcoin.

Here it is :
http://pastie.org/4166525

Everything should be self explanatory for anyone familiar with bash scripts and p2pool. It's configured for my needs but should easily be adapted. If you have any question when customizing it for p2pcoin I'd be happy to help.

Based on this script I made combination of 2 scripts that can be used at startup and in cron (every day/week) to keep p2pool updated.

First one os one-liner that atrually starts p2pool. This way you can easily edit pool options. Lets name it p2p.sh, put it in ~/ and make executable.

Code:

#!/bin/bash
screen -U -d -m python ~/p2pool/run_p2pool.py --irc-announce --merged http://nmcu:nmcp@127.0.0.1:8336/

Just add/remove merged mining in way you have it. All startup options on wiki: https://en.bitcoin.it/wiki/P2Pool#Option_Reference

Second script is checking for p2pool update and restart p2pool if need. If p2pool is not started (ie at boot) it starts it:

Code:

#!/bin/bash
EXISTINGPID=`pgrep -f run_p2pool`

cd ~/p2pool
echo "Checking for P2pool updates..."
if git pull | grep -q 'Already up-to-date'; then
    echo "P2pool is up to date."
    if [[ -z "$EXISTINGPID" ]]; then
        echo "Starting P2pool..."
        ~/p2p.sh
    fi
else
    echo "P2pool updated, starting..."
    ~/p2p.sh
    if [[ ! -z "$EXISTINGPID" ]]; then
        echo "Waiting for new p2pool to be ready..."
        sleep 90
        echo "Killing old p2pool."
        kill $EXISTINGPID
    fi
fi

I assume that p2pool is git cloned into ~/p2pool, if not edit proper line.

To avoid loss of hash power on pool restart (sometimes it might be about minute gap) remember to have backup pool in miner. It might be one of public: http://nodes.p2pmine.com/
Beauty of p2pool is, that you can mine at any node using own payout address and you get paid form sum of your shares