KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 625.

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: MattMell on December 28, 2017, 09:25:57 PM

my estimated next difficulty calculation : 1 890 290 596 971 0.92% 18/01/01 10:50

will probably end up between 1.0-2.5%

Any other estimates ?

Based on the prior blocks in this difficulty round, it's currently 9.88 mins between blocks.

That puts the next difficulty around 1,895,655,751,456.57, or about 1.2% increase. Scheduled for the wee hours in the morn of the first day of 2018 (US mountain time).

M

Waztim

member

Activity: 210

Merit: 15

Quote from: fjtropepe on December 28, 2017, 09:42:30 PM

Haven't been dancing hard enough. Sorry guys, about to get jiggy with it.

Come On Luck, why are you being so bashful? A serving of Teriyaki Chicken was sacrificed for the order. Getting Jiggy!! Mine On with Kano-San. Cheesy

fjtropepe

member

Activity: 126

Merit: 10

Haven't been dancing hard enough. Sorry guys, about to get jiggy with it.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: mtaboneweb on December 28, 2017, 07:12:06 PM

Maybe I found it? I guess it's the vertical red line and not the horizontal one?

1.27 Th/s

https://www.dropbox.com/s/niuolftvixp6ph3/2017-12-28_17-08-04.jpg

Yeah also the graph horizontal red line isn't zero

The average red line is, of course, the average for the whole graph.
That graph is about 24 days wide, so your average hash rate for the last 24 days will of course be pretty low if you've not been mining for a day yet.
It will be less than 1/24 of your hash rate.

If you, or anyone else, is wondering what those 2 red numbers at the far right bottom are:
The bottom one is the time between each time key (in this case 1 day) and the top one is how many times that is divided for the vertical lines (in this case 2 times)
Thus the time key shows once per day, and the red lines are 1/2 a day apart.

Waztim

member

Activity: 210

Merit: 15

Come On Block! Mine On with Kano-San, the best Bitcoin Mining Pool on Earth.

MattMell

newbie

Activity: 42

Merit: 0

my estimated next difficulty calculation : 1 890 290 596 971 0.92% 18/01/01 10:50

will probably end up between 1.0-2.5%

Any other estimates ?

VRobb

hero member

Activity: 1610

Merit: 538

I'm in BTC XTC

No, it's the horizontal line, though that's the average across the whole graph. Looking at the few spikes and then the last 5 or 6 shifts now showing, I'd say it all looks normal to me.
Mine On! Cool

mtaboneweb

jr. member

Activity: 55

Merit: 1

Maybe I found it? I guess it's the vertical red line and not the horizontal one?

1.27 Th/s

usukan

legendary

Activity: 1590

Merit: 1002

Quote from: kano on December 28, 2017, 06:45:01 AM

Quote from: usukan on December 28, 2017, 03:23:20 AM

in the stats Kano - "shifts"

what does "Inv Diff" actually mean? and why would I get some zeros here while actively mining?

Thanks - usukan

Your invalids you submitted during that shift, as a total Diff of invalids.
The lower the better

.. as opposed to the Diff you submitted which is "Your Diff"
The higher the better

Thanks Kano

mtaboneweb

jr. member

Activity: 55

Merit: 1

Quote from: kano on December 28, 2017, 06:25:56 PM

Quote from: mtaboneweb on December 28, 2017, 06:20:52 PM

So I'm up and running now and wondering if this is looking good or maybe there is something I should look into? My red line on the Shift Graph page has not moved above zero but hopefully I'll see some movement tomorrow?

https://www.dropbox.com/s/qtwywi2owxl9150/2017-12-28_16-14-52.jpg

Workers page...
https://www.dropbox.com/s/nqefdzvifgv67p3/2017-12-28_16-21-44.jpg

The shift graph shows completed shifts, so up until the first shift you were in completed, the average across the graph would have been zero.
Shifts are usually around 50 minutes each.

Edit: also, the shifts are processed about 13 minutes after they complete.

I guess that’s what I’m wondering about. I’ve completed 7 shifts and the red bar still says zero all the way to the right of the graph. The 7 completed shifts are in my first screenshot. Maybe I’m not being patient enough but I would hope to see more than 0 after roughly 7-ish hours.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: mtaboneweb on December 28, 2017, 06:20:52 PM

So I'm up and running now and wondering if this is looking good or maybe there is something I should look into? My red line on the Shift Graph page has not moved above zero but hopefully I'll see some movement tomorrow?

https://www.dropbox.com/s/qtwywi2owxl9150/2017-12-28_16-14-52.jpg

Workers page...
https://www.dropbox.com/s/nqefdzvifgv67p3/2017-12-28_16-21-44.jpg

The shift graph shows completed shifts, so up until the first shift you were in completed, the average across the graph would have been zero.
Shifts are usually around 50 minutes each.

Edit: also, the shifts are processed about 13 minutes after they complete.

mtaboneweb

jr. member

Activity: 55

Merit: 1

So I'm up and running now and wondering if this is looking good or maybe there is something I should look into? My red line on the Shift Graph page has not moved above zero but hopefully I'll see some movement tomorrow?

Workers page...

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: 2tights on December 28, 2017, 04:01:02 PM

Quote from: kano on December 28, 2017, 03:26:46 PM

Quote from: 2tights on December 28, 2017, 03:19:41 PM

Quote from: kano on December 28, 2017, 02:58:48 PM

Quote from: minergain.com on December 28, 2017, 09:12:59 AM

Quote from: kano on December 28, 2017, 06:47:02 AM

Time has no effect on you finding a block.
Each hash you do has the same chance of finding a block - be it 1 second after the last network block or 1 hour.

Kano, have you ever thought about the possibility of "reverse" mining? Where you randomly pick a final hash (probably the wrong terminology) with enough zeros in front, lock the time in, pick a group of transactions that are a little lower on the list so they stay for a while and then do a validation with each nonce - perhaps randomly selected but never duplicated. I guess the previous block hash is included, so once a block is found, then everything would have to start over. It is still luck, but seems that beating up a single answer may offer an answer quicker than totally "heads or tails" with this difficulty level. In any case, I have no clue if the network even allows the time to be locked in for multiple seconds or even minutes, but it would seem plausible since computer dates/times can vary.

Sha256 is a one way hash.

I think he's making an analogy to a rainbow table as used in things like password cracking where the rainbow table includes all the resulting hashes.

https://crypto.stackexchange.com/questions/34158/is-this-sha256-hash-implementation-secure-from-rainbow-table-brute-forcing-atta

Rainbow tables wont work on sha256 due to the size.

Well, its impractical based on current hardware limitations. though, in the future it won't be. That link discusses the exponential requirements for hardware resources to give the context.

Yeah I've made comment about that a while ago Cheesy

https://bitcointalksearch.org/topic/make-bitcoin-sha256-future-proof-263840

2tights

sr. member

Activity: 308

Merit: 251

I like big BITS and I cannot lie.

Quote from: kano on December 28, 2017, 03:26:46 PM

Quote from: 2tights on December 28, 2017, 03:19:41 PM

Quote from: kano on December 28, 2017, 02:58:48 PM

Quote from: minergain.com on December 28, 2017, 09:12:59 AM

Quote from: kano on December 28, 2017, 06:47:02 AM

Time has no effect on you finding a block.
Each hash you do has the same chance of finding a block - be it 1 second after the last network block or 1 hour.

Kano, have you ever thought about the possibility of "reverse" mining? Where you randomly pick a final hash (probably the wrong terminology) with enough zeros in front, lock the time in, pick a group of transactions that are a little lower on the list so they stay for a while and then do a validation with each nonce - perhaps randomly selected but never duplicated. I guess the previous block hash is included, so once a block is found, then everything would have to start over. It is still luck, but seems that beating up a single answer may offer an answer quicker than totally "heads or tails" with this difficulty level. In any case, I have no clue if the network even allows the time to be locked in for multiple seconds or even minutes, but it would seem plausible since computer dates/times can vary.

Sha256 is a one way hash.

I think he's making an analogy to a rainbow table as used in things like password cracking where the rainbow table includes all the resulting hashes.

https://crypto.stackexchange.com/questions/34158/is-this-sha256-hash-implementation-secure-from-rainbow-table-brute-forcing-atta

Rainbow tables wont work on sha256 due to the size.

Well, its impractical based on current hardware limitations. though, in the future it won't be. That link discusses the exponential requirements for hardware resources to give the context.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: 2tights on December 28, 2017, 03:19:41 PM

Quote from: kano on December 28, 2017, 02:58:48 PM

Quote from: minergain.com on December 28, 2017, 09:12:59 AM

Quote from: kano on December 28, 2017, 06:47:02 AM

Time has no effect on you finding a block.
Each hash you do has the same chance of finding a block - be it 1 second after the last network block or 1 hour.

Kano, have you ever thought about the possibility of "reverse" mining? Where you randomly pick a final hash (probably the wrong terminology) with enough zeros in front, lock the time in, pick a group of transactions that are a little lower on the list so they stay for a while and then do a validation with each nonce - perhaps randomly selected but never duplicated. I guess the previous block hash is included, so once a block is found, then everything would have to start over. It is still luck, but seems that beating up a single answer may offer an answer quicker than totally "heads or tails" with this difficulty level. In any case, I have no clue if the network even allows the time to be locked in for multiple seconds or even minutes, but it would seem plausible since computer dates/times can vary.

Sha256 is a one way hash.

I think he's making an analogy to a rainbow table as used in things like password cracking where the rainbow table includes all the resulting hashes.

https://crypto.stackexchange.com/questions/34158/is-this-sha256-hash-implementation-secure-from-rainbow-table-brute-forcing-atta

Rainbow tables wont work on sha256 due to the size.

2tights

sr. member

Activity: 308

Merit: 251

I like big BITS and I cannot lie.

Quote from: kano on December 28, 2017, 02:58:48 PM

Quote from: minergain.com on December 28, 2017, 09:12:59 AM

Quote from: kano on December 28, 2017, 06:47:02 AM

Time has no effect on you finding a block.
Each hash you do has the same chance of finding a block - be it 1 second after the last network block or 1 hour.

Kano, have you ever thought about the possibility of "reverse" mining? Where you randomly pick a final hash (probably the wrong terminology) with enough zeros in front, lock the time in, pick a group of transactions that are a little lower on the list so they stay for a while and then do a validation with each nonce - perhaps randomly selected but never duplicated. I guess the previous block hash is included, so once a block is found, then everything would have to start over. It is still luck, but seems that beating up a single answer may offer an answer quicker than totally "heads or tails" with this difficulty level. In any case, I have no clue if the network even allows the time to be locked in for multiple seconds or even minutes, but it would seem plausible since computer dates/times can vary.

Sha256 is a one way hash.

I think he's making an analogy to a rainbow table as used in things like password cracking where the rainbow table includes all the resulting hashes.

https://crypto.stackexchange.com/questions/34158/is-this-sha256-hash-implementation-secure-from-rainbow-table-brute-forcing-atta

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: minergain.com on December 28, 2017, 09:12:59 AM

Quote from: kano on December 28, 2017, 06:47:02 AM

Time has no effect on you finding a block.
Each hash you do has the same chance of finding a block - be it 1 second after the last network block or 1 hour.

Kano, have you ever thought about the possibility of "reverse" mining? Where you randomly pick a final hash (probably the wrong terminology) with enough zeros in front, lock the time in, pick a group of transactions that are a little lower on the list so they stay for a while and then do a validation with each nonce - perhaps randomly selected but never duplicated. I guess the previous block hash is included, so once a block is found, then everything would have to start over. It is still luck, but seems that beating up a single answer may offer an answer quicker than totally "heads or tails" with this difficulty level. In any case, I have no clue if the network even allows the time to be locked in for multiple seconds or even minutes, but it would seem plausible since computer dates/times can vary.

Sha256 is a one way hash.

wavelengthsf

full member

Activity: 658

Merit: 118

May the nonces be in our favor!

clgrissom3

legendary

Activity: 1736

Merit: 1032

Carl, aka Sonny :)

Quote from: VRobb on December 28, 2017, 01:45:57 PM

Actually kano and Canaan have been working together for some time now. We used to have contests where someone could win an Avalon miner (I never did, darn it!) and if you check the pool stats you'll see Canaan does their burn-in testing here.
Mine On! Cool

Haha! I never won any of those either but it was fun. It's almost time for an old fashion BLOCK FRIDAY! Cheesy

rifleman74

member

Activity: 658

Merit: 21

4 s9's 2 821's

Block dance...let's do this.

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