Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 897. (Read 5352420 times)

Look a few post's back.  Kano posted an update on his future plans for the pool.  I think you'll like it.

Just read this https://finance.yahoo.com/news/goldman-sachs-bitcoin-going-test-191000220.html

I am not sure whether it's good or bad. But historically Goldman Sachs's prediction only serves itself, not even its clients. But at least they are interested in trading BTC which means BTC price will fluctuate. It's good for miners though traders will make most easy money as usual  

Coinbase sent out an e-mail today on this...explained their strategy/tactic, and it's not bad, methinks. Same as CEX.IO.

However...the only safe place IMHO is in my Core wallet that's triple-redundant backed up. 

I am a ½ a loaf guy.

So I sold ½ of my coins and kept ½ my coins

most of my coins are now in a 0.14.2 core wallet

I have almost zero coins  in coinbase.

Projections  of what can happen are endless .  But I would rather be on a backed up core wallet for now.

I also would like to know what the outcome could be if keeping coins in Coinbase after Aug 1.
I understand they don't want to do any transaction during that period. But what will happen to the coins in Coinbase in future? What's the difference between keeping in your own wallet and Coinbase?

Hey guys I just saw the advertisement of this hard fork thing on Coinbase and wanted to ask your opinions if I should sell the couple of BTC that I have right now or just put them in my ledger wallet and wait to see what happens?  Thanks!  

Hello Kano,

Have you considered to change the payout to once daily scheme (i.e. pay with the first block after 0:00 UTC)? I know the current scheme works best for traceability and transparency, but they often result in consolidation by individual and large opportunity cost (block space that could be used to process other transactions).

As for trust / transparency, I don't think any meaningful number of miners here would have doubts on your integrity. Otherwise many would not stay here for so long.

Thanks.

Way cool. Thanks also for the clear sitreps, Kano. Makes my PTSD happy-happy... 

We should be at a "whopping" (for us, anyway) 46TH by August...up to 38 for now.

MIne on...

sapperlot with 85TH/s hits his 2nd Kano block with an R4!

This is our 2nd of BLOCK THURSDAY!

Block! by sapperlot
That's our first /NYA/ block but not a BIP91 block yet.

Edit: yep the payout was in that one, I'm reindexing one of the bitcoind at home, after the BIP91 testing, and of course it didn't show it, but of course it is there online

Since I can't stop myself from making some anti-segwit statement regularly ... since the world has gone mad and segwit in the new vogue ...

I'll be updating the main work generator to BIP91 later today - after I sleep - I want to be wide awake to check all is running ok.
I've tested it generating blocks (by a simple 1 line hack of reducing the PoW diff in bitcoin and the same in ckpool - and changing nothing else) - sorry to anyone in the IRC channel with those false block messages by kanobit

I've chosen BIP91 coz the code has the fewest changes and since both Segwit2x and BIP91 are the same thing excluding the 2x lock-in happening much later, and both will work the same until then, it's best for now to run the simpler, straight BIP91 and switch to Segwit2x when necessary, assuming all goes OK for the Segwit2x part.

The pool itself is still running standard transactions, no segwit commitment, but that still works OK with BIP91.
I'll update for the segwit commitment later with the code that was submitted last year to ckpool by someone in core ... though it was broken soon after that ... but appears to be ok now.

So that's the plan, and I'll post when I do the next changes.

I've posted a simple table about /NYA/ and Segwit2x here:
https://bitcointalksearch.org/topic/bitcoin-mining-sources-for-nya-2036632
Anyone with more info they'd like to add - post there and let me know

I keep my Coinbase wallet open for buying and selling bitcoin but I keep nothing in there.  I also mine to a blockchain.info wallet.  When it gets over 1.5 to 2 BTC I consolidate all of it to my KeepKey hardware wallet.  When it's done, I simply unplug the KeepKey and put it in my safe.  I thought about installing core and using that but in the back of my mind I couldn't help thinking that any computer connected to the internet can be hacked...even one running core.  Call me paranoid but that's when I decided to go with a hardware wallet.  Once I unplug it from my computer it cannot be hacked by anyone.  If it gets destroyed by fire or accident, I simply buy another one, use my recovery words, and I'm back in business with all of my coins safe and sound.

Thanks Kano, I've always liked how you keep everyone in the loop

The numbers at the top look OK.

The pool restarted 11:06 UTC so for an hour after that, no one had a '1 hr' hash rate
It shows the 5min value until ckpool thinks you've been mining for 1hr - or it has been running for 1hr

The '«Elapsed' time for the 'Share Rate' is not resetting (since I updated the code last week)
I've added it to my TODO list - but unless I find a show stopper affecting payouts - that I am still processing on the live pool with the new code, and on the backup pool with the old code, so I can compare each one - the bitcoin changes I'm doing have all my priority for now.

I noticed this morning that things look a lil bit different on the pools page.  the 5 min hash rate seems to be gone and only showing the hr hash rate on the top right and on the workers page I notice that this look weird to. . like the Last Block time and the elapsed time seems to be off by a bit.
Right now its saying at the top
Last    Block
Pool:     11h 34m (476607)
Network:     12m 28s (476697)

But the elapsed time for all the workers is saying 100hr 58m 14s  instead of 12m 28s

Well that was a little unexpected ...
I restarted the main backend pool - which only has about a dozen or so connections - since everyone mines to nodes - but alas it couldn't handle passing the sockets over, so everyone will have failed over and back again.

So, it's only a failover and immediate failback - and hash rate is almost back to where it was before - so all ok again.

I've modified the coinbase to now say /NYA/ like (almost) every other pool.
It now says: ".🐈. KanoPool 0p @P /NYA/ "

The bitcoind is still running my modified 0.13.1 but will be upgraded to my modified 0.14.2 soon - but that won't cause any failovers.
I'll post again about that when I do it.

The reward per block should be reasonably consistent - well consistent with your hash rate vs the pool hash rate - once you've been mining for 5Nd.
The reward per day is random.

Hello everyone. I have been mining at Kano for the last 3 days. I got rewards from day one itself. But as of yesterday 19-07-2017 I got rewarded less than half of what i have been getting. I have check all my miner and its qorking as usual. Did I miss anything?

I put my coins in a core wallet .

I have a tiny bit in coin base.
I have a some in bittrex

I also mine to a blockchain.info wallet

Well, it's an important subject nonetheless.

FWIW...I'm not even a Coinbase customer anymore, but got a detailed e-mail from them as to their actions, and why, and what to expect.