KanoPool since 2014 🐈 - PPLNS and Solo 0.5% fee - Worldwide - 2436 blocks

[wmabern]

Just found out for sure what batch number the S7 I bought online last night is. It's a batch 16 with one fan.
I wasn't expecting that.
I guess I shall find out how it performs and if it needs extra cooling.  
As long as it puts out TH without temp issues, I'll be fine with it.

edit: Anyone else on here have the batch 16?

I have two. They run 10-15C hotter than the B9 I've got, 10C hotter than my S2, and 20C hotter than an S3. I've a bunch of ambient CFM pointed at them, and they're running a consistent 70-79C on all three boards. They're also at least 15db noiser; the fan runs at 6K rather than the 4K on the earlier 2-fan models. Watch your temps for a couple of 24hr cycles just in case. They're mining just fine, though. Will be ordering two more in a couple of days before my coupons expire. That'll max out my flat for sure.

Thanks a lot for the info on the batch 16. I was wondering how they would do temperature-wise. I have two other S7's - I think they are batch 10, but not sure all.
I have a small AC unit pointed directly at the air intakes and a 20" box window fan to suck the heat out of the room. With them both over-clocked to 725MHz, they are both running in the low to mid 50C's.
I will have to do some rearranging in the miner room when the 3rd one gets here probably Wednesday or Thursday.

I want to make sure the 16 will get it's share of the AC flow. Louder won't both me as they are in another room with a door between the rest of the house.

You may have noticed my posts earlier about having to drop my rentals because of the pools bad luck. Right now I'm getting a little over 10TH between the two miners I have, so it will be nice to be able to add a little more hash of my own.
Are you running the 16's at 700MHz? I will probably let mine run at that level until I see how the temps look over a week or so.
Again, thanks for the info! And,
LETS GET SOME BLOCKS!!!!  

[1714976546]

1714976546

[1714976546]

1714976546

[1714976546]

1714976546

[1714976546]

1714976546

[Crispyato]

Ok chicken and restart

[kano]

...
Also is it possible on rentals, that due to the extra time involved to go from the miner to the rental network, then to the pool adds
unattractive latency or delays to the share transmittal? IMO this could add an issue with finding blocks, vs direct mining to the pool.
...

Yes using a random proxy adds latency.

Worse the fact that the miners on that proxy are who knows where on the planet.
It works like this:
Miner (who knows where) -> Proxy -> Pool -> Proxy -> Miner (who knows where)

So indeed it adds latency.

[thedreamer]

Thought so. So all the large rentals are effectively lowering the earnings due to the larger pool hash rate, while lowering the chance to hit a block.

[firetreeactual]

Just found out for sure what batch number the S7 I bought online last night is. It's a batch 16 with one fan.
I wasn't expecting that.
I guess I shall find out how it performs and if it needs extra cooling.  
As long as it puts out TH without temp issues, I'll be fine with it.

edit: Anyone else on here have the batch 16?

I have two. They run 10-15C hotter than the B9 I've got, 10C hotter than my S2, and 20C hotter than an S3. I've a bunch of ambient CFM pointed at them, and they're running a consistent 70-79C on all three boards. They're also at least 15db noiser; the fan runs at 6K rather than the 4K on the earlier 2-fan models. Watch your temps for a couple of 24hr cycles just in case. They're mining just fine, though. Will be ordering two more in a couple of days before my coupons expire. That'll max out my flat for sure.

Thanks a lot for the info on the batch 16. I was wondering how they would do temperature-wise. I have two other S7's - I think they are batch 10, but not sure all.
I have a small AC unit pointed directly at the air intakes and a 20" box window fan to suck the heat out of the room. With them both over-clocked to 725MHz, they are both running in the low to mid 50C's.
I will have to do some rearranging in the miner room when the 3rd one gets here probably Wednesday or Thursday.

I want to make sure the 16 will get it's share of the AC flow. Louder won't both me as they are in another room with a door between the rest of the house.

You may have noticed my posts earlier about having to drop my rentals because of the pools bad luck. Right now I'm getting a little over 10TH between the two miners I have, so it will be nice to be able to add a little more hash of my own.
Are you running the 16's at 700MHz? I will probably let mine run at that level until I see how the temps look over a week or so.
Again, thanks for the info! And,
LETS GET SOME BLOCKS!!!!  

I won't overclock mine. I tried 725 and they went up 5C, which in this instance is enough to put it over 80 and shut down. I'm happy with a steady 700.

[kano]

General Kano - are you sending us some BTCs before you turn in tonight? Thanks...  

I use my mining to pay the txn fees and my miners were off (accidentally on thu night) and the PSUs both stopped working when I switched them on, on fri night (and I didn't notice until sat morning)

So when I generated the payouts for 409446 and 409453 I had no BTC for the fees.
Both payouts were zero fee and I then spent an hour sorting that out to ensure they were (automatically) in the pool work even through they were zero fee.

So yeah they didn't show up anywhere else on the network since anyone else (most likely) rejected the transactions.

As you would have noticed, since they were in our block work, they were confirmed by our block.

We get about 3-4 blocks a day ... on average ... so usually that should be ok.

[wolfen]

What was the fee amount?

[firetreeactual]

No worries. It all comes through eventually. 

[kano]

we'll my prediction of 6 blocks or more when i awaken has failed me miserably

have some chicken sandwich for breakfast -- that usually works for this pool in the past... now we just passed 371% another monster RED block -- back to back massive RED blocks - what are the odds?

Yeah the CDF[Erl] actually says what the probabilities are of the last N blocks so you can get it off the web page:

Code:

Last  5 Blocks  2.5days  101.9%  220.42%  220.42%  0.9851  45.37%
Last 10 Blocks  3.4days  101.9%  151.04%  151.04%  0.9335  66.21%

So N=0.9851 means 1 in 1/(1-N) means 1 in ~67 chance of that or worse happening.
So average about once in about (67*5) 335 blocks would you expect 5 blocks that unlucky or worse.

N=0.9335 is 1 in ~15 or average about once in about (15*10) 150 blocks

[kano]

What was the fee amount?

... zero ...

[kano]

April 2016 Block CDF Competition list:

The 2 winning blocks are:

Block #851 ashg8000 with a CDF of 0.991 (471.929%) at 2016-04-29 17:15:08 UTC

Block #777 Abramov with a CDF of 0.019 (1.945%) at 2016-04-13 10:50:28 UTC

Now to determine the prizes, the first block found on the network in May (UTC) is:
409640 2016-05-01 00:12:11.001 0000000000000000051dd8cd63dcd32373ec53dab1bf7df05714cdefc5a50add
Which has an odd 'd' on the end.

So the prizes for April are:
Abramov wins the Avalon6
ashg8000 wins ~0.125 BTC from the next block we find

I'll contact Abramov (and Avalon) soon with details about getting the prize.

ashg8000 will get his BTC sent to his current payouts address in the next couple of days.

[LASERminer]

Congrats to the winners!
And thank you Kano and Avalon for such contest with fine prize and so geeky rules

PS
Now I wish pool hit some blocks soon so everybody could be the winners!

[kano]

Now for the final May Avalon6 Giveaway competition details:

Details are 'relatively' the same as March and April ... and I'm adding another small incentive.

On each Sunday morning at 00:01 UTC in May (starting the 8th - lol which happens to be mother's day here) the leader at exactly that time, with the lowest CDF, will get my fee from the next 2 blocks found.

Adds up to a total of 4 new prizes totalling a bit over 1BTC for the month so it's not a lot, but anyway
... and it is actually 'possible' for one miner to win all four and one of the 2 final prizes.

March rules were here:
https://bitcointalk.org/index.php?topic=789369.msg14042677#msg14042677

[cavaliersrus]

Now for the final May Avalon6 Giveaway competition details:

Details are 'relatively' the same as March and April ... and I'm adding another small incentive.

On each Sunday morning at 00:01 UTC in May (starting the 8th - lol which happens to be mother's day here) the leader at exactly that time, with the lowest CDF, will get my fee from the next 2 blocks found.

Adds up to a total of 4 new prizes totalling a bit over 1BTC for the month so it's not a lot, but anyway
... and it is actually 'possible' for one miner to win all four and one of the 2 final prizes.

March rules were here:
https://bitcointalk.org/index.php?topic=789369.msg14042677#msg14042677

very cool idea there kano good luck to everybody

[pattim]

This is a rare occurrence with two fat red blocks so close together.

I sort of compare slush's hits to Kano's and they've been tracking pretty well through this blockless time.  They also tracked the blocky weeks a little bit ago.  So I think the big miners are driving the statistics.  What are the chances two similar pools would perform similarly in time?

[firetreeactual]

What was the fee amount?

... zero ...

 

Re Slush...I don't monitor it all the time any more, but when we were consistently hitting 4-5 blks a day, they hadn't hit but one block in several days. It may just be my ageing research methods prof brain, but that doesn't seem like a correlation.

[not.you]

Thought so. So all the large rentals are effectively lowering the earnings due to the larger pool hash rate, while lowering the chance to hit a block.

No it doesn't work like that.  The shares that arrive at the pool are evaluated at that time.  Even though there will have been delay in getting them to the pool they won't be producing an artificial increase in pool hashrate because the pool will either accept or reject them at the moment they arrive at the pool.  What you are really looking at is increased chance for stales and probably wasted hashrate in the form of rejects.  If the miners pointed at NH were pointed directly at kano pool then the work updates and submissions would have less latency but as long as the share is still valid when it arrives at the pool through the more circuitous route through NH, it still has as much chance of producing a block as any other share.  I hit a block on the pool with a rental this past month.  The latency just means that more of those arriving shares will have become rejects (or potentially stales) due to that latency then would have otherwise been the case.  Really the loss here, if there is any, will be on the person who paid the rental.  I believe the shares will be deemed valid by NH and so part of the rental expense, and paid by NH to the actual miner, even though they may be deemed invalid by the kano pool due to latency.

[kano]

Oh and I should have pointed out something relevant about the lowest CDF

To get the highest chance of getting the lowest CDF, you have to, at the latest, start mining when a block is found.

The simplest way to do this is to always be mining when a block is found.
i.e. always be mining, since no one knows when a block will be found

[citronick]

Juvia's crystal ball says... our next block is about within hour from now!

[Crispyato]

Oh and I should have pointed out something relevant about the lowest CDF

To get the highest chance of getting the lowest CDF, you have to, at the latest, start mining when a block is found.

The simplest way to do this is to always be mining when a block is found.
i.e. always be mining, since no one knows when a block will be found

Maybe the contest should just be a lowest cdf contest...