Bitcoin Forum
December 16, 2017, 04:53:38 PM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 [1590]
  Print  
Author Topic: [25+PH] KanoPool kano.is NO FEE TIL 2018 PPLNS US,DE,SG,JP,NL,NYA 🐈  (Read 5062739 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
kano
Legendary
*
Offline Offline

Activity: 2296


Linux since 1997 RedHat 4


View Profile
Today at 03:25:19 AM
 #31781

...
Cool beans kano.  looking at the time pool 10 detected a new block  "[2017-12-15 18:31:22.953] Stratum from pool 10 detected new block at height 499476"   with the time that slush pool finised the block 499476 and got it relayed in was at 18:31:17  so its looking like it only tool a few millseconds less then 6 seconds for the pool to be geting cracking on new work. from the time slush got the block before that relayed in.   Thats seem pretty darn quick.      but if I happen to be looking at the right moments again and notice any big discrepancies in the time displayed on the top of the kanopool page I will try to take note of how much the time is off if I happen to notice again.    
No, 6 seconds is WAY too slow.

But I suspect you are misreading that time.
The time in the block is not when it was found.
Block 499476 has a date stamp of "2017-12-15 18:31:17" which is the (somewhat random) time put in the block header, not the time the block was found, and certainly not the time that pool processed the block.

If it was, then that would mean that slush is slow to distribute their blocks.

All our node's bitcoinds processed the block during the second of "2017-12-15 18:31:22"





That very well could be that slush is slow. They have been going threw some sort of DDoS attack for about the last week or so more then even normal.  and there page some times wont refresh or will pop up with a Cloudflare notice quite a lot.  

But for what is worth they hit another block about 20 mins ago and I happened to notice it when they were about 12 mins in to the next block and kanopool info was showing it being 2 mins in to the next block and so I put the 2 pages next to each other and hit refresh on kano and then I took a screen shot for you so you can see what I mean.   and got it just in the nick of time because only a few seconds later someone some were found that block and then it was on to the next one when I refreshed the kano page again.

http://i65.tinypic.com/2lwt834.jpg
Well I don't know what is causing that for you - but again you'd need to check the UTC time in the bottom left and make sure your ISP or connection isn't caching old data.

We found 498508 at 2017‑12‑10 03:39:29
Add 143hrs and 14m gives 2017‑12‑16 02:53:29 - so the time you got that page would be around 02:53:29 give or take a minute due to the "143hrs and 14m" rounding.

That's 3 mins and 20 seconds after block 409532 plus or minus a minute.
Network there says 2:51 since last block which fits into 3:20 + or - a minute.

So your web page matches what you would expect to see at about 2017‑12‑16 02:53:29 (plus or minus a minute)

Pool: https://kano.is Here on Bitcointalk: Forum BTC: 1KanoPb8cKYqNrswjaA8cRDk4FAS9eDMLU
FreeNode IRC: irc.freenode.net channel #kano.is Majority developer of the ckpool code
Help keep Bitcoin secure by mining on pools with full block verification on all blocks - and NO empty blocks!
1513443218
Hero Member
*
Offline Offline

Posts: 1513443218

View Profile Personal Message (Offline)

Ignore
1513443218
Reply with quote  #2

1513443218
Report to moderator
1513443218
Hero Member
*
Offline Offline

Posts: 1513443218

View Profile Personal Message (Offline)

Ignore
1513443218
Reply with quote  #2

1513443218
Report to moderator
1513443218
Hero Member
*
Offline Offline

Posts: 1513443218

View Profile Personal Message (Offline)

Ignore
1513443218
Reply with quote  #2

1513443218
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
smutboy420
Full Member
***
Offline Offline

Activity: 226


View Profile
Today at 04:07:19 AM
 #31782

UTC time in the bottom left seems all good when I refresh kano page. and then click up my clock your time shown is only about 1-2 seconds from the time on my clock in windows which is about how long it takes me to bring my clock back up to see my clock.

But whatever the difference is.  That was causeing slush to show it was 12:16 in to block 449532  and kanopool showing 2m 51s in to 449532   was what seemed pretty far off with it only takeing a few seconds to hit the screen capture button to take the screen shot.


 Tho you know all the under the hood and in and out or all this pool stuff so if its all good from your view thats good enough for me.  esp being I know you actually looked and didn't just do what some pool ops would do if they didn't even understand they even had a problem if anyone was pointing out something that was actually wrong.  or take days or even to weeks to reply back to a support ticket.  You are a true Johny on the spot when it comes to support or ?s on the forum. 

   
smutboy420
Full Member
***
Offline Offline

Activity: 226


View Profile
Today at 04:16:43 AM
 #31783

ha ha now just seen another block was started on by slush and this time the times are nuts on almost to the second

With you showing  Network: 4m 40s (499538)  when I hit refresh and slush was showing they were 4m 41s in to block 499538   and being it takes about .5 to 1 second or so to refresh the full page that would be pretty close to exact same time sync.   Grin

rifleman74
Member
**
Offline Offline

Activity: 70


View Profile
Today at 05:41:37 AM
 #31784

Alright, enough's enough.  Time for a block.   Luck luck luck
1manshow
Newbie
*
Offline Offline

Activity: 12


View Profile
Today at 06:20:04 AM
 #31785

Can someone let me know how do I set different location pool information in secondary and tertiary pool information on Antminer S9? All I can find on main page of Kano website is stratum+tcp://stratum.kano.is:3333 and port variations. Or you people set any other pool information in those second and third pool info? Sorry for my bad English.
xuy
Member
**
Offline Offline

Activity: 86


View Profile
Today at 06:34:50 AM
 #31786

Does anyone know how much BTC for each THs/Day?
Waztim
Jr. Member
*
Offline Offline

Activity: 56


View Profile
Today at 07:20:49 AM
 #31787

Does anyone know how much BTC for each THs/Day?

Go here, http://tradebtc.net/bitcalc.php

Edit: To reach these expected payouts, you must reach 5ND. Hope this helps and welcome to the Best Bitcoin Pool, KANO POOL!!
kano
Legendary
*
Offline Offline

Activity: 2296


Linux since 1997 RedHat 4


View Profile
Today at 07:40:50 AM
 #31788

Can someone let me know how do I set different location pool information in secondary and tertiary pool information on Antminer S9? All I can find on main page of Kano website is stratum+tcp://stratum.kano.is:3333 and port variations. Or you people set any other pool information in those second and third pool info? Sorry for my bad English.
Ports don't matter unless you are having trouble with port 3333 due to your miners.
Sometimes internet providers block ports and can cause problems like that but I doubt they'd block 3333
However, some people find that only certain ports work and everything else is blocked, so you can use the other ports in that case, and usually 80 should be fine.

Anyway, your setup would depend on where you are, to decide which should be first.

Normally you'd use stratum+tcp://stratum.kano.is:3333 first if you are in the USA on the west coast of central USA
If you are on the east cost or north east canada, then you'd use stratum+tcp://nya.kano.is:3333

If you are in Europe you'd use either stratum+tcp://de.kano.is:3333 or stratum+tcp://nl.kano.is:3333

From the asia area you'd use either stratum+tcp://jp.kano.is:3333 or stratum+tcp://sg.kano.is:3333

Second would be the next nearest node, or if you use stratum+tcp://stratum.kano.is:3333 first then 2nd would be stratum+tcp://nya.kano.is:3333

For third, I'd suggest you use a PPS pool as I mentioned recently.
https://bitcointalk.org/index.php?topic=789369.msg26349919#msg26349919

-------

An aside that some may not know:

If you have a petahash or more on west USA, I can setup so you can access a node there that is white listed for large miners only Smiley

Of course anyone with more than a petahash always mining at the pool, I'll try setup a node near them if they want, of course that depends on where they are, but I don't mind setting up a white listed node for anyone with that or more hash rate.
These nodes only allow data from the pool, from me and of course the miners who are white listed, they completely ignore other data.
(Edit: oh they also of course have a bitcoin node running on them Tongue)

PM me if you want that and have more than a petahash that will stay on the pool.

-------

Edit: also another thing that few may know about, that I've had on the pool for years now, is that large miners can divide their payouts up to multiple addresses if they request it.
There's a different address management page that I can enable for an account, that allows you to enter multiple addresses (up to whatever limit I set) and you also specify the ratio of the reward that each address gets.

So e.g. you could send 10% to one address and 90% to another etc.

Again PM me if you need this Smiley

The cloud mining changes will allow more control over this, but I've left those changes incomplete for now since no one mining on the pool has enough hash rate for that, so completing those changes got down graded in the TODO list to: 'who knows when if ever'
The main part of that change was actually a change in account control that is live already.
Most will have noticed this with the 'Verify' option on your account - this is just one part of the account control I added where I can set various options on accounts (including saying they are cloud master and cloud accounts) and the web and KanoDB treat each differently with different web pages and different access control.
The part missing for cloud mining is mainly just the new web pages and a table to store the cloud settings.

Pool: https://kano.is Here on Bitcointalk: Forum BTC: 1KanoPb8cKYqNrswjaA8cRDk4FAS9eDMLU
FreeNode IRC: irc.freenode.net channel #kano.is Majority developer of the ckpool code
Help keep Bitcoin secure by mining on pools with full block verification on all blocks - and NO empty blocks!
Newko
Full Member
***
Offline Offline

Activity: 233


View Profile
Today at 10:21:49 AM
 #31789

Ok...something like this worked about a year or so ago, so let me try again:

Hickory dickory dock
We really need a block
Two, not one, would be more fun
Hickory, dickory BLOCK!

Mine on!  Grin
aideed
Jr. Member
*
Offline Offline

Activity: 34


View Profile
Today at 10:44:34 AM
 #31790

Ok...something like this worked about a year or so ago, so let me try again:

Hickory dickory dock
We really need a block
Two, not one, would be more fun
Hickory, dickory BLOCK!

Mine on!  Grin

+1!

Mine hard, mine on!

1D8cym8zs44vaS4PfXjwtjhBvRjrUNejeK
kano
Legendary
*
Offline Offline

Activity: 2296


Linux since 1997 RedHat 4


View Profile
Today at 11:31:07 AM
 #31791

Been having more problems again over the last hour with the Silicon Valley half of stratum.kano.is
Seems another low level DDoS of the providers servers.
As long as you have a backup node then it should have little effect on you since the rest of the nodes are all ok.
Most users will automatically switch to the LA half of stratum.kano.is and that's all OK, but that's random due to the DNS round-robin so some will still be trying to connect to the Silicon Valley half.
Still awaiting an "it's OK now" reply for the provider.

Pool: https://kano.is Here on Bitcointalk: Forum BTC: 1KanoPb8cKYqNrswjaA8cRDk4FAS9eDMLU
FreeNode IRC: irc.freenode.net channel #kano.is Majority developer of the ckpool code
Help keep Bitcoin secure by mining on pools with full block verification on all blocks - and NO empty blocks!
Waztim
Jr. Member
*
Offline Offline

Activity: 56


View Profile
Today at 12:29:25 PM
 #31792

And the Block goes on, and the Block goes on. Let's crack this Puppy. A Ham Sammich has now been offered unto the Block so that it may look down upon us and have mercy upon our purring miners and reward us with what we have so dutifully worked for. I hope its like Ham, cause that's all I got, after that we may have to go to Chicken Flavored Ramen Cup O Noodles. LOL

We have only just begun to mine!!

The only thing to fear is fear itself!!

The Block Stops here!!

Make This Block Great Again!!

Lock this Block Up!!

Mine On!!
kano
Legendary
*
Offline Offline

Activity: 2296


Linux since 1997 RedHat 4


View Profile
Today at 12:43:22 PM
 #31793

Been having more problems again over the last hour with the Silicon Valley half of stratum.kano.is
Seems another low level DDoS of the providers servers.
As long as you have a backup node then it should have little effect on you since the rest of the nodes are all ok.
Most users will automatically switch to the LA half of stratum.kano.is and that's all OK, but that's random due to the DNS round-robin so some will still be trying to connect to the Silicon Valley half.
Still awaiting an "it's OK now" reply for the provider.
Well no more disconnects since before I made the above post, so it seems all OK again now.
No reply from the provider though Tongue
Maybe they don't like that I monitor and see the network problems before they even notice them ...
Anyway, all good, mine on.

Pool: https://kano.is Here on Bitcointalk: Forum BTC: 1KanoPb8cKYqNrswjaA8cRDk4FAS9eDMLU
FreeNode IRC: irc.freenode.net channel #kano.is Majority developer of the ckpool code
Help keep Bitcoin secure by mining on pools with full block verification on all blocks - and NO empty blocks!
1manshow
Newbie
*
Offline Offline

Activity: 12


View Profile
Today at 01:02:00 PM
 #31794

Can someone let me know how do I set different location pool information in secondary and tertiary pool information on Antminer S9? All I can find on main page of Kano website is stratum+tcp://stratum.kano.is:3333 and port variations. Or you people set any other pool information in those second and third pool info? Sorry for my bad English.
Ports don't matter unless you are having trouble with port 3333 due to your miners.
Sometimes internet providers block ports and can cause problems like that but I doubt they'd block 3333
However, some people find that only certain ports work and everything else is blocked, so you can use the other ports in that case, and usually 80 should be fine.

Anyway, your setup would depend on where you are, to decide which should be first.

Normally you'd use stratum+tcp://stratum.kano.is:3333 first if you are in the USA on the west coast of central USA
If you are on the east cost or north east canada, then you'd use stratum+tcp://nya.kano.is:3333

If you are in Europe you'd use either stratum+tcp://de.kano.is:3333 or stratum+tcp://nl.kano.is:3333

From the asia area you'd use either stratum+tcp://jp.kano.is:3333 or stratum+tcp://sg.kano.is:3333

Second would be the next nearest node, or if you use stratum+tcp://stratum.kano.is:3333 first then 2nd would be stratum+tcp://nya.kano.is:3333

For third, I'd suggest you use a PPS pool as I mentioned recently.
https://bitcointalk.org/index.php?topic=789369.msg26349919#msg26349919

-------

Thank you very much for your detailed explanation mate. Glad to be part of your awesome pool and the level of support from you directly is exhilarating. Mine on!
kano
Legendary
*
Offline Offline

Activity: 2296


Linux since 1997 RedHat 4


View Profile
Today at 01:17:41 PM
 #31795

Logins to the web site are currently disabled due to someone sending a lot of fake login attempts (from lots of different IP addresses)
The logins don't really cause a problem, but better to disable them for a while, just in case someone has an easy password and the 'hacker' guesses it ...

Pool: https://kano.is Here on Bitcointalk: Forum BTC: 1KanoPb8cKYqNrswjaA8cRDk4FAS9eDMLU
FreeNode IRC: irc.freenode.net channel #kano.is Majority developer of the ckpool code
Help keep Bitcoin secure by mining on pools with full block verification on all blocks - and NO empty blocks!
kremit
Newbie
*
Offline Offline

Activity: 13


View Profile
Today at 04:01:47 PM
 #31796

But for what is worth they hit another block about 20 mins ago and I happened to notice it when they were about 12 mins in to the next block and kanopool info was showing it being 2 mins in to the next block and so I put the 2 pages next to each other and hit refresh on kano and then I took a screen shot for you so you can see what I mean.   and got it just in the nick of time because only a few seconds later someone some were found that block and then it was on to the next one when I refreshed the kano page again.
I think I see the confusion... the UI in your left screenshot is showing the time into their pool round, not the time into a network block. If you look at the table to the right of the 12 minutes in your screenshot, it shows Slush found a block 11 minutes before, which triggered a new round. Back when it was a much smaller pool, that round timer would show 2, 4, even 12 hours until a pool block was found (I use them as backup). So the timer doesn't have anything to do with the current network block listed below it. I can confirm that the last network block time on kano's website almost always matches up when I'm logged in there and happen to check against another site like btc or tradeblock... or my bitcoin node :-)
Pages: « 1 ... 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 [1590]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!