Re: [1400GH/s] p2pool: Decentralized, DoS-resistant, Hop-Proof pool

Nice, 2 more blocks last night while I was asleep ... I got one of them Cheesy

(my first block in MANY months)

Edit: ... and I've spent some time now (since that post) working out why my block sux.
It is only 16k and only had 28 txn in it.
My bitcoind (default 0.8.3 settings for txns etc except: paytxfee=0.0005) on the other hand at the time had 1854 in it's mempool:

Code:

2013-07-25 16:25:43 CTxMemPool::accept() : accepted 7b1f0fd72e281abdb9b6724aa839b872550a3e7ff8de395dfbe20cd92777d4ae (poolsz 1854)
2013-07-25 16:25:43 ThreadRPCServer method=submitblock
.
.
2013-07-25 16:25:44 SetBestChain: new best=000000000000006e312482364ffc008b8fabad506fefde343a1acfc1f64ae982 height=248394 log2_work=70.874866 tx=21101483 date=2013-07-25 16:24:32 progress=0.999995
2013-07-25 16:25:44 ProcessBlock: ACCEPTED
.
.
2013-07-25 16:25:44 CTxMemPool::accept() : accepted c75dd649944be1e262c3c82fda612e29c1631b74b7563f0142e28486623c2217 (poolsz 1828)

... anyone care to explain that before I switch over to some other pool ... it really does look like it's p2pool itself that decided to produce that crap block ... unless I've misunderstood somewhere ... or are there hidden options in p2pool that I need to fix and the default settings suck?

P2Pool sometimes has to limit the number of transactions in a block because of per-share tx inclusion limits. Only 50kB of new transactions are allowed per-share, so it takes time the pool of allowed share to build up.

I didn't have a clue p2pool controlled the precise list of transactions in the coinbase. I assumed it was all or nothing as the expected block income as reported by p2pool was rising after a bitcoind restart (with more transactions being learned by bitcoind) and fees only briefly were 0 after a new block, rising sharply immediately after it and resuming a slow rise (as I assumed, transactions kept coming in).

Is the pool emptied at each new block? 50kB every share is 1MB/average block interval. This is not enough to build full blocks half the time if the pool is emptied though.

Could you take the time to explain how p2pool handles transactions in more details (and maybe paste it on the bitcoin wiki page for p2pool if you have the rights to do so)? One of many questions is how it behaves when nodes don't have the same bitcoind settings (meaning they don't process the same transactions).