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

maybe yes maybe not.
the developer already turn off the p2pool vps (vps.forre.st) ?
developer abandon the project ?

v16 in progress (?)

Hi there, that is my node!  

1) Payouts from the pool will vary depending on the overall hashrate of the pool.  Your expected payout will change from hour to hour, day to day, depending on the conditions of the pool and the shares you have found.
2) That payout is for the entire node; and is only if the pool finds a block and will vary depending on fees in the current block being mined and your valid shares.
3) Expected time to block for the whole pool right now is around 10+ days, so yeah.  That is just an estimate though and due to variation could be anywhere from a couple days to a couple weeks.

Just hang in there and monitor the chart for your workers, it will tell you the expected payout for your miner.  Your current mean payout is around 0.85 BTC.

If you run your own node, you may have better results (less latency issues).  If you need help in setting one up, PM me and I will assist you.

From what I noticed, some of your miners have issues at times and your DOA rate spikes.  I have the same issue with some of my S7's; they will just timeout and stop hashing and need to be rebooted, or just produce nothing but DOA work until they settle...  Everything else looks okay, and I tweaked my node [initially] to help your miners.  

The Node's efficiency remains above or around 100%. I mostly monitor that parameter, If that is around 100% all is pretty much well.

http://p2pool.science/1DHY.png

Hello,

I started to mine on P2POOL. My hardware is 5x Antminner S7. I'm posting to p2pool.science and I have few questions:

1) Why it seems to be like my earnings not always go up. I've watching them go a little down instead of slowly grow when I have slow hashing power.
2) Is the term: "payouts if a block were found now" true? I mean, never received a payment from p2pool net, but is it true? is actually the amount I earn if a block if found now?
3) I found in a webpage a term: "Expected Time to Block = 12d ...." Is it an expected time to get a block on the net?

Payouts seems to be higher than in antpool. Am I wrong?

Thank you!

What error are you referring to?

Both those links leads to the pages with some strange info. http://p2pool.info/ says that last block was found more than a year ago. http://forre.st:9332/ doesn't even shows a hashrate... 

Here we can se a more precise and actual stats: http://minefast.coincadence.com/p2pool-stats.php

But I like an official links...

I was confused. My bad!

So, if the node has a 0% fee, what does the -a or --address option do?

No

I was referring to not having the bitcoind out in the open as much as possible as "hiding the mining bitcoind"

i.e. if you had a wallet on it also, there may be consideration of not having it too easily accessible, but without a wallet, there's much less issue about having it well connected and "in the open"

Your initial phrasing was confusing because we were talking about running bitcoind without a wallet. I thought that you may have been saying, "running bitcoind without a wallet is counter productive to distributing blocks quickly." However, I now understand that you were pointing out the obvious that p2pool is hiding the mining from bitcoind and that p2pool is counter productive to distributing blocks quickly. Well, no shit! LOL That is the price individuals pay to operate their own trusted nodes on a trust-less network.

Well, to state the obvious, distributing from, and getting network blocks to, your bitcoind is of course the most important part of any mining network.
If you are working on old blocks, then you are trying to generate a block that wont be accepted.
If you find a block, you want it to get out and everyone else to work off it, not some other block.

For non-p2pool that's bitcoind connections, connection to the block-relay, and any other custom distribution you have.
For p2pool that also includes the p2pool network itself, since it's a block-relay also
(as I've said before about centralising p2pool is bad for p2pool since it reduces the effectiveness of that relay)

So, a lesser one of those 3 for p2pool mining is your bitcoind connectivity.
Of course you can say, well everyone else on p2pool distributes the blocks ... but that's the same as saying ... well maybe no one else on p2pool does either.
Thus:

Got it!

I am confused about your hiding the mining bitcoind statement. What exactly is counter productive to distributing blocks quickly?

Slush's Pool, yeah, I remember that. I own and run my own server stacks. I trust no one.

Completely separating the wallet from mining means a few things:
1) The wallet actions don't affect your mining
2) The wallet code in bitcoind can be disabled and thus improve bitcoind performance
3) The contents of your wallet are not accessible from anything that can access your mining
4) Your wallet can be anywhere, separate machine, cold wallet, paper wallet, whatever

In general, keeping a wallet separate from mining is a very good security precaution.
Hiding the mining bitcoind is counter productive to having it distribute blocks quickly,
but limiting all access to a wallet is a good thing

P.S. never have a wallet bitcoind online in anything that you don't 100% control.
Slush's lesson is a good lesson to learn regarding that ... a few years ago 10's of 1000's of BTC in his pool wallets on linode were taken by someone with access in linode through the back door that they purposely had in their system ... ... ...

I thought as much. The documentation for the -a or --address option stated "generate payouts to this address (default:

), or (dynamic)" and it was not clear to me that the -i or --numaddresses and the -t or --timeaddresses options were directly tied to the -a or --address option when operating under the default behavior. Thank you for the clarification/confirmation.

Are there any advantages, speed or otherwise, to using or not using a wallet with bitcoind for p2pool?

They are for dynamic addresses using bitcoin wallet and not required when you use -a or -address

numaddresses is the size of the new adress pool maintained, default 2
timeaddresses is how long to use an address before geting a new one, default is 2 days

I recompiled bitcoind with the --disable-wallet option on my node. I know p2pool definitely requires the -a or --address command when running with no wallet and is a good practice to use generally, but does it need any other options to run without a wallet?

What exactly do the -i or --numaddresses and the -t or --timeaddresses options do?

Got it. It wants the same thing either in hexadecimal or decimal.

You need to change the block version in the P2Pool source code, it's line 372 in work.py, to:


or


Both work.

Are there any major issues with switching a p2pool node to Bitcoin Classic?

You're confusing the ckpool software which kano was talking about with kano's kano.is ckpool. But now we're way off topic.
To make it on topic, note I have on numerous occasions suggested ckpool can be used as an intermediary to make part of p2pool scale better, but that adds yet another layer of complexity to setting up p2pool.

GUYS

You seem to be forgetting that this is a forum for discussing p2pool; not for promoting other pools or constantly poking holes in p2pool and it's low hashrate.

Something that would *really* help would be for competitors to p2pool (which is a minnow against the Goliaths such as CKPool) to keep off this discussion group.

I know p2pool node operators have a choice on how much they donate to forrestv...

BUT where do CKPool users have a choice on how much they 'donate' in fees ?