You probably have a few rogue dust bunnies in there.  As a side note -- and I seriously doubt this has anything to do with it but -- this is the miner I gave fubly's crack a run on and had to eventually reflash with Bitmains first s9 update to get running.
How can you be sure? |
|
|
|
You totally could have used these for prizes in your competition.  |
|
|
|
I would check the website http://holybitcoin.com/ out. HolyScott, the website owner, is a well known forum member and he is probably one of the few folks still selling them. He does take PayPal if that helps. |
|
|
|
You have to have a really low hashrate to not get a share within the payout window. The S5 at 1.155 TH should on average get a share at least once an hour which should yield ~75 shares within the payout window.
Yes, on CURRENT hashrate. Take step back, when P2Pool was 3rd-5th biggest mining pool. What HR you will need when pool is @200TH or 500TH not 1TH? Under the current solution, individual miners, within reason, need to scale with the pool. In my opinion, working through the effort of created multiple share chains to accommodate dust payments is irresponsible and is a complete disservice to both the miners getting paid dust payments and the folks working on development. However, if there was a way to accumulate dust payments and/or have the ability to opt-in to carryover payments from block find to block find within the share chain until a certain threshold was met, then I would say that was a reasonable solution. |
|
|
|
P2Pool protocol need major change.
Standard pool role is to make miner variance LOWER. At the moment, when P2Pool power raise miner variance raise as well.
Also, when power raise smaller miners are unable to get share and payout.
You have to have a really low hashrate to not get a share within the payout window. The S5 at 1.155 TH should on average get a share at least once an hour which should yield ~75 shares within the payout window. To keep decentralized structure of pool, I see that P2Pool protocol can adopt few share chains on different share power (diff).
This way, we will have "payout" chain, that store share information ready to pay and few (2? 3?) chains storing lower diff share information.
Having additional share chains to store low difficulty shares only creates more problems for miners with really low hashrates. Specifically, it will enable payouts that are essentially dust. |
|
|
|
|
I still roll 5x Bitmain U1 miners on a Raspberry Pi. It is only useful for the entertainment of watching the blinking lights. I point them at p2pool along with 4x S3 miners and they make a decent little payout every time we find a block.
|
|
|
|
You could always mine on p2pool and if you get lucky to find a share or two before a payout, you might make a few satoshi. |
|
|
|
P2Pool has consistently been above a 1 PH average as of recent (about a month or so). This slight surge is higher than the relative growth of total Bitcoin network Hashrate over the same period. P2pool is currently less than 1% of total network Hashrate. If we can continue to grow just a little bit more, this variance should improve dramatically.
I understand the variance is mathematically calculated the same in either case, but I believe there's a psychological element to it for P2Pool miners (especially new ones). Hitting a block every couple of days is dramatically different then hitting every couple of weeks. Feels like a precipice to me...just need to grow a little bit more 😉
If p2pool could push into the >2PH range, I believe we could improve the psychological element significantly. Honestly, I would be a lot happier if we were in the 3 to 5 PH range, but unfortunately we are not there. |
|
|
|
I was on a point to revert all my work to yesterday 9am, but now I fixed a memory leak and the new version which is at git now,
compiles perfect (with some errors) and works well.
I am confused. How can you say "compiles perfect", but still have some errors. Is that not the very definition of not compiling perfectly? What compile time errors are you getting? |
|
|
|
|
Difficulty projections are increasing. Last I saw was 3.5% on nextdifficulty.com and it looks to be possibly increasing beyond that.
|
|
|
|
A super-low-quantity batch like that would help explain the high unit cost, since engineering and tooling (especially for the case) need to be absorbed somehow.
Of course, a combination of two truths - "people are, in general, idiots" and "Bitmain is greedy" - also explain the rapid sellout despite high prices without speculation of unknown factors.
The R4 was listed for several days before it sold out. I honestly expected it to sell out in less than 6 hours. Personally, I did not buy one because the price was ridiculous and Bitmain has a knack for disregarding the GPL. At this point, I would prefer to wait for Avalon to potentially never release a product than to contribute any further to Bitmain's overpriced under warrantied product line. |
|
|
|
The price is rising, I expect the difficulty follow the trend.
I somehow fear that my pick is too small, but we will see what the future holds for us.
I agree with you. I was thinking that 5.0% was going to be too small. |
|
|
|
I see, glad to hear that !
Are there any issues / bottlenecks - apart from lack of miners ?
Nope |
|
|
|
Come on three in a row!!!
I am kind of bummed because one of my miners glitched out and it was only mining at 20% speed for 4 shifts. A whole day went by before I noticed. UGH |
|
|
|
Finally, we are on to the next block. GREEN GREEN GREEN |
|
|
|
It is nice to see p2pool is still around.
Well done !
We are still solving the occasional block. |
|
|
|
|
It looks like there is another small downtrend going on. This next difficulty could go either way IMHO.
|
|
|
|
Just received the first batch of APW5 PSUs and R4s. I was a little uncertain about the actual number of 6-pin PCI-e connectors it came with due to some of the images showing only 7 connectors total. I'm pleased to share that there are indeed 14 x 6-pin PCI-e connectors, as originally advertised by Bitmain. The APW5 does appear to be capable of supporting 2 R4s with a single PSU (using 220v power).  Nice! That is a lot of connectors. |
|
|
|
|
Show Posts
