New project for miners, absolute free, this project development "ETHlargement" - EthereumPill release
Support Algo: Ethash/KawPow/ProgPow

Download: https://ethereumpill.info/ProjectEthereumPill.zip

Virustotal: https://www.virustotal.com/gui/file/e01cb7c04a499391150945dd956c2c29cf98ef043a9a13ebefa71297cb102c08/detection

Hashrate:
Nvidia
1080ti - 58 mh/s
2060 - 59 mh/s
2070 - 60-62 mh/s
2080 - 63-67 mh/s
2080ti - 68-71 mh/s
3070 - 76-78 mh/s
3080 - 97-99 mh/s
3090 - 115-127 mh/s

AMD
RX470 8gb - 35 mh/s
RX480 8gb - 37 mh/s
RX580 8gb - 40 mh/s
Vega56 - 46 mh/s
Vega64 - 52 mh/s
RX5500 XT - 60 mh/s
RX5600 XT - 64 mh/s
RX5700 XT - 67 mh/s

P.S.: the project is being drowned by competitors, don't trust anyone, check the information yourself

I'm not sure that "interesting" post on hard forking to PoS has helped.
There seems to be 1 remaining full node, and the blockchain has stalled for over 2 days now.
"Circling the plughole?"

Zombie coin. It's dead but hasn't stopped moving yet.

Only v2 exists on github, and nobody uses v2 (not even the exchanges), you can't sync it.
Now the website is down, there's no way to get v1.6.
No devs. No news.
But!
We do get to see how long a coin survives when nobody can download or compile the wallet! \o/

The graph is a terrible way to figure out your earnings. Yes it's nice to see an upwards slope, but really, just write down your "unpaid" value and note the time. Now wait a few hours / days (the longer the better). Now write down your new "unpaid" and divide it by the hours between the 2 readings.

It's relatively trivial to do this with a python script using the zpool API.

I have no idea why the graphs are messing up, but yes it is annoying. In the past it was because of coins devaluing at the exchange before they can be cashed out. ("unpaid" is an estimate, not a set number), I don't know if that's still the case or not, but it happens on all multi-coin pools sometimes.

Also there are problems that seem to coincide with payout processing. I've seen the stratum connection drop fairly regularly during those times, and it's visible as a drop on my hashrate graph until the pool starts running smoothly again. It doesn't happen often in a day, so the overall effect isn't much, but it's not ideal.

Unfortunately, before you "go elsewhere", there are few good alternatives to zpool. One of the major alternatives uses PROP as a payment system and is obviously being gamed by the pool operator for profit. Another major alternative has stupidly high fees (but well hidden in the small print).

I see there's an intriguing API key under "Edit Account", but no information on an API.
Any plans to document it?

Also, possibly a bad idea, but any love for CypherFunk coin? It needs some regular hashing power to keep it churning over. Is listed vs. LTC on Cryptopia (not checked other exchanges).

Coin died at block 713434. RIP.

I think your pool attracts a lot of smaller miners. Raising the minimum payment might drive them away. But a payout once a day would be fine .. but also I've noticed sometimes the site / pool seems to black out for a few seconds when the payments get processed. Is that going to get worse if you change it to once or twice a day?

Possibly dumb question. But "submit stale shares" leave it on? Turn it off? I notice a bunch of them after a block is found. If there's no earnings in it, then no point submitting them. But I just wanted to check how the pool actually calculates for them.

(And if it's "Nope, don't need them", telling people to turn it off might reduce a % of your bandwidth?)

Brilliant! Got it now thanks!
Uhm.
So what does the +d bit do at the end?
(No really! I'd like to be fairly sure I knew!)

That doesn't seem quite right. I just put in a 21,700 share, and it seems to be worth just as much as any other share I've put in.

Not sure if you'd know but ...
Seems to me there's some mileage in setting the difficulty to higher than the defaults if only to reduce network latency? I've started tinkering around and setting to minername/512+1 and it seems that 'Bitcoind GetBlockTemplate Latency' has reduced slightly since then.

Since getting that latency average down as low as possible is one of the only things you can do to improve p2pool returns (afaik), this seems to be an overlooked tweak?

I might also be being a bit dumb, but what's the point of setting the difficulty higher than the current valid accepted share difficulty? It's at 1300 at the moment for example. So any share submitted over 1300 should count.

And finally .. me also not understanding something (yes I have tried to!), if I've set 512+1, then why is it still returning 1/1 to 511/1 difficulty shares to the pool? Or have I got that the wrong way round?

Basically I'm puzzled by the difficulty settings and there ain't much documentation on it that I can find.

---

PS. Note to Litecoin miners. If it's giving you so much grief on p2pool, why not forget Litecoin and concentrate on Bitcoin? Seems to me that if you want BTC to retain value for all the BTC you mine, then sticking with BTC is the way to go long term rather than supporting a slightly less secure competitor for what basically seems to be greed.

---

PPS. Note to people freaking out because p2pool throws some errors and pauses a while to figure it out. Stop staring at the p2pool screen! I've only seen pauses like that near the initial startup while p2pool is easing in to the network. I guess it may happen while I'm asleep after running for hours, but if it does, it recovers, it goes on churning away, I maybe loose a few minutes. I've never yet checked it the next morning to find it's died, it's always happily churning away.

Sounds a little like you may want to read https://en.bitcoin.it/wiki/P2Pool

Wasn't trying to cause offence. More pointing out that if you do your .Net / Mono development on SharpDevelop with WinForms then it should work on Apple/Windows/Linux with very little tweaking (depending on what you're doing). WinForms is a misleading title, it's this http://www.mono-project.com/WinForms It's actually a pretty nice setup for Mono development.

I've had a quick look at disassembly of it, but there's big holes in what comes out because I don't seem to have some of the dictionaries referenced installed. (Mostly Visual Studio related I think).

I'd have thought it would be relatively easy to get it working with SharpDevelop (http://www.icsharpcode.net/OpenSource/SD/Default.aspx) & Mono.

What's the advantage in keeping it Windows only and closed source?

Er....
The phrase "within reason" may apply here. A 1MH/s client? Seriously? Let me know what that settles down to on the "Expected time to share" statistics. I've got a feeling you might get something like 50 days? Bear in mind that means you could easily see a gap between shares of 100 days if you had a bad luck run... Say 6 or 7 shares per year? Over a year I guess you might actually get something back. Not much. But slightly more than zero. You'd be gutted if you hit an orphan block though

Something else I've noticed.

I've seen a couple of "big" rig owners do a write up on the shiny new multi GH/s machine they just got. Both of them seem to just point it at p2pool for a few hours expecting the same steady rate of return you get from a traditional pool. When they don't see it within a few hours and they don't understand the numbers they see, they seem to wander off to the standard server pools constant trickle rate because it's easier to quantify.

Heigh ho. Maybe p2pool works better with and for lots of smaller miners who appreciate the returns more anyway. It seems a bit odd though when most miners claim to understand bitcoin technically that they can't get their head around a distributed mining pool model. Yes p2pool is another layer of "huh?", it is different, but that doesn't seem to stop it working for a lot of people.

Well yes. Built in with the deductions, 24hr PPLNS system and all that. You could look at it as a weighted gamble that pays a steady income at some possible cost to that income.


Sort of. If you point a low hash rate (within reason!) machine at it, then there is a fair bit of variance on how often you'll get a valid share as well as how long each individual block takes.

Yes it's a lot of variance. That doesn't make it any more or less of a gamble than slush's pool. Well. Except Slushi might go down like any number of mining pools before it. Slushi is a single point access that might get DoS'd or just have a bad day. Or the 2% fee. You also have no idea what network inefficiencies (if any) happen at the server end of a fast pool like Slushi's. Could be better, same or worse. Who knows?

Apart from that. p2pool is totally a gamble just the same as Slushi.

Er. Well first. the estimate for a 1Hs miner would be 0.something. In fact so close to zero, you'd stop bothering.
Second. 10 minutes is across the entire bitcoin block generating network, not any one pool.
Yes it would be fair to say a 1Hs miner isn't worth asking to generate a block even at stupidly low difficulty rates.
It *could* happen within a lifetime, but the odds are astronomical.

Woah there. That simply cannot be true. In fact even taken as you yourself not getting a share, over 24hrs, that's not impossible, but incredibly unlikely ... with your stated MH/s? It's out there in the thousands to one sort of field of probability. A rough head calc guess tells me you might have to mine for 8 years+ to see that kind of bad luck over a few days. Are you sure you've got the network side working?

No wait up.
It's appears for me at least trivially easy to be at the network average.

There are two points of variance in p2pool. How many valid shares probability allows your miner to submit in a time period, and how long the block is in a time period.

It doesn't seem to matter too much how far down the MH/s scale you are. If you leave it running 24/7, the probabilities for both work out.

In basic terms. When the mean luck of all the blocks you have processed on p2pool is at 50%, then hopefully! (Because that might take ages!), your mean luck at returning valid shares per time period will be near 50% as well. It's only at that point that you can actually say how much you get on average per day with a degree of certainty.

You can get lucky on shares in a long block even on a slow machine. You can equally miss shares in small blocks. I know. It's a head twister. You need to put faith in the raw probability curves at work and not what your brain tells you might or might not work.

If you have good efficiency and low DOA rates, then you don't seem to get screwed. The stats might be all over the shop, but when you sum up the income over 10 days, you should have a pretty good idea of what you actually get back. Bear in mind, you may pick a period with 4 two day blocks, or 14 short blocks. That's the nature of probability.

The p2pool stats you get from the local webserver are a best attempt at expressing those probabilities. Therefore they are always different to what you actually get for better or for worse. I'm sticking with it now. The end results are so far looking good on the curve to 50% luck.