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

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: Smoovious on July 07, 2012, 07:10:34 AM

Quote from: mdude77 on July 07, 2012, 06:47:38 AM

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

hero member

Activity: 504

Merit: 500

Scattering my bits around the net since 1980

Quote from: mdude77 on July 07, 2012, 06:47:38 AM

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

legendary

Activity: 1540

Merit: 1001

Quote from: Smoovious on July 07, 2012, 06:37:41 AM

Quote from: mdude77 on July 07, 2012, 06:32:10 AM

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

organofcorti

donator

Activity: 2058

Merit: 1007

Poor impulse control.

Quote from: rav3n_pl on July 07, 2012, 06:27:48 AM

Quote from: organofcorti on July 07, 2012, 06:20:08 AM

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.

Smoovious

hero member

Activity: 504

Merit: 500

Scattering my bits around the net since 1980

Quote from: mdude77 on July 07, 2012, 06:32:10 AM

Quote from: rav3n_pl on July 07, 2012, 06:27:48 AM

Quote from: organofcorti on July 07, 2012, 06:20:08 AM

Quote from: mdude77 on July 07, 2012, 06:04:38 AM

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

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: rav3n_pl on July 07, 2012, 06:27:48 AM

Quote from: organofcorti on July 07, 2012, 06:20:08 AM

Quote from: mdude77 on July 07, 2012, 06:04:38 AM

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_pl

legendary

Activity: 1361

Merit: 1003

Don`t panic! Organize!

Quote from: organofcorti on July 07, 2012, 06:20:08 AM

Quote from: mdude77 on July 07, 2012, 06:04:38 AM

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....

organofcorti

donator

Activity: 2058

Merit: 1007

Poor impulse control.

Quote from: mdude77 on July 07, 2012, 06:04:38 AM

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

Smoovious

hero member

Activity: 504

Merit: 500

Scattering my bits around the net since 1980

Quote from: mdude77 on July 07, 2012, 06:04:38 AM

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

mdude77

legendary

Activity: 1540

Merit: 1001

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

mdude77

legendary

Activity: 1540

Merit: 1001

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

Proofer

member

Activity: 266

Merit: 36

Quote from: rav3n_pl on July 05, 2012, 11:39:15 AM

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.

rav3n_pl

legendary

Activity: 1361

Merit: 1003

Don`t panic! Organize!

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

member

Activity: 266

Merit: 36

Ubuntu 11.04, p2pool Version: 3.1-17-gb3a4925: If I try to run p2pool without my bitcoind username and password at the end of the command line, I get:

Code:

Traceback (most recent call last):
  File "/home/user/src/p2pool/run_p2pool.py", line 5, in
   main.run()
  File "/home/user/src/p2pool/p2pool/main.py", line 676, in run
   cp.readfp(StringIO.StringIO('[x]\r\n' + f.read()))
  File "/usr/lib/python2.7/ConfigParser.py", line 316, in readfp
   self._read(fp, filename)
  File "/usr/lib/python2.7/ConfigParser.py", line 538, in _read
   raise e
ConfigParser.ParsingError: File contains parsing errors:
   [line 5]: ' # Network-related settings:\n'
   [line 7]: ' # Run on the test network instead of the real bitcoin network.\n'
   [line 8]: ' #testnet=1\n'

# Connect via a socks4 proxy
#proxy=127.0.0.1:9050

##############################################################
## Quick Primer on addnode vs connect ##
## Let's say for instance you use addnode=4.2.2.4 ##
## addnode will connect you to and tell you about the ##

[the rest of my bitcoin.conf file is listed here]

rav3n_pl

legendary

Activity: 1361

Merit: 1003

Don`t panic! Organize!

Quote from: organofcorti on July 04, 2012, 08:17:51 PM

Couple of questions, rav3n_pl:

How dynamic is the difficulty? How often does it change?

If it changes often and this causes orphaned shares, what would the downside of changing it less frequently be?

Thanks for the work you do explaining p2Pool - it's really very helpful for those of us that want to understand it better but don't actually mine there.

Share diff is changing about every 10 sec. Every LP in P2pool means that some node found a valid p2pool chain share and diff is adjusted to meet another share in about 10sec.
DOA share appears when it is delivered to pool after LP message (it is from "previous" LP) and it can not be joined into chain.
Orphaned share is like in bitcoin chain - 2 shares almost at once and win that one what follows quicker by another valid share.

Diapolo

hero member

Activity: 772

Merit: 500

Quote from: rav3n_pl on July 04, 2012, 08:09:05 PM

https://en.bitcoin.it/wiki/P2Pool#Miners
Added simple tips that help few ppl reduce local DOA when using cgminer (best miner imo).

We have 2 kind of stales/doa there.

1. Miner getting work from p2pool
2. Miner finds a share diff>1 solution and send it to pool
3. Pool register share to calculate hash speed of miner
4. Pool checking that SD of share is higher that current SD of p2pool
5. If 4 is true Pool sending share to to other nodes.

Tuning miner options can reduce DOA that appears between 2 and 3. We can see it as red line in local graph.
It will NOT reduce doa/stales in between 4 and 5. Forrestv is struggling to improve logic of pool in that point. BUT like in "real" bitcoin share chain there is no way to reduce number of orphans to 0... ;]

You did not even mention the diakgcn kernel in CGMINER (use -v 2 -w 256 with it for optimal performance) :-P, at least it should be mentioned as an option and perhaps it can be valuable for some users out there

.

Dia

twmz

hero member

Activity: 737

Merit: 500

Quote from: organofcorti on July 04, 2012, 10:47:19 PM

Quote from: twmz on July 04, 2012, 09:47:58 PM

If you submit a pseudo share (i.e. a diff 1 share) and it doesn't meet the requirements of the current share difficulty, it is just not a share. It's not orphaned or DOA just because it doesn't meet the difficulty. This is common as most shares that the miner submits meet the diff 1 requirements but not the diff 800 requirements.

I follow - I was assuming the miner would be mining at the appropriate difficulty and only sending shares that met it. But if you're sending D1 shares which then may be rejected if they don't meet diff 800, then this isn't an issue. Thanks for the explanation, twmz.

Yes, p2pool "lies" to the miner and tells it to look for diff 1 shares. This was done for multiple reasons. It helps verify the miner is working more quickly because shares are found 800 times faster. It allows p2pool to estimate hashrate of local miners more accurately. Also, some miners choke on shares that are higher than diff 1 and so this is also done to be as compatible with existing miners as possible.

organofcorti

donator

Activity: 2058

Merit: 1007

Poor impulse control.

Quote from: twmz on July 04, 2012, 09:47:58 PM

If you submit a pseudo share (i.e. a diff 1 share) and it doesn't meet the requirements of the current share difficulty, it is just not a share. It's not orphaned or DOA just because it doesn't meet the difficulty. This is common as most shares that the miner submits meet the diff 1 requirements but not the diff 800 requirements.

I follow - I was assuming the miner would be mining at the appropriate difficulty and only sending shares that met it. But if you're sending D1 shares which then may be rejected if they don't meet diff 800, then this isn't an issue. Thanks for the explanation, twmz.

twmz

hero member

Activity: 737

Merit: 500

Quote from: organofcorti on July 04, 2012, 09:11:12 PM

Quote from: twmz on July 04, 2012, 08:31:01 PM

Quote from: organofcorti on July 04, 2012, 08:17:51 PM

How dynamic is the difficulty? How often does it change?
If it changes often and this causes orphaned shares, what would the downside of changing it less frequently be?

If, when you started looking for a share the difficulty was 800 and you find a share that is valid for difficulty <= 800, the only way that that wouldn't be valid is if someone else found a share in between when you started looking and when you found a share (which is the only time the difficulty changes).

If you start looking for a solution at difficulty, but by the time you submit it the difficulty is 900 and your solution is too large for the retarget, it will get rejected - is that DOA or orphaned? Not sure.

Either way, if difficulty changes too often then when it increase you'd expect to have an increase in submitted shares that do not solve the current difficulty. Or is the LP mechanism fast enough to prevent this?

If you submit a pseudo share (i.e. a diff 1 share) and it doesn't meet the requirements of the current share difficulty, it is just not a share. It's not orphaned or DOA just because it doesn't meet the difficulty. This is common as most shares that the miner submits meet the diff 1 requirements but not the diff 800 requirements.

Now, if a pseudo share comes in that builds off of share X, but share X+1 has arrived at the node in the mean time, then that is a DOA pseudo share, regardless of if it meets the difficulty requirements. If it happens to meet the difficulty requirements it will be counted in the "dead shares" statistics.

Since share difficulty only changes in response to new shares being added to the share chain, the only way difficulty could change while your pseudo share was "in flight" would be if a new share had been added to the sharechain. In that case, your pseudo share is DOA no matter what because it isn't building off the head of the sharechain. Again, difficulty change or not, it's DOA, so I don't think the difficulty change rate matters.

organofcorti

donator

Activity: 2058

Merit: 1007

Poor impulse control.

Quote from: twmz on July 04, 2012, 08:31:01 PM

Quote from: organofcorti on July 04, 2012, 08:17:51 PM

How dynamic is the difficulty? How often does it change?
If it changes often and this causes orphaned shares, what would the downside of changing it less frequently be?

If, when you started looking for a share the difficulty was 800 and you find a share that is valid for difficulty <= 800, the only way that that wouldn't be valid is if someone else found a share in between when you started looking and when you found a share (which is the only time the difficulty changes).

If you start looking for a solution at difficulty, but by the time you submit it the difficulty is 900 and your solution is too large for the retarget, it will get rejected - is that DOA or orphaned? Not sure.

Either way, if difficulty changes too often then when it increase you'd expect to have an increase in submitted shares that do not solve the current difficulty. Or is the LP mechanism fast enough to prevent this?

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