With the new ASIC-compatible version of p2pool, is it still recommended to turn off queuing in cgminer?
Any input on this? I'm trying p2pool with my Jalapeño and I'm curious if this still makes a difference.
Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 502. (Read 2591928 times)
With the new ASIC-compatible version of p2pool, is it still recommended to turn off queuing in cgminer?
Any input on this? I'm trying p2pool with my Jalapeño and I'm curious if this still makes a difference. 
Thank you twmz and baloo_kiev, that explains it. 
It basically works the same as Eligius, then. Mine with your address to get paid, mine without to donate to the pool funds.
It basically works the same as Eligius, then. Mine with your address to get paid, mine without to donate to the pool funds. 
There could be corrupt nodes that ignore your address though.
I think the point he is missing in the discussion is that p2pool is a share chain like bitcoin is a block chain
(and of course the share chain is a construction 'above' the block chain)
Everyone using p2pool is mining against the same share chain and your shares will not be accepted unless they pay out everyone mining as per the current share chain
You don't have a private p2pool that is only for you.
I also wonder if he's missing the point that you can't redirect a hash to somewhere else without effectively mining for that somewhere else (e.g. you'd be solo mining thus only finding a block every ... once in an eternity)
(and of course the share chain is a construction 'above' the block chain)
Everyone using p2pool is mining against the same share chain and your shares will not be accepted unless they pay out everyone mining as per the current share chain
You don't have a private p2pool that is only for you.
I also wonder if he's missing the point that you can't redirect a hash to somewhere else without effectively mining for that somewhere else (e.g. you'd be solo mining thus only finding a block every ... once in an eternity)
I'm confused - if I open my p2pool to the general internet public, how do they get paid? Does p2pool do all this automatically?
If Joe Bloggs mines on my p2pool node using his BTC address as his username, does p2pool automatically pay Joe when a block is found?
If Joe Bloggs mines on my p2pool node using his BTC address as his username, does p2pool automatically pay Joe when a block is found?
The way p2pool works is that the coinbase transaction (generated by the node that finds the block) directly pays the 25 BTC to each of the addresses that earned the payout. This is true regardless of if someone mines on a private or public node.
So payments go to other/my nodes, rather than to miners who connect to my node?
So, if Joe Bloggs connected his miner to my pool, he'd just be donating some hashes to my node for no reward?
payouts go to the addresses that found shares. If a miner connecting to your node uses their address as their username and finds shares, they will get paid. If they don't use an address as a username, your node will use your node's address for any found shares (i.e. they are donating hashes to you). You can also specify a fee % so that some percentage of the shares they find will be assigned to your node's address instead of the address they used as a username.
I'm confused - if I open my p2pool to the general internet public, how do they get paid? Does p2pool do all this automatically?
If Joe Bloggs mines on my p2pool node using his BTC address as his username, does p2pool automatically pay Joe when a block is found?
If Joe Bloggs mines on my p2pool node using his BTC address as his username, does p2pool automatically pay Joe when a block is found?
The way p2pool works is that the coinbase transaction (generated by the node that finds the block) directly pays the 25 BTC to each of the addresses that earned the payout. This is true regardless of if someone mines on a private or public node.
So payments go to other/my nodes, rather than to miners who connect to my node?
So, if Joe Bloggs connected his miner to my pool, he'd just be donating some hashes to my node for no reward?
Miners have to specify payout address as their username. If they give an invalid address or any other login or no login at all, they will mine to the node's address.
With the new ASIC-compatible version of p2pool, is it still recommended to turn off queuing in cgminer?
is p2pool now 100% Avalon - ready?TIA
With the new ASIC-compatible version of p2pool, is it still recommended to turn off queuing in cgminer?
is p2pool now 100% Avalon - ready?TIA
I'm confused - if I open my p2pool to the general internet public, how do they get paid? Does p2pool do all this automatically?
If Joe Bloggs mines on my p2pool node using his BTC address as his username, does p2pool automatically pay Joe when a block is found?
If Joe Bloggs mines on my p2pool node using his BTC address as his username, does p2pool automatically pay Joe when a block is found?
The way p2pool works is that the coinbase transaction (generated by the node that finds the block) directly pays the 25 BTC to each of the addresses that earned the payout. This is true regardless of if someone mines on a private or public node.
So payments go to other/my nodes, rather than to miners who connect to my node?
So, if Joe Bloggs connected his miner to my pool, he'd just be donating some hashes to my node for no reward?
With the new ASIC-compatible version of p2pool, is it still recommended to turn off queuing in cgminer?
I'm confused - if I open my p2pool to the general internet public, how do they get paid? Does p2pool do all this automatically?
If Joe Bloggs mines on my p2pool node using his BTC address as his username, does p2pool automatically pay Joe when a block is found?
If Joe Bloggs mines on my p2pool node using his BTC address as his username, does p2pool automatically pay Joe when a block is found?
The way p2pool works is that the coinbase transaction (generated by the node that finds the block) directly pays the 25 BTC to each of the addresses that earned the payout. This is true regardless of if someone mines on a private or public node.
I'm confused - if I open my p2pool to the general internet public, how do they get paid? Does p2pool do all this automatically?
If Joe Bloggs mines on my p2pool node using his BTC address as his username, does p2pool automatically pay Joe when a block is found?
If Joe Bloggs mines on my p2pool node using his BTC address as his username, does p2pool automatically pay Joe when a block is found?
I had a look at things when I got home, and I've set up a Pentium G620 (dual core 2.6GHz Sandy Bridge) to run both the p2pool and also it's running the Block Erupters. It'll run the Jalapeno if it ever appears, too. The Celeron was maybe a little too slow - might have been OK running Linux, but I don't have the patience to set it up that.
Pool is available now (hopefully) on http://847pool.no-ip.biz:31337 for web stats; port 8333 for mining.
Pool is available now (hopefully) on http://847pool.no-ip.biz:31337 for web stats; port 8333 for mining.
Nice, 2 more blocks last night while I was asleep ... I got one of them 
(my first block in MANY months)
(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).
Nice, 2 more blocks last night while I was asleep ... I got one of them
(my first block in MANY months)
(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.
Man I want the i7 4770 haswell
i'm running bitcoind/litecoind and p2pool for each on an ODRIOD-U2 without any issues. it's a quad core 1.7ghz arm with 2 gb ram ~$120 shipped. it's pretty much like a pi on steroids.
also, i put in a pull request to change the links to blockchain.info instead of blockexplorer, which doesn't even seem to be working anymore.
also, i put in a pull request to change the links to blockchain.info instead of blockexplorer, which doesn't even seem to be working anymore.
Idk the celerons, atoms and i5s I've used are trash
I'm running p2pool/bitcoind/altcoinds/cgminer on an Intel Next Unit of Computing with a Celeron 847 @ 1.10GHz, 4GB RAM with 4x AsicMiner USB Eruptors. I had to move the blockchains (bitcoin, devcoin, namecoin, ixcoin) to an external USB hard drive (system drive is 32GB SSD). It took some tweaking, but my get work latency is ~0.2-0.3 and I see DOA of 1.5% and 101.5% efficiency. CPU load seems pretty low (~80-90% idle mostly). Seems fine to me. Biggest problem is that my share luck seems to be inversely proportional to p2pool's block luck.
The NUC is brilliant, I have one here as my HTPC (it's the i3 version). I've got it in a Tranquil passive case. Totally silent.
The 847 I have is on a MiniITX Gigabyte board. Current specs are 4GB RAM, 250GB Samsung 840 SSD. In the hour or so it's been running, it seems to be doing OK. I'll give it a few days and see how it performs, I have plenty of spare hardware I can throw at it.
I'm running my miners on a different machine, though that may change. I might run the ASICMiners off this machine, too, if it can cope. Leave my main PC to do it's thing.
One core is basically running flat out for p2pool.exe all the time.Initial impressions seem good though.
Running OK now, it took a little while to settle down.
I also found the graphs.
I'm running a browser on a Remote Desktop session to my p2p machine via my home PC via LogMeIn, which is reducing 1080p res to 1280x1024 for work PC. Slow, laggy and tiny. Jump to: