Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 1817. (Read 5352367 times)
January 17, 2016, 07:44:24 PM
Yeah but you are pretty lucky here, you have found 7.
January 17, 2016, 07:40:22 PM
Aww man! This starts AFTER I hit a block? 
January 17, 2016, 07:27:00 PM
What's the contest? I missed it.
Go to the first post.
January 17, 2016, 07:20:58 PM
Nice, 4 blocks in 24h 
all three of my s7`s went from 4.7THs to 2THs at pool just seconds after the last block was found, but when I checked the rigs they were was mining at 4.7,
anyway no big deal as it all went back to normal over the next 10-15 minutes, another DDOS or something else?
Congartatulations to all and respect to Kano&Ck
all three of my s7`s went from 4.7THs to 2THs at pool just seconds after the last block was found, but when I checked the rigs they were was mining at 4.7,
anyway no big deal as it all went back to normal over the next 10-15 minutes, another DDOS or something else?
Congartatulations to all and respect to Kano&Ck
January 17, 2016, 07:19:08 PM
What's the contest? I missed it.
January 17, 2016, 07:18:23 PM
Avalon6 contest starts now!
Hey Kano, you need to add another rule to the contest.
Why? I suspect there's some users with a lot of hash power and they are making other accounts to split their hashpower.
Look at the workers. Users with almost the same name
And i think 250TH is too high.
If you are somebody with 249TH you have enough money to buy an Avalon in 2-3 days.
IMHO
I didn't say anywhere that he can't do that if he wanted to.
He's had 2 accounts for ages since he joined anyway.
That's not something new.
The point of the upper limit is so that someone with 500THs, who doesn't really care about winning one miner, wont win one.
If they do care, they can of course make a worker with 50TH if they want.
The lower limit is coz I don't want to attract hundreds of tiny miners to the pool.
The pool hashrate vs workers is very good. Lots of tiny miners makes that not as good.
He's had 2 accounts for ages since he joined anyway.
That's not something new.
The point of the upper limit is so that someone with 500THs, who doesn't really care about winning one miner, wont win one.
If they do care, they can of course make a worker with 50TH if they want.
The lower limit is coz I don't want to attract hundreds of tiny miners to the pool.
The pool hashrate vs workers is very good. Lots of tiny miners makes that not as good.
January 17, 2016, 07:14:49 PM
Avalon6 contest starts now!
Hey Kano, you need to add another rule to the contest.
Why? I suspect there's some users with a lot of hash power and they are making other accounts to split their hashpower.
Look at the workers. Users with almost the same name
And i think 250TH is too high.
If you are somebody with 249TH you have enough money to buy an Avalon in 2-3 days.
IMHO
January 17, 2016, 07:09:54 PM
Avalon6 contest starts now!
--
Edit: 5 minutes and still no blocks?
--
Edit: 5 minutes and still no blocks?
Sorry, forgot to flip the FBN (Find Block Now) Bit.
January 17, 2016, 07:05:10 PM
woooooooooo good luck everyone, an avalon 6 is a sweeeeeet prize. Just for the reduced noise factor, you can put it almost anywhere in your house. Plus what is it, like 1000w? Doesnt strain your electric system for a 15a breaker circuit.
January 17, 2016, 07:00:02 PM
Avalon6 contest starts now!
--
Edit: 5 minutes and still no blocks?
--
Edit: 5 minutes and still no blocks?
January 17, 2016, 06:30:02 PM
Avalon6 contest starts in 30min 
Edit: I added one change to the first post, that I forgot to put in there -ck and I can't win.
Edit: I added one change to the first post, that I forgot to put in there
-ck and I can't win. 
January 17, 2016, 06:15:29 PM
thedreamer hits another block for Kano...number 7?
January 17, 2016, 05:57:31 PM
green getting brighter ! yum
January 17, 2016, 05:45:29 PM
Cool stuff. A nice quick block feels good.
January 17, 2016, 05:38:41 PM
Good info, Kano & CK.
New block. Good thing.
Ordered another 500g of that frankincense...
New block. Good thing.
Ordered another 500g of that frankincense...
January 17, 2016, 05:19:37 PM
Just an update on what's been going on behind the scenes with the remote mining nodes.
I've been working on getting the remote nodes to submit all blocks found by the pool simultaneously around the world as quickly as possible to minimise the risk of orphans in addition to decreasing the mining latency for miners and am finally happy with the performance. This last block was found on the main pool and submitted to its local bitcoind in LasVegas USA and then it was also submitted in Dallas TX, SG, DE, and RU all within only 90ms. Of course in addition we are submitting our blocks to Matt's relay node but this is helping propagate our found blocks across the network faster than the relay can, and we are now not sure of the future of the relay node.
I've been working on getting the remote nodes to submit all blocks found by the pool simultaneously around the world as quickly as possible to minimise the risk of orphans in addition to decreasing the mining latency for miners and am finally happy with the performance. This last block was found on the main pool and submitted to its local bitcoind in LasVegas USA and then it was also submitted in Dallas TX, SG, DE, and RU all within only 90ms. Of course in addition we are submitting our blocks to Matt's relay node but this is helping propagate our found blocks across the network faster than the relay can, and we are now not sure of the future of the relay node.
January 17, 2016, 04:53:55 PM
Just got confirmation from -ck, it will be in the pool section. I will post a link here when I have it up.
January 17, 2016, 04:53:36 PM
Hi All
Under worker tab -worker Name-Total 1(3 Miners) ? Where this 3 miners figure coming from .
Thanks
Under worker tab -worker Name-Total 1(3 Miners) ? Where this 3 miners figure coming from .
Thanks
Any one have any idea ?
In git I have it disabled coz I was expecting problems with ckdb displaying it.
I enabled it for testing on the main pool and saw that it wasn't originally showing anything at all due to a problem in ckdb.
However, some new or re-connections can add a count in there.
If everyone is taking too much notice of it I'll just disable it until it's working properly
I didn't announce it coz ... yeah I wasn't sure if the main pool would show it properly without restarting everything ... and didn't want to do a restart just for that number.
Ignore it until I mention that it is there
January 17, 2016, 04:21:09 PM
In pool section?
Theres some other guy with a API for antpool, he has it in pool.
Theres some other guy with a API for antpool, he has it in pool.
I like it here, all things related to Kano in one spot. Just my 2 cents.
Thanks, please PM me, I don't want to fill this thread with this "off-topic" content.
Pool section maybe? -ck?
People are having trouble finding my answers to questions in this thread that is why I would like to start a new one.
The first time I mentioned CKPoolMonitor was on page 47:
https://bitcointalksearch.org/topic/m.10087361
Now we are on 436, that is alot to filter through.
ZACHM - I don't think it really matters what section you post your thread as we can always referred users with questions for the tool toward that thread. But I agree, it would be nice, to have a 1 spot thread to all the features / updates /questions for your tool. You can always answer quick questions on here and if they need more info, they can follow the other thread. Love the work you're doing, please keep up the good work.
January 17, 2016, 04:01:03 PM
I asked SPECIFIC QUESTIONS in relation to CKPool, like: "How does CKPool know the difference between Core and Classic." I asked this because If I'm mining here and you guys are hell bent on running core till bitcoin is dead, would my mining on your Core (1MB) Pool be comparable with a Bitcoin Classic (2MB) wallet. Does the pool payout know what kind of wallet I use by the wallet address or some other way?
I also asked if there is anything special I would need to do to the Classic Wallet or to the firmware of my miners . I'm by far not a coder, I have not even attempted to decypher any of the coding for bitcoin, pools, miner firmware or wallets, so I have absolutely no clue if there are compatibility issues or anything else that would throw a monkey wrench into the spokes..... I don't want mine on CKPool and not get paid because I'm running a non-compatible wallet.
I just have no clue, as I suspect others are kinda in the dim light of this issue.
Its not MY political agenda, its the pure FACT ( from what I've been reading in a lot of articles) that the 1MB block is running out of space. YOU - I'm sorry to say - injected politics by censoring (deleted) my questions forcing this confrontation. I'm not looking for confrontation, I'm looking for answers from pool management and users to the legitimate questions of compatibility and get an idea WHEN I should switch over.
ckpool is the name of the code this pool runs by the way. Hence my misunderstanding that you intended to talk about this pool but thought you were asking questions about code instead. In short the ckpool software doesn't care and can work with anything. Same with kano.is I also asked if there is anything special I would need to do to the Classic Wallet or to the firmware of my miners . I'm by far not a coder, I have not even attempted to decypher any of the coding for bitcoin, pools, miner firmware or wallets, so I have absolutely no clue if there are compatibility issues or anything else that would throw a monkey wrench into the spokes..... I don't want mine on CKPool and not get paid because I'm running a non-compatible wallet.
I just have no clue, as I suspect others are kinda in the dim light of this issue.
Its not MY political agenda, its the pure FACT ( from what I've been reading in a lot of articles) that the 1MB block is running out of space. YOU - I'm sorry to say - injected politics by censoring (deleted) my questions forcing this confrontation. I'm not looking for confrontation, I'm looking for answers from pool management and users to the legitimate questions of compatibility and get an idea WHEN I should switch over.
Jump to: