|
firetreeactual
Legendary
Offline
Activity: 952
Merit: 1003
|
|
May 08, 2016, 09:58:59 PM |
|
well as of last monday due to heat index and humidity in my state i have pulled the plug on my 2xS5+s and the sp30 SP20 is the only option for me with easy scheduling (off mid day due to heat in the office) and manual fan speed control (to make it quiet), which equals to generate quiet 1TH/s at minimum fan speed without overheating. ...and I thought I was the only one who had to deal with that stuff...ambient temp, air circulation, heat generated, etc. at least for a small residential or office space...in my case, in the central Pacific tropics, in yours the US Southeast (if I remember correctly). Obviously (from reading a number of posts over the past few months) I'm not the only one. Lots of challenges for some of us...and periodic challenges (ie., weathering the occasional red week) for others. Mine on...
|
To infinity and beyond...on two 741s and one of only 3...nope, make that 4...full nodes in Hawaii...on <30A. (I have other gear on the Hoth ice planet)
|
|
|
chudm
Newbie
Offline
Activity: 59
Merit: 0
|
|
May 08, 2016, 10:35:32 PM |
|
Guys i live in venezuela, and trust me, keeping the miners at a 60-65 Celsius Degrees is no easy task i have severals s7 running right now at 66 degrees, but im modifying the room next week so im hoping to get around 57-60 degrees!
|
|
|
|
ss200
Full Member
Offline
Activity: 269
Merit: 100
The Protocol for the Audience Economy
|
|
May 08, 2016, 11:19:26 PM |
|
Why block 410 747 and 410 756 unit are not included in the payment? on block location momemt they had 101+ confirmation sorry for my english, it's Google Translator
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4522
Merit: 1844
Linux since 1997 RedHat 4
|
|
May 08, 2016, 11:48:16 PM |
|
Why block 410 747 and 410 756 unit are not included in the payment? on block location momemt they had 101+ confirmation sorry for my english, it's Google Translator
Coz we haven't found a block since the payments were sent out. https://bitcointalk.org/index.php?topic=789369.msg14727294#msg14727294410747 f7c79c04cffaea409a71ceb779bd54cdea0fb7981c2025df9e0113d6d3e6c453 410756 62636002fb3cd279e92841fa6178c1bd1ab53e96dde41cc5531d97581d838561
|
|
|
|
clgrissom3
Legendary
Offline
Activity: 1722
Merit: 1032
Carl, aka Sonny :)
|
|
May 08, 2016, 11:55:02 PM |
|
Block by dilmurod with 907.10GHs! I didn't think that was even possible! Way to go and welcome to the Acclaim Board with your first kano block! EDIT: This confirmed the payouts for blocks 410747 and 410756!
|
|
|
|
hoosier_13
Member
Offline
Activity: 62
Merit: 10
|
|
May 08, 2016, 11:59:49 PM |
|
That's more like it - let's rally this week
|
Bitrated user: TICH13.
|
|
|
philipma1957
Legendary
Online
Activity: 4158
Merit: 8036
'The right to privacy matters'
|
|
May 09, 2016, 12:00:32 AM |
|
To clarify why Kano makes us wait to hit a block for payments to clear. We had more then 250 miners so a payment has more then 250 entires and takes about 45,000 bytes.
Kano pays a .002 fee to send the block payment. If you want real fast confirm on a 45,000 byte transaction you need .01 not .002.
So we save at least .008 in fees on every payment made.
To top it off almost every fee he pays .002 x 850 = 1.7 coins ends up in the fees of the blocks we hit.
So we saved at least 6.8 coins. And we added about 1.7 back to our blocks. That is the up side. A gain of 8.5 btc for the pool. The down side is payments slow up just a bit.
I did a few estimates the one of 6.8 btc in fees not spent and 1.7 btc in fees added back is the conservative estimate.
And we just hit a block so payments will confirm now.
|
|
|
|
Newko
|
|
May 09, 2016, 12:00:43 AM |
|
Block by dilmurod with 907.10GHs! I didn't think that was even possible! Way to go and welcome to the Acclaim Board with your first kano block! That's 5 blocks today! now we're cooking with gas!
|
|
|
|
philipma1957
Legendary
Online
Activity: 4158
Merit: 8036
'The right to privacy matters'
|
|
May 09, 2016, 12:02:53 AM |
|
We shall pull out of the red soon two days of whaling away and back to the green
|
|
|
|
wolfen
|
|
May 09, 2016, 12:06:38 AM |
|
Five blocks today
|
For those about to block we salute you! AC->BTC
|
|
|
sorry2xs
Legendary
Offline
Activity: 924
Merit: 1000
Dark Passenger Bitcoin miner 2013,Bitcoin node
|
|
May 09, 2016, 12:08:06 AM |
|
i think is more nitro
|
Please tip the Node 1MPWKB23NsZsXHANnFwVAWT86mL24fqAjF; KO4UX THAT NO GOOD DO GOODER BAT!!!
|
|
|
kano (OP)
Legendary
Offline
Activity: 4522
Merit: 1844
Linux since 1997 RedHat 4
|
|
May 09, 2016, 12:37:20 AM Last edit: May 09, 2016, 02:47:31 AM by kano |
|
Anyone wondering about the bitcoind state on the pool. I've completed switching them all over to standard 0.12.1 now. Edit: oh that comment doesn't read right ... I mean standard in terms of core code, but with -ck's performance enhancements of course
|
|
|
|
citronick
Legendary
Offline
Activity: 1834
Merit: 1080
---- winter*juvia -----
|
|
May 09, 2016, 02:12:51 AM |
|
Finally got my rigs moved over to new man-cave, after being "evicted" from home. Business as usual now at kano.is and started main gear and rental cycles. I was caught halfway during my man-cave move, in our "red period", good and bad I guess .... fact of life in mining. Have faith in the pool - it will have ups and downs, but longterm overall we are 106% - which is still fantastic. I believe, we will be in the greens in no time.... there is always sunshine after rain. Even a small 900GHs miner got a block today and it came in right after the pool's top miner 12MTh... that's the kano pool that we know! Orphans and close calls will always be there - sometime we win those and sometimes not - that's normal lifecycle in mining. Meanwhile, my new man-cave is slowly coming back to life and my wifey is happy with the new found extra space at home.... in the end, my wife won this "orphan" race on the eviction notice
|
If I provided you good and useful info or just a smile to your day, consider sending me merit points to further validate this Bitcointalk account ~ useful for future account recovery...
|
|
|
citricut
Newbie
Offline
Activity: 22
Merit: 0
|
|
May 09, 2016, 06:06:40 AM |
|
Now that we are back at 30PH, could there be a relation between end of rentals and blocks coming through again? Like there is between the disappearance of the pirates and the global warming...
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4522
Merit: 1844
Linux since 1997 RedHat 4
|
|
May 09, 2016, 08:32:45 AM |
|
Someone was trying to do a DNS UDP attack on the pool over some of the last half hour and continuing in very small amounts ... Fortunately that doesn't work It seems to come and go, but so far all low enough to cause zero problems. Just thought I'd mention it in case something does happen in the near future and people can't get at the pool.
|
|
|
|
aurel57
Legendary
Offline
Activity: 1176
Merit: 1000
|
|
May 09, 2016, 09:11:26 AM |
|
To clarify why Kano makes us wait to hit a block for payments to clear. We had more then 250 miners so a payment has more then 250 entires and takes about 45,000 bytes.
Kano pays a .002 fee to send the block payment. If you want real fast confirm on a 45,000 byte transaction you need .01 not .002.
So we save at least .008 in fees on every payment made.
To top it off almost every fee he pays .002 x 850 = 1.7 coins ends up in the fees of the blocks we hit.
So we saved at least 6.8 coins. And we added about 1.7 back to our blocks. That is the up side. A gain of 8.5 btc for the pool. The down side is payments slow up just a bit.
I did a few estimates the one of 6.8 btc in fees not spent and 1.7 btc in fees added back is the conservative estimate.
And we just hit a block so payments will confirm now.
thanks phil for explaining it. (i was not worried but did wonder how that worked also)
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4522
Merit: 1844
Linux since 1997 RedHat 4
|
|
May 09, 2016, 09:26:40 AM |
|
Well there's some minor confusion in that, that I don't quite follow his wording So I'll repeat stuff I've said before and explain it in more detail. I the past, I paid all the transaction fees from my mining. No one else had to pay for any txn fees. Firstly, I used to put 0.002 fee on each transaction - about $140 a month - no big deal. It seems that bitcoin wants about 0.02 fee or there abouts. That would be about $1400 a month ... so yeah too much in my opinion. Our job as a pool is to confirm transactions. Really it's now pointless using a 0.002 fee since it often doesn't get confirmed by any other pools for hours. Recently I had my miner off by mistake and when I got to doing the payout my miner total was less than 0.002 So I changed the payout processing to allow me to set a zero fee - i.e. don't take anything from my mining. I also sorted it out to guarantee that I could ensure the zero fee pool payout transaction would be in our block work. I've now set the payouts to always be zero fee. Side effect of it all is the payout will (almost always) only be confirmed by the next block we find after I send the payout. Current hash rate (30PH) expects on average 3.3 blocks a day, so payouts should be rare to take more than a day.
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4522
Merit: 1844
Linux since 1997 RedHat 4
|
|
May 09, 2016, 09:36:33 AM |
|
... and while I was typing the above ...
There was a short network drop out to the pool. It lasted less than 30 seconds so it seemed that few if anyone was actually disconnected. The hash rate showed 20PH as soon as the network fixed itself (probably due to not seeing any shares for a few seconds) and then shot straight back up to 30PH - meaning that the delayed shares suddenly arrived.
Thus it would appear few if any miners were disconnected by it or lost any shares.
|
|
|
|
rkinnin
|
|
May 09, 2016, 11:38:43 AM |
|
Well there's some minor confusion in that, that I don't quite follow his wording So I'll repeat stuff I've said before and explain it in more detail. I the past, I paid all the transaction fees from my mining. No one else had to pay for any txn fees. Firstly, I used to put 0.002 fee on each transaction - about $140 a month - no big deal. It seems that bitcoin wants about 0.02 fee or there abouts. That would be about $1400 a month ... so yeah too much in my opinion. Our job as a pool is to confirm transactions. Really it's now pointless using a 0.002 fee since it often doesn't get confirmed by any other pools for hours. Recently I had my miner off by mistake and when I got to doing the payout my miner total was less than 0.002 So I changed the payout processing to allow me to set a zero fee - i.e. don't take anything from my mining. I also sorted it out to guarantee that I could ensure the zero fee pool payout transaction would be in our block work. I've now set the payouts to always be zero fee. Side effect of it all is the payout will (almost always) only be confirmed by the next block we find after I send the payout. Current hash rate (30PH) expects on average 3.3 blocks a day, so payouts should be rare to take more than a day. Zero Fee! Congrats on the move.....and thank you very much. .....especially on the payout schedule too. Just curious....how much do you actually mine yourself?
|
|
|
|
|