Author

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

legendary
Activity: 1302
Merit: 1318
Technical Analyst/Trader
Thanks for this post extremely informative.

Sure... You're very welcome.
legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
I'm finally on the BOARD!!! WOOT WOOT WOOT!!! PEW PEW PEW!!!

#   Height   Who   Block Reward   When   Status   Diff   Diff%   CDF   B
518   397511   nhando1977.POWER   25.33692083   2016-02-09 08:26:24+00   +37 Confirms   63,502,550,898   44.063%   0.356   1

 

Way to go!  We all appreciate it!
full member
Activity: 196
Merit: 100
I'm finally on the BOARD!!! WOOT WOOT WOOT!!! PEW PEW PEW!!!

#   Height   Who   Block Reward   When   Status   Diff   Diff%   CDF   B
518   397511   nhando1977.POWER   25.33692083   2016-02-09 08:26:24+00   +37 Confirms   63,502,550,898   44.063%   0.356   1

 
legendary
Activity: 924
Merit: 1000
Dark Passenger Bitcoin miner 2013,Bitcoin node
All who are new to mining, new to the pool and new to the blockchain will find the following video quite educational.  Andreas got into explanations about SHA256, the blockchain, what goes on in a "race" when blocks are found by competing miners, the importance of low latency, etc...  I thought it was educational and others new to mining here on the pool will find it educational as well. 

If I'm out of line for posting the link in this forum, my feelings will not be hurt in any way if the moderator decides it needs to be deleted.

Consensus Algorithms, Blockchain Technology and Bitcoin UCL - by Andreas M. Antonopoulos
https://www.youtube.com/watch?v=fw3WkySh_Ho
Thanks for this post extremely informative
legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
POWER 3 PH power ! go go go, SUPA GREEN !

Block # 397438 found by Dragon Miner 1.5 th/s miner

Code:
                          Best Share
captminer2.301 sg.kano.is 1797192791277

talking about BMT FW problems ? hmmmmm

after a hard reboot & i saw this !


2 blocks? wow - you are "rich"! LOL.
One of s7s is also giving me issues - did several power reboots but still freezes after 1 hour....
hard reboot = power reboot?
legendary
Activity: 1302
Merit: 1318
Technical Analyst/Trader
All who are new to mining, new to the pool and new to the blockchain will find the following video quite educational.  Andreas got into explanations about SHA256, the blockchain, what goes on in a "race" when blocks are found by competing miners, the importance of low latency, etc...  I thought it was educational and others new to mining here on the pool will find it educational as well.  

If I'm out of line for posting the link in this forum, my feelings will not be hurt in any way if the moderator decides it needs to be deleted.

Consensus Algorithms, Blockchain Technology and Bitcoin UCL - by Andreas M. Antonopoulos
https://www.youtube.com/watch?v=fw3WkySh_Ho
legendary
Activity: 924
Merit: 1000
Dark Passenger Bitcoin miner 2013,Bitcoin node
woke up this morning to beeps sip down and most importantly 2 more blocks
legendary
Activity: 1500
Merit: 1002
Mine Mine Mine
POWER 3 PH power ! go go go, SUPA GREEN !

Block # 397438 found by Dragon Miner 1.5 th/s miner

Code:
                          Best Share
captminer2.301 sg.kano.is 1797192791277

talking about BMT FW problems ? hmmmmm

after a hard reboot & i saw this !

legendary
Activity: 924
Merit: 1000
Dark Passenger Bitcoin miner 2013,Bitcoin node
full member
Activity: 475
Merit: 100
nhando finally Smiley well done
newbie
Activity: 32
Merit: 0
Well Done that man !!

Hell of a way to go block hunting

nhando1977   3,854.76THs    Smiley

The whole pool wasn't that big for a long time.


newbie
Activity: 48
Merit: 0
Couple of node questions guys:
1) I'm in south eastern Australia: which node should I be pointing to?
2) Why? as in does it matter?

The nodes increase the propagation speed of the blocks found by the pool.
They also will attempt to submit a block, if you find one and are mining to a node, before the main pool node will submit it.
If your ping time to the node and to the main pool are similar, then mining to the main pool will be best.
If they are quite different, 100-200ms (or more) different, then mining to the node is appropriate.
So I worked out how to ping:
main ~200ms
jp ~ 330ms &
sg ~ 130ms

So I should point to singapore?

Crash
While singapore is a little faster (70ms), not being very close to singapore and knowing how routing from Australia to the rest of the world can be random, I'd probably still suggest connecting to the main pool node in your specific case.
Ok, thanks
member
Activity: 106
Merit: 10

So either the miners are confused of their identity, the block counter is messed up - well it is a bitmain firmware, who knows what they fucked up this time Smiley - or you run a strange proxy that mixes the workers up.

Anyway, doesn't really matter, one of them found a block, and we are all very happy about that Cheesy

Well there you have it.  Thanks for the insight, and I'm glad we won the orphan race.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
...
Heck, they don't even show the Orphan in their stats and block page, like it never happen.... How do we show their 10PH of miners the truth and get 5PH to move here?
If you scroll back about 100 pages, you'll find wizkid telling me how I'm displaying blocks wrongly by showing orphans and rejects ... ... ...

Yeah it's somewhat pointless telling them that they are hiding information, they've been doing it for so long, it's second nature to them.
newbie
Activity: 48
Merit: 0
Couple of node questions guys:
1) I'm in south eastern Australia: which node should I be pointing to?
2) Why? as in does it matter?

The nodes increase the propagation speed of the blocks found by the pool.
They also will attempt to submit a block, if you find one and are mining to a node, before the main pool node will submit it.
If your ping time to the node and to the main pool are similar, then mining to the main pool will be best.
If they are quite different, 100-200ms (or more) different, then mining to the node is appropriate.
So I worked out how to ping:
main ~200ms
jp ~ 330ms &
sg ~ 130ms

So I should point to singapore?

Crash

im in north australia, pointed to de.kano, getting around 5.2ms
did you try de.?
to sg. im getting 327ms
I'm getting over 350ms to DE
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Couple of node questions guys:
1) I'm in south eastern Australia: which node should I be pointing to?
2) Why? as in does it matter?

The nodes increase the propagation speed of the blocks found by the pool.
They also will attempt to submit a block, if you find one and are mining to a node, before the main pool node will submit it.
If your ping time to the node and to the main pool are similar, then mining to the main pool will be best.
If they are quite different, 100-200ms (or more) different, then mining to the node is appropriate.
So I worked out how to ping:
main ~200ms
jp ~ 330ms &
sg ~ 130ms

So I should point to singapore?

Crash
While singapore is a little faster (70ms), not being very close to singapore and knowing how routing from Australia to the rest of the world can be random, I'd probably still suggest connecting to the main pool node in your specific case.
full member
Activity: 475
Merit: 100
Couple of node questions guys:
1) I'm in south eastern Australia: which node should I be pointing to?
2) Why? as in does it matter?

The nodes increase the propagation speed of the blocks found by the pool.
They also will attempt to submit a block, if you find one and are mining to a node, before the main pool node will submit it.
If your ping time to the node and to the main pool are similar, then mining to the main pool will be best.
If they are quite different, 100-200ms (or more) different, then mining to the node is appropriate.
So I worked out how to ping:
main ~200ms
jp ~ 330ms &
sg ~ 130ms

So I should point to singapore?

Crash

im in north australia, pointed to de.kano, getting around 5.2ms
did you try de.?
to sg. im getting 327ms
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Block!  cryptichermit gets on the Acclaim board with his first Kano block!  Way to go!
It's a real orphan race this time ... we were first on the relay ... lets hope we win ...
We Won! ... and beat eligius Smiley

Is it unusual that the reported worker is inaccurate?
website says cryptichermit.cpww9 found the block, but it was actually cpww16?

cpww9 found it.

Strange GUI is reporting no block found (wanted to capture the moment)-

Look here- CPWW9
https://i.imgur.com/oDTPDXG.png


But CPWW16 is the only miner at that location showing a block find-
https://i.imgur.com/oSagsAR.png

Looking into the pool logs ...
Code:
shares.657867091.json={"workinfoid":6247676423394308467,"errn":0,"result":true,"clientid":592004,"ntime":"56b9712e","nonce2":"0aae070000000000","enonce1":"31fcbc56","createby":"code","diff":4094.0,"nonce":"19025d2e","seqpid":7866,"username":"cryptichermit","sdiff":233179621372.90506,"hash":"000000000000000004b7191e28206df9829849d391357c6fc6f9e715eda702d3","seqshares":622840664,"createdate":"1454993741,960935954","seqstart":1454650523,"createcode":"parse_submit","workername":"cryptichermit.cpww9","seqall":657867091}
block.657867666.json={"height":397486,"seqpid":7866,"username":"cryptichermit","blockhash":"eda702d3c6f9e71591357c6f829849d328206df904b7191e0000000000000000","workinfoid":6247676423394308467,"confirmed":"1","createdate":"1454993742,300635863","workername":"cryptichermit.cpww9","clientid":592004,"enonce1":"31fcbc56","nonce2":"0aae070000000000","nonce":"19025d2e","diff":233179621372.90506,"createby":"code","reward":2517438430,"seqstart":1454650523,"createcode":"block_solve","seqall":657867666,"seqblock":32}
We see a clientid that was returned by the miner when it submitted the share to the pool ... 592004
Checking the logs regarding miners connecting we see:
Code:
[2016-02-07 07:48:09.970] Authorised client 592004 worker cryptichermit.cpww9 as user cryptichermit
So the pool is happy to say that it was cpww9 Smiley

So either the miners are confused of their identity, the block counter is messed up - well it is a bitmain firmware, who knows what they fucked up this time Smiley - or you run a strange proxy that mixes the workers up.

Anyway, doesn't really matter, one of them found a block, and we are all very happy about that Cheesy
newbie
Activity: 48
Merit: 0
Couple of node questions guys:
1) I'm in south eastern Australia: which node should I be pointing to?
2) Why? as in does it matter?

The nodes increase the propagation speed of the blocks found by the pool.
They also will attempt to submit a block, if you find one and are mining to a node, before the main pool node will submit it.
If your ping time to the node and to the main pool are similar, then mining to the main pool will be best.
If they are quite different, 100-200ms (or more) different, then mining to the node is appropriate.
So I worked out how to ping:
main ~200ms
jp ~ 330ms &
sg ~ 130ms

So I should point to singapore?

Crash
member
Activity: 66
Merit: 10


Strange GUI is reporting no block found (wanted to capture the moment)-

Look here- CPWW9
https://i.imgur.com/oDTPDXG.png


But CPWW16 is the only miner at that location showing a block find-
https://i.imgur.com/oSagsAR.png


Look at the best share though.  It's clear that cpww9 found the block.  Antminer firmware has always had problems with the foundblocks field not being accurate.

X
Jump to: