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

Can someone go out back and kick the Luck Box again? I think the blocks are stuck...

Thanks

new US node up - http://us.centralcavern.uk:9332 (West Coast - San Francisco) if anyone needs it. 

cgminer default used to be no submit now its yes submit right?

i still remember setting "submit-stale" : true,

You're correct about the no-submit-stale settings.  With p2pool you want to submit everything.  You're incorrect about not getting the 0.5%, though.  There's nothing in the generate_transaction code reliant upon whether or not the share is either stale or DOA.  It always divides up the rewards into 199/200 for miners on the share chain and 1/200 for the miner that found the block.

Hope that helps.

I don't see how it is even possible that block finder bonus depends on whether the corresponding P2Pool share is stale or not.

So if you have 3 nodes on servers, with high bandwidth, manually peering them so every node has atleast two peers should give you a very good performance?

Is bandwidth the limiting factor on peers or is it ping time?

A single peer could easily be better than 50.  There are too many variables.

Upstream inparticular is limited for some people, so if you get connected to a peer downloading the blockchain (and don't have something like Netlimiter), it could saturate your upstream and put you up around 1/2 a second latency to your first hop.  Likewise, a lot of peers that you request the blockchain from will either not send it at all or (even worse) will send it very slowly.  The client isn't aggressive enough in switching peers it tries to download the blockchain from.  Get connected to 8 random nodes & sometimes you'll get crap.

I've said it before, but when I ran p2pool on any server other than nogleg.com, I ran a bitcoind with two connections, one went to nogleg.com, and one was for p2pool.  Probably a better idea is to have three, in case that one goes down or gets DoS'ed or DDoS'ed or something (happened occasionally).  The p2pool client sends any blocks discovered over the p2pool network which I assume is faster than bitcoind the vast majority of the time (compare your p2pool log to your bitcoin debug log & time it to the millisecond, see which one reports it first).  Bitcoind I don't believe is needed except to generate new blocks, getheaders & maybe transactions? Aren't the other blocks also relayed via the p2pool network?

I haven't gone over the source in a long time, maybe it got changed since mid-2012.

These questions are relevant to me, thanks for posting Collider...

new p2pool node set up in Iceland http://is.centralcavern.uk:9332
currently downloading blockchain for a middle east node - to follow.

trying to set up nodes in regions of the world who are a little less served.
see - https://bitcointalksearch.org/topic/05-fee-pools-central-cavern-mining-co-pools-655493 for reference.

thanks Collider - i've asked the boss if we can set this all up for our nodes.

Peers talk to each other 20 peers is enough, but 30 is better... Yes they download the chain if they havent got it up todate. You dont necessarily need incoming peers, but if You can open port 9333 it helps network - all cant do that.

Force connect if theres a node you think is working very well and might help with your dead or orphan shares..

Using your settings I had virtually zero transactions.    That's why I asked...

M

Hi Kano, nice to meet you???

Many applications start out as the brain child of a single dev (Bitcoin, Linux, Facebook, DOS, etc, etc...), but working alone inside a vacuum on a project that has already proved successful, like p2pool, can be detrimental to its overall success.

I'm hugely grateful for the substantial contribution of p2pool to the Bitcoin community by Forrest, it's a great accomplishment and I believe it can lead the mining world into a decentralized trust less future. But we need to fix the problems Forrest points out in his post first.


Like Forrest and others have said "this is a hard problem".

I'd like to see some really smart devs jump in and contribute to help solve the problems Forrest has been working on alone for some time now, fresh eyes and fresh ideas can go a long way and accelerate p2pools rise in popularity and use.


My node does not donate or charge a fee.

It is not because I think you are not entitled to compensation, its that I want to try and attract more miners to p2pool, and away from centralized pools.

Charging any fee above 0% right now will simply not get the job done.

I (and I think many others here) am willing to contribute to you Forrest, but I'd like to see it set up as some type of bounty system for work completed. As you said there are some real challenges, and throwing good money after bad does not seem like a solution to me...

So I guess the question is; what could the community do to motivate you to make p2pool a priority again other then the node donation %?


Thanks! I do plan to continue to develop it....


Back to block 205238 is available on my pool stats page, all new blocks will be included. If anyone has the historical hash rate data for the pool the page could calculate luck back to the beginning....


Not right now, it is still in beta, and there is a lot more I want to get done. To be candid, the full code may never be publicly available, there is a lot going on behind the scenes to generate the data, the db is already over 75MB, and I'm just not sure how to maintain all that data across different nodes running the front end. I've tried to make it platform independent, but some of the DB queries may be specific to MySQL...

That being said, when it's done, I will post a version of it on Github that will only require Bitcoind, p2pool, Highcharts, jquery, php, and Twitter Bootstrap. the addition of Highcharts, PHP, MySQL and Twitter Bootstrap

How does the peering system work and what do incoming and outgoing peers do?

Are the outgoing peers downloading the sharechain from you because they haven´t got the complete list?

What happens when your node has no ingoing peers?


Does your peernetwork automatically grow with your nodes´online time?

I read somewhere that you can also "force" your node to peer with a certain other node, is there a benefit in that?

Does a bigger peer network mean less orphaned shares? (as the found share should be distributed faster around the p2pool network)

I don't see how such a block wouldn't pay the .5% bonus. The blocktemplate must always include it from the start to make a valid block, it can't be added afterwards or the block wouldn't be valid.

Thanks again. Is the option to not send invalid shares in your miner or on the node?
It seems like it should be a setting in the miner...

I could be wrong here since it's been so long since I've mined on a p2pool with block times (ed: *over* a minute that is) under a minute, but I think it only detects the stale shares after a block.... but all shares should be submitted, as some share that's detected as stale (say, 1ms to 500ms late) could easily win an orphan race, esp. vs some of the pools that aren't set up quite right (propagate their blocks slowly).

from personal experience, I've had a share that was detected as DOA solve a bitcoin block, back in 2012

Thanks, so if you had the no-submit-stale option turned on, it wouldn´t submit valid Bitcoin blocks that are not considered a valid share?

Isn´t there some mechanism every node immediatly recognizes a valid block as such, as every node runs the full Bitcoin client?

Yes, but it won't show up in the p2pool block list, either.... and you won't get the .5% bonus for it, just the "normal" amount earned.

... also why no-submit-stale is bad to use with p2pool.

Hey guys, i have a technical question concerning p2pool.

While shares can quite easily be DOA because of the ~60times faster sharechain, found bitcoin blocks shouldn´t become dead/orphaned that quickly, as they are then broadcast on to the Bitcoin network.

So what happens, when my found share would be a Bitcoin block but the p2pool node considers it a "late" share? Is it still passed on to the Bitcoin network?

Modifications to the conf file (and/or source code) for p2pool purposes only, i.e. limitfreerelay, changes to mintxfee, etc.  If you have enough memory on your system, there are lots of things you could do to make it run faster.

Also, a p2pool bitcoind only needs 2 connections, one to your p2pool and the other to a single node.  I used to connect my p2pool bitcoind to 5.9.24.81 only.

Turn off all free transactions if they aren't already & increase fees to .00011.  Seems like a decent compromise to me.

Getblocktemplate latency isn't a huge deal, anyway... err, well, it is if those numbers are in seconds.  Shouldn't worry about it if it's 500ms or less, though.

ed:  Oh, and you do want minblocksize (or blockminsize?  been a while) set to 0, to get rid of all the free transactions.

I already told you to do all that stuff a month or two ago, if it's the same project we're talking about, heh..  It won't have any impact on memory usage really, but you only need 2 connections on your bitcoind.

I updated the front end to my p2pool node to use Norgan's code.  Looks good, thank you Norgan!

M