Topic: [∞ YH] solo.ckpool.org 2% fee solo mining USA/DE 255 blocks solved! - page 266. (Read 1514780 times)

I swear.. Renting hash can feel like ill-gotten losses. The whole "Well, the hardware isn't worth the cost of what it can ROI." seems a lot better than: "Throw some BTC in a cloud farm, which are profits to the owner, in hopes of a win."  I'd rather own the overpriced hardware I guess At worst, you can rent out some of your hash to make up for losses.  At best, you can hit a block and sell the equipment for a decent profit.  

I remember renting 1P for 30 minutes got a 10B share...
But you gotta hope nakamoto blesses you with a block

I tried that also, 3 times I rented 1P for 24 hours from NiceHash, Best share was 5B, so I rented 50T for 18 hours and hit a block.  Go figure...

Ive had some horrible luck. Ran 1PH for 6 hours, 500TH for 3 hours, 100TH for 12 hours, 50TH for 1 day and I've been running a S5 for over 2 months and my best share after all of this has been 0.99 billion...

Didn't know you had hit a block, congratz on that one.

Hopefully lightning won't hit you but some more btc blocks will ;-)

Yes, but remember I hit a block last week with 50T.  Maybe lightning will strike twice!!

With 50T shouldn't you better call it "gambling" instead of "hoping"? Don't want to spoil the fun though but in the the long run isn't it just luck you are counting on when renting 50Th?

I have a 21B share this round with my 50T rental.  Hoping!!!

I pulled a 7B share with 3S3s. I pulled the U3 out as it kept going zombie on me. Total power is roughly 1.3TH. Letting the blocks roll in guys

Funny you pulled a best share of 1.9B with a 12 hr 100TH rental. My friend pulled a 1.1B share running his GPU as a test for two weeks at 500MH/s :O
Jacob

36000 Km x 2 @ C => 240 mS (Signal Runtime) + Handling that is close to the border OK it works!

Nice to see how everything fits.


Of corse, ty Kano for a deeper understanding of the timing (I dont know the technics behind the stratum protocol).

I was just reporting, because the server is new and I like a good performance, so i tryed to ping the pool
and was realy supprised about the short time.

Well ... if you had mining hardware that could handle a block change instantly ... ok lets call that 1ms ...

If at some pool you where getting 0.4% rejects/stales that were thus really only due to network speed, then 0.4% of 600s is ... 2400ms ...

The main point of my comment is that a 101ms ping time is only a part of what you need to consider.
Using only the ping time to decide will certainly give you the wrong answer unless the ping time is very large.

Still running, bestshare": 19198012551.985401, that was from yesterday.

What makes me thinking about some chinese pool's.
They use SAT I-Net for connection, wich give you a latency greater 600 mS.
I used it for 3 years also, because I am living on the country/forrest side with no speedy i-net.

How can they secure a good share rate then?

 

I threw 100Ths at it yesterday for 12+ hours and didn't see anything higher than 1.9b 

To put that image at a size that would still be too big for the importance and accuracy of the content:


There is no magic 100 is "Looking good" but 101 is "Too far"

One problem with that image is that it is telling p2poolers to centralise p2pool.
Right ...
The idea of p2pool is to run it yourself so you can indeed make the claim that p2pool is decentralised.
The image is telling people to centralise p2pool and mine on other nodes.

Now if you were silly enough to mine on someone else's random who knows what set up p2pool node, then their node configuration is just as likely to make even a 500ms ping time almost totally irrelevant.
Most of them are, to be blunt, poorly configured and slow to handle work changes.

--

So now, when discussing pools with high performance hardware and software (and pools that don't have that ...)

The performance of solo.ckpool.org (and kano.is closely behind it ) means that the fast pool work change time will make even a sizeable ping time worth your while mining.

The ping time vaguely infers your stale share rate, so of course a higher ping time will mean higher stales.
But also remember that a block time average is expected to be around 600s (or less at the moment) so even a 600ms work reply time would put your stale shares caused by that at around ... 0.1% ...
The problem isn't so much your ping time as it is the mining hardware being able to switch work quickly.

So yes, ping time is quite relevant if it takes you 2000ms to get a packet from the Antarctic via penguin satellite to Tasmania then weave it's way through the crappy internet of Australia and make it to a pool somewhere else on the planet, but in general the pool's work change time will usually be way more important to determining if you will find a block ... which is all that matters here on solo ...

here is the lowest estimate I can find

https://bitcoincharts.com/


Blocks   389403
Total BTC   14.985M
 
Difficulty   93448670796
Estimated   96038295084 in 1701 blks
 
Network total   803850.738 Thash/s
Blocks/hour   7.21 / 499 s


 so if you take 96 and 108   the middle is 102 for  next diff   or a 9 to 10% jump.

still big a very big  number   about   90ph in hash

That's for sure. 93 billion - I don't think any of my miners have ever seen a number that high.
Next estimation is 108 billion.

 

Big Diff jump.  Much harder to hit a block!!  Been suck on this bestshare": 19198012551.985401 for a couple days!!

<>

  i go to bed now, right on your server.

It is too late now, have to realy go to bed, tomorrow i will try to setup a bitcoind then.

good night