Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 974. (Read 5352429 times)
May 10, 2017, 08:10:52 PM
Block by mikese! This is our 1st of BLOCK Thursday!
May 10, 2017, 08:03:40 PM
Our ISP says that a major fiber trunk was cut in the Detroit area causing the outage to their service. Um, no backbone backup to cover this and route around the break???
Ja. I powered down all the Bitmain gear because being Bitmain they were all still running pretty toasty.
The Avalons however - they still report as alive, just throttled down to a standby mode. As in cool air exiting them so I left them alive. Nice touch there and hopefully once the RiPi can talk to the 'net hopefully they will automajickally restart.
Ja. I powered down all the Bitmain gear because being Bitmain they were all still running pretty toasty.
The Avalons however - they still report as alive, just throttled down to a standby mode. As in cool air exiting them so I left them alive. Nice touch there and hopefully once the RiPi can talk to the 'net hopefully they will automajickally restart.
May 10, 2017, 07:56:59 PM
Grumble grumble....
The internet/phones at work have been down since 10:30 this morning so main farm is off line
Was holding a steady 233THs, just looked and still just the 37.4 here at home reporting....
Owwee
The internet/phones at work have been down since 10:30 this morning so main farm is off line
Was holding a steady 233THs, just looked and still just the 37.4 here at home reporting....Owwee
Yeah, that's a slight drop in hash rate!
That's a very good reason to grumble. I would make it a large GRUMBLE with caps, underlined, and bold!
I hate that helpless feeling.
Hope you get it back online soon.
Good luck with it.
May 10, 2017, 07:52:27 PM
PG&E started summer rates and the on peak rate is $0.55/kWh. So obviously I have to turn off miners. I wonder whether it will affect mining rewards if miners run 12 hours per day. Thanks!
Are you meaning $0.55 cents per kWh? As in half of a dollar plus 5 cents? That's crazy high! I can certainly see why you have to turn them off. What is the normal/off peak rate?
It will certainly effect your rewards. I suppose you could take what your "average" reward amount is for a given time and divide by two. AFAIK, that will probably be the outcome averaged out over time.
Good luck!
May 10, 2017, 07:51:53 PM
Grumble grumble....
The internet/phones at work have been down since 10:30 this morning so main farm is off line Was holding a steady 233THs, just looked and still just the 37.4 here at home reporting....
Narf
The internet/phones at work have been down since 10:30 this morning so main farm is off line
Was holding a steady 233THs, just looked and still just the 37.4 here at home reporting....Narf
May 10, 2017, 07:38:18 PM
PG&E started summer rates and the on peak rate is $0.55/kWh. So obviously I have to turn off miners. I wonder whether it will affect mining rewards if miners run 12 hours per day. Thanks!
May 10, 2017, 07:32:03 PM
Thanks for your input. I did use the low fee because I didn't care how long it would take and I was expecting the BTC would go high but I didn't expect it might be lost. I think the fee is pretty low comparing to what you quoted 0.00218603 BTC per /kb
Date sent: 7 May 2017, 2:49:32 pm
Input 0.05295024 BTC
Output 0.05136317 BTC
Sigops 112
Fees 0.00158707 BTC
Fees Rate (BTC / KB) 0.00057880 BTC
406 Confirmations
I send coins of varying amounts all the time from my Core wallet to my Coinbase account. Coinbase only requires 3 confirmation before it is considered "confirmed".
The only reason I can think of that you are having problems is that it was sent with too low of a transaction fee.
I don't know anything about BTC.com or how they operate, but I have never had any difficulties sending coins to coinbase. On the one or two occasions that I have sent the coins from Core to Coinbase with a low fee (I didn't care how fast it arrived), it was available in Coinbase (after 3 confirmations) within about 12 hours.
I would check your fee's and see if it was low.
From what I recall from earlier today there were MANY transactions in a backlog.
Good luck!
EDIT: I realized this occurred over a week ago, but there are currently 124,990 unconfirmed transactions in the mempool and the optimal fee is 0.00218603 BTC per /kb. ( I don't trust the optimal fee calculators. I just use my common sense depending on how fast I want the transaction to become available.)
Date sent: 7 May 2017, 2:49:32 pm
Input 0.05295024 BTC
Output 0.05136317 BTC
Sigops 112
Fees 0.00158707 BTC
Fees Rate (BTC / KB) 0.00057880 BTC
406 Confirmations
I moved .05 BTC from BTC.com to Coinbase on May 3. It was pending on Coinbase for 2 days and then it's gone. BTC.com sent again (automatically) on May 7. It has 283 confirmation now but it still does not show at Coinbase. Does anyone know whether the .05 BTC will eventually arrive at Coinbase? Thanks!
I send coins of varying amounts all the time from my Core wallet to my Coinbase account. Coinbase only requires 3 confirmation before it is considered "confirmed".
The only reason I can think of that you are having problems is that it was sent with too low of a transaction fee.
I don't know anything about BTC.com or how they operate, but I have never had any difficulties sending coins to coinbase. On the one or two occasions that I have sent the coins from Core to Coinbase with a low fee (I didn't care how fast it arrived), it was available in Coinbase (after 3 confirmations) within about 12 hours.
I would check your fee's and see if it was low.
From what I recall from earlier today there were MANY transactions in a backlog.
Good luck!
EDIT: I realized this occurred over a week ago, but there are currently 124,990 unconfirmed transactions in the mempool and the optimal fee is 0.00218603 BTC per /kb. ( I don't trust the optimal fee calculators. I just use my common sense depending on how fast I want the transaction to become available.)
May 10, 2017, 04:50:26 PM
Block by canaan! This is our 2nd of BLOCK WEDNESDAY! 
A7v2 and 2 payouts
Edit: it's an orphan race ...
Edit2: we won .. and beat FUPool
Edit3: lol OK it wasn't an orphan race - blocktrail is screwed up at the moment
(we did of course get the block)You ain't kidding! Blocktrail shows the last block was found 1 hour and 5 mins ago.
May 10, 2017, 04:33:07 PM
I definitely think we should add another block to today's set. Let's DO IT!!!
COMEONBLOCKSSSSSSSSSSSSSSSSSSSSSSSSSSSS!!!!!! SnapCracklePop!!!
COMEONBLOCKSSSSSSSSSSSSSSSSSSSSSSSSSSSS!!!!!! SnapCracklePop!!!
May 10, 2017, 03:58:56 PM
I moved .05 BTC from BTC.com to Coinbase on May 3. It was pending on Coinbase for 2 days and then it's gone. BTC.com sent again (automatically) on May 7. It has 283 confirmation now but it still does not show at Coinbase. Does anyone know whether the .05 BTC will eventually arrive at Coinbase? Thanks!
I send coins of varying amounts all the time from my Core wallet to my Coinbase account. Coinbase only requires 3 confirmation before it is considered "confirmed".
The only reason I can think of that you are having problems is that it was sent with too low of a transaction fee.
I don't know anything about BTC.com or how they operate, but I have never had any difficulties sending coins to coinbase. On the one or two occasions that I have sent the coins from Core to Coinbase with a low fee (I didn't care how fast it arrived), it was available in Coinbase (after 3 confirmations) within about 12 hours.
I would check your fee's and see if it was low.
From what I recall from earlier today there were MANY transactions in a backlog.
Good luck!
EDIT: I realized this occurred over a week ago, but there are currently 124,990 unconfirmed transactions in the mempool and the optimal fee is 0.00218603 BTC per /kb. ( I don't trust the optimal fee calculators. I just use my common sense depending on how fast I want the transaction to become available.)
May 10, 2017, 02:18:52 PM
Block by canaan! This is our 2nd of BLOCK WEDNESDAY!
A7v2 and 2 payouts
Edit: it's an orphan race ...
Edit2: we won .. and beat FUPool
Edit3: lol OK it wasn't an orphan race - blocktrail is screwed up at the moment
(we did of course get the block) 
May 10, 2017, 02:15:40 PM
May 10, 2017, 02:13:58 PM
Block by canaan! This is our 2nd of BLOCK WEDNESDAY!
May 10, 2017, 12:31:43 PM
ok thanks. my grandma just picked up my second s7 can't wait to get off of school to set it up.
Yep as they both stated above your post can't wait to get off of school to set it up.Specifically:
Separate worker names means you see them separately on the Workers->Workers page and 'can' see them separately on the Workers->Shift Graph
The Workers->Management page is pretty much pointless and best ignored unless you have very old miners that have problems with difficulty
(or use a proxy and have LOTS of miners)
May 10, 2017, 12:30:34 PM
ok thanks. my grandma just picked up my second s7 can't wait to get off of school to set it up.
well done grandma can't wait to get off of school to set it up. May 10, 2017, 12:26:14 PM
ok thanks. my grandma just picked up my second s7 can't wait to get off of school to set it up.
can't wait to get off of school to set it up. May 10, 2017, 09:06:48 AM
Noob question, but when i set up another miner do i use the same worker name or a different one if i want to have both of my miners mining on kano?
You can do it both ways, you can set up MyAccount.MyWorkers and monitor them separately on your end, or you can set up MyAccount.MyWorker1and MyAccount.MyWorker2 and monitor them separately at the pool site.I imagine, that's not really the answer you were looking for, but it's all a matter of preference.
May 10, 2017, 09:05:50 AM
Noob question, but when i set up another miner do i use the same worker name or a different one if i want to have both of my miners mining on kano?
You would use the same username, with different worker names appended i.e.: Username.worker1 and Username.worker2 etc... Underscore works also (Username_worker3) May 10, 2017, 08:55:49 AM
Noob question, but when i set up another miner do i use the same worker name or a different one if i want to have both of my miners mining on kano?
Jump to: