Author

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

full member
Activity: 152
Merit: 100
pretty awesome, waiting on 3 blocks to mature at once BTC
hero member
Activity: 1246
Merit: 501
Nice, lots of blocks today.   Grin
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
hi... i want to know.. how long we wait to receive the payout? thx
On the blocks page, I have to wait until they hit 101 before I can send the payout to the miners (the same as bitcoin-qt)
I do the actual final payment step manually, but the pool code calculates and generates the payouts (as you can check in git)
So the first one will be after about 10 hours from now, and the 2nd one about 4 hours after that.

Also note that if you mine less than 10,000 satoshi worth (as I mentioned before) it ends up in a dust fund.
If you later total more than 10,000 satoshi, I'll send the sum to your address.
A transaction of less than 10,000 satoshi requires more than that in fees, so I save it up for later.

The accounting information is still missing from the web site, due to the fact that I've had to expedite doing the Marker changes due to memory usage.
The accounting web information is probably next after the Marker changes are finished.

Edit: the Marker changes are explained here:
https://bitcointalksearch.org/topic/m.9417792
newbie
Activity: 47
Merit: 0
I went to bed last night seeing we hit a block, wake up and see we hit another. I was beginning to think I brought my bad luck to the pool when we didn't find a block for a while.
member
Activity: 62
Merit: 10
hi... i want to know.. how long we wait to receive the payout? thx
full member
Activity: 152
Merit: 100
so much for bad luck lol, 8.1%  Cool
legendary
Activity: 2210
Merit: 1109
And for your further pleasure:

Code:
[2014-11-07 21:14:16] Possible block solve diff 85422913003.058868 !   
[2014-11-07 21:14:16] BLOCK ACCEPTED!    
[2014-11-07 21:14:16] Solved and confirmed block 328952  

https://blockchain.info/tx/5d3260e6320f8a2dd26c8cc1af0689288d8c9b752b5be0a641150e7b621b1ed3

2 strikes in a row  Grin great !
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
And for your further pleasure:

Code:
[2014-11-07 21:14:16] Possible block solve diff 85422913003.058868 !   
[2014-11-07 21:14:16] BLOCK ACCEPTED!    
[2014-11-07 21:14:16] Solved and confirmed block 328952  

https://blockchain.info/tx/5d3260e6320f8a2dd26c8cc1af0689288d8c9b752b5be0a641150e7b621b1ed3
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
heh 221.93%  Shocked
That's really not remotely unusual. No pool is exempt from bad luck, but over time it all evens out.
full member
Activity: 152
Merit: 100
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
From the pool console for your pleasure:
Code:
[2014-11-07 17:44:04] Possible block solve diff 48041159117.256241 !  
[2014-11-07 17:44:04] BLOCK ACCEPTED!
[2014-11-07 17:44:04] Solved and confirmed block 328928

https://blockchain.info/block-index/486179/000000000000000016e2f2d72a1622591c493f26623063296f8d48b8488c4c63
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Yeah a short downtime coz it looks like someone crashed the pool (on purpose?) with a specially crafted invalid share.
Bug fixed and pool back up and running.
You are good Wink
For the record I have noticed a couple of pool restarts after my post. Seems like it was continuous attack
Just the one share attack.
ckolivas fixed the bug once we had a chance to look at it.
I restarted ckpool twice extra: once to enable a full debug version and a second time to push the actual change in so the specific problem wouldn't happen again.
A standard ckpool restart just makes you immediately reconnect to the pool, so the outage on the miner is very small and it shouldn't failover away from the pool either.
Though, we avoid restarting ckpool as much as possible Smiley
legendary
Activity: 1610
Merit: 1000
Yeah a short downtime coz it looks like someone crashed the pool (on purpose?) with a specially crafted invalid share.
Bug fixed and pool back up and running.
You are good Wink
For the record I have noticed a couple of pool restarts after my post. Seems like it was continuous attack
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Yeah a short downtime coz it looks like someone crashed the pool (on purpose?) with a specially crafted invalid share.
Bug fixed and pool back up and running.
legendary
Activity: 1610
Merit: 1000
Kano,
Kano.is shows

CKPool:     1,047.02THs
Shares:     71,750,871,312 (181.17%)
Invalid:     144,561,079 (0.201%)
Pool, Last Block:     87h (328234)
Network, Last Block:     47m (328802)
Users:     41
Workers:     1488
User:   
Pass:   
 
  
Meanwhile accourding to blochainifo last block is


https://blockchain.info/block-index/486129/00000000000000001bb35f08fbb5508a04b4a56372924b4da251dd7f76ed9d76

It seems like there is an  issue with pool web front end or bitcoind hang...

PS
It seems ok now pool web front end is in sync with blockchain
member
Activity: 71
Merit: 10

Nice... Smiley Just added the rest of mine too.
legendary
Activity: 2210
Merit: 1109
Incoming.

BAM ! 911+ TH and counting  Grin Shocked Grin

edit: We hit 1+ PHs !!
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
legendary
Activity: 4326
Merit: 8950
'The right to privacy matters'
I sent the payout for the last block a short while ago, and it has been confirmed also, in case anyone was waiting - done first thing when I woke up.


 thanks paid for the 2.  Will keep them here for now 6 s-3's all told.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Updated the list of available urls/ports if there are any network issues at your end that cause problems with or block port 3333:
You can also try any of:
stratum+tcp://stratum80.kano.is:80
stratum+tcp://stratum81.kano.is:81
stratum+tcp://stratum443.kano.is:443
stratum+tcp://stratum8080.kano.is:8080

Jump to: