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

[spiccioli]

You might want to try these settings in bitcoin.conf to improve your bitcoind performance if it is indeed the bottleneck. I've found processing hundreds of transactions can also slow things down so some of these settings limit the number of transactions to a couple hundred.

Code:

#Max number of nodes to connect to. Another possible bottleneck.
maxconnections=20

#Maximum size, in bytes, of blocks you create:
blockmaxsize=100000

#How many bytes of the block should be dedicated to high-priority transactions,                                                                                                 
#included regardless of the fees they pay                                                                                                                                 
blockprioritysize=2000

#Minimum block size you want to create; block will be filled with free transactions                                                                                       
#until there are no more or the block reaches this size:                                                                                                                  
blockminsize=0

#Fee-per-kilobyte amount (in BTC) considered the same as "free"                                                                                                                    
#Be careful setting this: if you set it to zero then                                                                                                                      
#a transaction spammer can cheaply fill blocks using                                                                                                                      
#1-satoshi-fee transactions. It should be set above the real                                                                                                              
#cost to you of processing a transaction.                                                                                                                                 
mintxfee=0.0005

cabin

I think these options should be mandatory when running p2pool on a slow/old/single core pc and/or using an ADSL or any other kind of async/slow home transmission channel.

spiccioli.

[twmz]

Since our current lucky streak has been completely jinxed already, I'll just pile on and point out that for the first time in nearly a year, the all-time luck is back to even!

[rav3n_pl]

Anyway, on 8. nov all-time luck went to 99.9%! Really good improvement form less than 90% few months back. Sadly that last over-lengh blocks killing it again... :/

Since our current lucky streak has been completely jinxed already, I'll just pile on and point out that for the first time in nearly a year, the all-time luck is back to even!

Yep ;]

[mdude77]

And we have a nice luck streak again  

got 5,07 bitcoin in 12 hours of mining   (~4,5ghs, estimated by p2pool 0,62-0,80/24hr)

I assume I'm misreading this because of currency differences.   In 12 hours we had 4 blocks.  I'm at ~2 gh, which gets me about 0.3 BTC/block.  That's 1.2BTC for 4 blocks.  Scale that up to 4.5gh and I get 2.7BTC.  How did you get 5.07btc?

M

[cabin]

You might want to try these settings in bitcoin.conf to improve your bitcoind performance if it is indeed the bottleneck. I've found processing hundreds of transactions can also slow things down so some of these settings limit the number of transactions to a couple hundred.

Code:

#Max number of nodes to connect to. Another possible bottleneck.
maxconnections=20

#Maximum size, in bytes, of blocks you create:
blockmaxsize=100000

#How many bytes of the block should be dedicated to high-priority transactions,                                                                                                 
#included regardless of the fees they pay                                                                                                                                 
blockprioritysize=2000

#Minimum block size you want to create; block will be filled with free transactions                                                                                       
#until there are no more or the block reaches this size:                                                                                                                  
blockminsize=0

#Fee-per-kilobyte amount (in BTC) considered the same as "free"                                                                                                                    
#Be careful setting this: if you set it to zero then                                                                                                                      
#a transaction spammer can cheaply fill blocks using                                                                                                                      
#1-satoshi-fee transactions. It should be set above the real                                                                                                              
#cost to you of processing a transaction.                                                                                                                                 
mintxfee=0.0005

cabin

I think these options should be mandatory when running p2pool on a slow/old/single core pc and/or using an ADSL or any other kind of async/slow home transmission channel.

spiccioli.

I don't think there is a way to enforce these, but we can certainly recommend them to everyone.. especially the transaction limit ones. I think I remember reading even the large pools were not letting their blocks grow massive in the hopes they propagate faster and have less orphans. I'm not sure if that was proven to be correct or not.. but it sounds plausible and I know in my personal case it reduced my getWork times.

[aadje93]

And we have a nice luck streak again  

got 5,07 bitcoin in 12 hours of mining   (~4,5ghs, estimated by p2pool 0,62-0,80/24hr)

I assume I'm misreading this because of currency differences.   In 12 hours we had 4 blocks.  I'm at ~2 gh, which gets me about 0.3 BTC/block.  That's 1.2BTC for 4 blocks.  Scale that up to 4.5gh and I get 2.7BTC.  How did you get 5.07btc?

M

Hi, made screenshot:



even another transaction ~5hours later wich made another 0,60 bitcoin for the block.

And you can see each block gets me less, dont know why that is but I think its the PPLNS system...

[K1773R]

And we have a nice luck streak again  

got 5,07 bitcoin in 12 hours of mining   (~4,5ghs, estimated by p2pool 0,62-0,80/24hr)

I assume I'm misreading this because of currency differences.   In 12 hours we had 4 blocks.  I'm at ~2 gh, which gets me about 0.3 BTC/block.  That's 1.2BTC for 4 blocks.  Scale that up to 4.5gh and I get 2.7BTC.  How did you get 5.07btc?

M

Hi, made screenshot:



even another transaction ~5hours later wich made another 0,60 bitcoin for the block.

And you can see each block gets me less, dont know why that is but I think its the PPLNS system...

yes its the PPLNS systems, sometimes u get more, sometimes less.

[forrestv]

P2Pool release 9.0 tag: 9.0 hash: 2cb4d8381e179f71ea2075cdce948ea83cf0dc55

HARDFORK: Upgrade is required! Hardfork will happen after 95% of the pool's hash rate has upgraded. Everybody having not upgraded will be split off into a tiny P2Pool.

Windows binary: http://u.forre.st/u/urxoztyg/p2pool_win32_9.0.zip
Source zipball: https://github.com/forrestv/p2pool/zipball/9.0
Source tarball: https://github.com/forrestv/p2pool/tarball/9.0

Changes:
* Transaction preforwarding Transactions that you're mining are sent to peers before you get a share, so any block solution you find can be broadcast virtually instantaneously. This could theoretically get our invalid block rate below any other pool's thanks to our large network of nodes. This was implemented in v8, but was prevented from taking effect due to a bug being discovered.
* Stratum support in the P2Pool protocol. Stratum mining will be enabled in a future patch to v9.

[aadje93]

P2Pool release 9.0 tag: 9.0 hash: 2cb4d8381e179f71ea2075cdce948ea83cf0dc55

HARDFORK: Upgrade is required! Hardfork will happen after 95% of the pool's hash rate has upgraded. Everybody having not upgraded will be split off into a tiny P2Pool.

Windows binary: http://u.forre.st/u/urxoztyg/p2pool_win32_9.0.zip
Source zipball: https://github.com/forrestv/p2pool/zipball/9.0
Source tarball: https://github.com/forrestv/p2pool/tarball/9.0

Changes:
* Transaction preforwarding Transactions that you're mining are sent to peers before you get a share, so any block solution you find can be broadcast virtually instantaneously. This could theoretically get our invalid block rate below any other pool's thanks to our large network of nodes. This was implemented in v8, but was prevented from taking effect due to a bug being discovered.
* Stratum support in the P2Pool protocol. Stratum mining will be enabled in a future patch to v9.

(may i ask why we need stratum support when you are acutally using some kind of stratum when mining on P2Pool)

Thanks for the update still Upgraded my node (86.84.172.146:9332)

[forrestv]

(may i ask why we need stratum support when you are acutally using some kind of stratum when mining on P2Pool)

More efficient communication between your P2Pool node and your miner. One Stratum work unit could supply an ASIC miner with a virtually infinite amount of work, as opposed to a getwork work unit, which gives 4 GH of work.

[K1773R]

(may i ask why we need stratum support when you are acutally using some kind of stratum when mining on P2Pool)

More efficient communication between your P2Pool node and your miner. One Stratum work unit could supply an ASIC miner with a virtually infinite amount of work, as opposed to a getwork work unit, which gives 4 GH of work.

less load for the overall system

[mdude77]

And we have a nice luck streak again  

got 5,07 bitcoin in 12 hours of mining   (~4,5ghs, estimated by p2pool 0,62-0,80/24hr)

I assume I'm misreading this because of currency differences.   In 12 hours we had 4 blocks.  I'm at ~2 gh, which gets me about 0.3 BTC/block.  That's 1.2BTC for 4 blocks.  Scale that up to 4.5gh and I get 2.7BTC.  How did you get 5.07btc?

M

Hi, made screenshot:



even another transaction ~5hours later wich made another 0,60 bitcoin for the block.

And you can see each block gets me less, dont know why that is but I think its the PPLNS system...

Thanks for the screenshot.  You must have had crazy efficiency, or a great luck streak on shares.  I did the math based on your current payout and you're showing around 4.7gh.

M

[aadje93]

And we have a nice luck streak again  

got 5,07 bitcoin in 12 hours of mining   (~4,5ghs, estimated by p2pool 0,62-0,80/24hr)

I assume I'm misreading this because of currency differences.   In 12 hours we had 4 blocks.  I'm at ~2 gh, which gets me about 0.3 BTC/block.  That's 1.2BTC for 4 blocks.  Scale that up to 4.5gh and I get 2.7BTC.  How did you get 5.07btc?

M

Hi, made screenshot:



even another transaction ~5hours later wich made another 0,60 bitcoin for the block.

And you can see each block gets me less, dont know why that is but I think its the PPLNS system...

Thanks for the screenshot.  You must have had crazy efficiency, or a great luck streak on shares.  I did the math based on your current payout and you're showing around 4.7gh.

M

atm (after upgrade restart of node) 112,5% 4,65ghs/s

[twmz]

got 5,07 bitcoin in 12 hours of mining   (~4,5ghs, estimated by p2pool 0,62-0,80/24hr)

Mystery solved:  That's not 5 BTC in 12 hours.  It's 5 BTC in 26 hours

[mdude77]

got 5,07 bitcoin in 12 hours of mining   (~4,5ghs, estimated by p2pool 0,62-0,80/24hr)

Mystery solved:  That's not 5 BTC in 12 hours.  It's 5 BTC in 26 hours

lol

it never occurred to me that was a screenshot of them all those he was counting.  thanks.

M

[-ck]

* Stratum support in the P2Pool protocol. Stratum mining will be enabled in a future patch to v9.

I think this is great news, allowing p2pool to scale to any size in the future, taking a lot of load off the local p2pool software itself, allowing it to concentrate on the business of getting those blocks and transactions out ASAP. Sending higher difficulty targets to the miner will take it even further.

[nibor]

Not much point putting a black line through the end of the addresses!
You only need about 10 characters of an address for it to be unique:
http://www.firstbits.com/?a=1Es9aGimor

[nibor]

P2Pool release 9.0 tag: 9.0 hash: 2cb4d8381e179f71ea2075cdce948ea83cf0dc55

Love the NewNewShare class Made me laugh as much as the recent document I read that said "the NewXXX class is now depreciated".

[K1773R]

Not much point putting a black line through the end of the addresses!
You only need about 10 characters of an address for it to be unique:
http://www.firstbits.com/?a=1Es9aGimor

seems like a winblows user with mspaint

[Aseras]

Or, you could just look at the block from p2pool.info and payouts and figure out who someone "is". Not like having a btc address is worth anything.

Last block, http://blockchain.info/tx/461dc130c75eb95ac54bbdfaff5375ce091f8cdde2d526e554050880471e5905