[∞ YH] solo.ckpool.org 2% fee solo mining 289 blocks solved!

[willi9974]

if your miner create no new share with a higher diff as your best share before, than will your bestshare stay at this point so long as you send a share they has a higher diff as before.

the bestshare parameter shows you only the best share what you have send. if you will not find a better one, the old value will stay so long as you find a better one.

Best regards,
Willi

Yes, I understand this, but why doesn't the Antminer Dashboard data have anything to do with the CKPOOL data?

please have a look at the page, what the data mean...



https://www.eastshoremining.com/glossary-and-directions-for-the-miner-status-page-of-antminer-series/

URL: this is the pool address

User: the user name of the worker

Status: status of pool connection. Alive means it is connected to the pool. If otherwise, it will show “dead”.

Diff: mining difficulty.

Priority: the priority of the pool you set. Usually, the miner will try to connect the pool with the priority “0” first, if failed, then it will try to connect the pool with the priority “1”, then the priority “2”, and so on.

Accepted: this indicates the shares accepted by the pool. Any shares that were “accepted” by the pool are set in stone (unless you delete your worker or your account).

DiffA#: the difficulty of the last Accepted share.

DiffR#: the difficulty of the last Rejected share.

DiffS#: the difficulty of the last Stale share.

Rejected: If your miner successfully performs work, but submits it too late for that block, it is called a ‘rejected share’ of work. You will get no credit for that work, and it cannot be banked towards future coin generation. Rejected shares are inevitable, regardless of how powerful your mining computer is. The desired goal is to minimize rejected shares and maximize accepted shares.

Discarded: this indicates the shares that were never turned into the pool. Maybe someone solved that share first, or maybe the block was solved and the miner restarted the work. Discards are not rejects, they aren’t even shares. It means your miner had work prepared to hash but instead it discarded it in favor of newer/fresher work. You aren’t wasting any hashes when your miner discards work.

Stale: stale is when your miner submits work for a block that was already solved. This means your miner wasn’t notified about the new block yet, it’s inevitable.

LSDiff: last share difficulty.

LStime: time since the last share.

[Josek8]

if your miner create no new share with a higher diff as your best share before, than will your bestshare stay at this point so long as you send a share they has a higher diff as before.

the bestshare parameter shows you only the best share what you have send. if you will not find a better one, the old value will stay so long as you find a better one.

Best regards,
Willi

Yes, I understand this, but why doesn't the Antminer Dashboard data have anything to do with the CKPOOL data?

please have a look at the page, what the data mean...



https://www.eastshoremining.com/glossary-and-directions-for-the-miner-status-page-of-antminer-series/

URL: this is the pool address

User: the user name of the worker

Status: status of pool connection. Alive means it is connected to the pool. If otherwise, it will show “dead”.

Diff: mining difficulty.

Priority: the priority of the pool you set. Usually, the miner will try to connect the pool with the priority “0” first, if failed, then it will try to connect the pool with the priority “1”, then the priority “2”, and so on.

Accepted: this indicates the shares accepted by the pool. Any shares that were “accepted” by the pool are set in stone (unless you delete your worker or your account).

DiffA#: the difficulty of the last Accepted share.

DiffR#: the difficulty of the last Rejected share.

DiffS#: the difficulty of the last Stale share.

Rejected: If your miner successfully performs work, but submits it too late for that block, it is called a ‘rejected share’ of work. You will get no credit for that work, and it cannot be banked towards future coin generation. Rejected shares are inevitable, regardless of how powerful your mining computer is. The desired goal is to minimize rejected shares and maximize accepted shares.

Discarded: this indicates the shares that were never turned into the pool. Maybe someone solved that share first, or maybe the block was solved and the miner restarted the work. Discards are not rejects, they aren’t even shares. It means your miner had work prepared to hash but instead it discarded it in favor of newer/fresher work. You aren’t wasting any hashes when your miner discards work.

Stale: stale is when your miner submits work for a block that was already solved. This means your miner wasn’t notified about the new block yet, it’s inevitable.

LSDiff: last share difficulty.

LStime: time since the last share.

I have looked at all this many times....

What I want to know is why the data is not the same in Dasboard and what CKPOOL indicates in my miner:

Dashboard:
It indicates in the Diff: 91.6K
In the DiffA: 93637514146

If we look in Ckpool it indicates this:

shares: 782833382698,
bestshare: 1033460203823.859

These data have nothing to do in common, can someone explain this data to me?
I also see that in Dashboar the Diffa always goes up but in Bestshare it has been a long time without change....

[Josek8]

if your miner create no new share with a higher diff as your best share before, than will your bestshare stay at this point so long as you send a share they has a higher diff as before.

the bestshare parameter shows you only the best share what you have send. if you will not find a better one, the old value will stay so long as you find a better one.

Best regards,
Willi

Yes, I understand this, but why doesn't the Antminer Dashboard data have anything to do with the CKPOOL data?

please have a look at the page, what the data mean...



https://www.eastshoremining.com/glossary-and-directions-for-the-miner-status-page-of-antminer-series/

URL: this is the pool address

User: the user name of the worker

Status: status of pool connection. Alive means it is connected to the pool. If otherwise, it will show “dead”.

Diff: mining difficulty.

Priority: the priority of the pool you set. Usually, the miner will try to connect the pool with the priority “0” first, if failed, then it will try to connect the pool with the priority “1”, then the priority “2”, and so on.

Accepted: this indicates the shares accepted by the pool. Any shares that were “accepted” by the pool are set in stone (unless you delete your worker or your account).

DiffA#: the difficulty of the last Accepted share.

DiffR#: the difficulty of the last Rejected share.

DiffS#: the difficulty of the last Stale share.

Rejected: If your miner successfully performs work, but submits it too late for that block, it is called a ‘rejected share’ of work. You will get no credit for that work, and it cannot be banked towards future coin generation. Rejected shares are inevitable, regardless of how powerful your mining computer is. The desired goal is to minimize rejected shares and maximize accepted shares.

Discarded: this indicates the shares that were never turned into the pool. Maybe someone solved that share first, or maybe the block was solved and the miner restarted the work. Discards are not rejects, they aren’t even shares. It means your miner had work prepared to hash but instead it discarded it in favor of newer/fresher work. You aren’t wasting any hashes when your miner discards work.

Stale: stale is when your miner submits work for a block that was already solved. This means your miner wasn’t notified about the new block yet, it’s inevitable.

LSDiff: last share difficulty.

LStime: time since the last share.

It is a complete question, I am looking for information about this data and they are very different.

For example in Diff in the dashboard that is: difficulty of the network (in an Ascik indicates me a Diff and in another mined in the same Pool indicates me another different Diff), in this case mining in Ckpool.

[willi9974]

your DiffA: 93637514146 in your miner homepage means --> the difficulty of the last Accepted share from the ck solo pool (but not the highest)

your bestshare: 1033460203823.859 displayed on the ck pool stats, means the highest share what your miner has send to the pool

so my understanding

PS: if you have more questions, so please post a screenshot from your miner local homepage and the full stats from the solo pool, than we can compare it (must be nearly from the same time) and make maybe your BTC address black...

[nalien2000]

Josek i would also point out, in the ckpool stats, the "shares" number is not actually the quantity of shares.  Rather, it is the quantity of shares times the difficulty.  The CKpool stats do not show the difficulty.  But your miners stats should show it.  For example, if you mine with a low hashpower gekkoscience compac f (or several of them), when you first start mining, you will notice in cgminer that the difficulty is set to 10,000.  That is too high of a difficulty for just a few terahash.  So eventually the difficulty lowers to a couple thousand.  But when it is 10k, there are fewer  shares showing up in cgminer.  This is a function of how the pool assigns work to the miners.  It assigns as much work as your compac F's can handle.  So while the difficulty is 10k, there are fewer shares. But once it adjusts to like 2k, there are more shares.  That is just how the pool works to assign work to the miners and to estimate the haspower.  You are trying to compare your miner's stats to ckpool stats.  Its kind of apples to oranges because ckpool shows the total diffculty (number of shares times difficulty per share) while your miners stats show thq quantity of shares, and separately the difficulty.  I may not be explaining this well but i have seen good explanations on the bitcointalk forums.

[willi9974]

The Christmas Run 28 is started
Main topic is here --> https://bitcointalk.org/index.php?topic=5417696.0


Live View Link:
https://solo.ckpool.org/users/bc1q2yctc27qdzqn37csfwj00frgsx0lfyqdjcmm3s

{
 "hashrate1m": "21.4P",
 "hashrate5m": "14.8P",
 "hashrate1hr": "2.55P",
 "hashrate1d": "115T",
 "hashrate7d": "16.5T",
 "lastshare": 1671864115,
 "workers": 22,
 "shares": 2325000000,
 "bestshare": 7183580694.071639,
 "bestever": 7183580694,
 "worker": [
  {
   "workername": "bc1q2yctc27qdzqn37csfwj00frgsx0lfyqdjcmm3s",
   "hashrate1m": "21.4P",
   "hashrate5m": "14.8P",
   "hashrate1hr": "2.55P",
   "hashrate1d": "115T",
   "hashrate7d": "16.5T",
   "lastshare": 1671864115,
   "shares": 2325000000,
   "bestshare": 7183580694.071639,
   "bestever": 7183580694
  }
 ]
}

Bitcoin Difficulty:
35.364.065.900.458

Bestshare:
7.183.580.694
483.723.196
140.255.286
132.654.236

[citb0in]

Fingers crossed for all of you and hope it turns into a Christmas present!!!!  

~ ~ ~ GOOD LUCK ~ ~ ~

[o_solo_miner]

The Christmas Run 28 is started
Live View Link:
https://solo.ckpool.org/users/bc1q2yctc27qdzqn37csfwj00frgsx0lfyqdjcmm3s

GOOD LUCK all miners out there.
I got my fingers crossed for you.

and Happy Hollydays (Frohe Festtage) to all.
 

[jimjam123]

Good Luck everyone!.
Would be a great Christmas Present for us.
Thanks again Willi and CK for supporting us miners in the community.

[cryptokayman]

is there something wrong with the pool? it hashing at 2.4PHs!

[paid2]

is there something wrong with the pool? it hashing at 2.4PHs!

Nothing to worry about

Sometimes Nicehash bids are stopped for some time (if for example someone rent a lot of hashrate with a higher price per Ph/s than us)

We are not loosing money, don't worry

[citb0in]

Exactly.

The BlockSolvers (see signature) have also started Run #008 and we wish all of them good luck. May the block finally be mined Good luck to everyone
=> Live Stats CKpool <=

Merry Christmas to all out there.

[cryptokayman]

is there something wrong with the pool? it hashing at 2.4PHs!

Nothing to worry about

Sometimes Nicehash bids are stopped for some time (if for example someone rent a lot of hashrate with a higher price per Ph/s than us)

We are not loosing money, don't worry

No i meant Ckpool servers is running at 2.5 PHs something is going on looking at Kano.is app

[jimjam123]

Kano's Pool is running at that rate, not CK's.
Look like you have the wrong pool.
CK is @ {"hashrate1m": "74.5P", "hashrate5m": "75.5P", "hashrate15m": "71.2P", "hashrate1hr": "58.7P", "hashrate6hr": "42.8P", "hashrate1d": "30.2P", "hashrate7d": "28.7P"}

is there something wrong with the pool? it hashing at 2.4PHs!

Nothing to worry about

Sometimes Nicehash bids are stopped for some time (if for example someone rent a lot of hashrate with a higher price per Ph/s than us)

We are not loosing money, don't worry

No i meant Ckpool servers is running at 2.5 PHs something is going on looking at Kano.is app

[mikeywith]

Hello.

Let's see if you can clarify this for me.

A S19J 104 has been 44 days without shutdown in CKPOOL and in Dashboard indicates this:

It indicates in the Diff: 91.6K
In the DiffA: 93637514146

If we look in Ckpool it indicates this:

shares: 782833382698,
bestshare: 1033460203823.859

These data have nothing to do in common, can someone explain this data to me?
I also see that in Dashboar the Diffa always goes up but in Bestshare it has been a long time without change....

Best regards,

Diff = the difficulty set the by pool, based on the number of shares you submit when you first connect the miner, the pool will set a number that is small enough to indicate the hashrate and large enough to avoid sending dozen of packets back and forth

Diffa  = Difficulty of the last accepted share, it always changes with every share you submit

on the pool side :

shares  = number of shares submitted (obvious I guess)
bestshare: is similar to the Diffa on the miner status page but unlike the miner status page it doesn't reset with every share you submit, the pool would reset it one a block is found.

if you so happen to hit your bestshare while looking at the miner's status page updated, diffA and bestshare on the pool will be the same.

[hiaxis]

Hi All, I'm trying to wrap my little brain around the math behind a BTC block being generated. I believe I understand the basics. However, my question is related to the nonce. Let's say I have just one miner. When it starts to "guess" the  hash for my proposed solution by incrementing the nonce from 0 to n, followed by the extranonce (rehashing each time and comparing to target), the odds of any duplication of work is zero because I have just one miner.

Now let's say I have two miners here at ckpool solo, both pointing to the same BTC address, different worker names. Are extranonce ranges provided by the pool to prevent duplicate "guesses" by each of the two miners? What if I use no worker name instead? Can this then lead to a possible duplication of work in either case? What if I have 10 miners then? Still no chance of work duplication?

It seems that because I want to avoid testing the same block header twice for the solution that awards me 6.25 BTC, it could be advantageous to control the extranonce ranges for each miner I have pointing to the same BTC address here on ckpool solo to prevent any duplication of work. Is this already happening in the backend and I am just not aware of it?

Just trying to get a better understanding...

[o_solo_miner]

Hi All, I'm trying to wrap my little brain around the math behind a BTC block being generated. I believe I understand the basics. However, my question is related to the nonce. Let's say I have just one miner. When it starts to "guess" the  hash for my proposed solution by incrementing the nonce from 0 to n, followed by the extranonce (rehashing each time and comparing to target), the odds of any duplication of work is zero because I have just one miner.

Now let's say I have two miners here at ckpool solo, both pointing to the same BTC address, different worker names. Are extranonce ranges provided by the pool to prevent duplicate "guesses" by each of the two miners? What if I use no worker name instead? Can this then lead to a possible duplication of work in either case? What if I have 10 miners then? Still no chance of work duplication?

It seems that because I want to avoid testing the same block header twice for the solution that awards me 6.25 BTC, it could be advantageous to control the extranonce ranges for each miner I have pointing to the same BTC address here on ckpool solo to prevent any duplication of work. Is this already happening in the backend and I am just not aware of it?

Just trying to get a better understanding...

This is the solo.ckpool thread, please open a new thread in the main mining section.

To your question: No, the stratum send to each individual miner a unique number, that is for every seperate connection, your miner does not have to add a worker name on it.
Read the stratum docs.
https://bitcointalk.org/index.php?topic=557866.0

[hiaxis]

Hi All, I'm trying to wrap my little brain around the math behind a BTC block being generated. I believe I understand the basics. However, my question is related to the nonce. Let's say I have just one miner. When it starts to "guess" the  hash for my proposed solution by incrementing the nonce from 0 to n, followed by the extranonce (rehashing each time and comparing to target), the odds of any duplication of work is zero because I have just one miner.

Now let's say I have two miners here at ckpool solo, both pointing to the same BTC address, different worker names. Are extranonce ranges provided by the pool to prevent duplicate "guesses" by each of the two miners? What if I use no worker name instead? Can this then lead to a possible duplication of work in either case? What if I have 10 miners then? Still no chance of work duplication?

It seems that because I want to avoid testing the same block header twice for the solution that awards me 6.25 BTC, it could be advantageous to control the extranonce ranges for each miner I have pointing to the same BTC address here on ckpool solo to prevent any duplication of work. Is this already happening in the backend and I am just not aware of it?

Just trying to get a better understanding...

This is the solo.ckpool thread, please open a new thread in the main mining section.

To your question: No, the stratum send to each individual miner a unique number, that is for every seperate connection, your miner does not have to add a worker name on it.
Read the stratum docs.
https://bitcointalk.org/index.php?topic=557866.0

This was a solo pool question. I am mining on the solo pool. Regardless, I suspected the pool handled it with the extranonce values, I'm guessing by applying a different value to each miner to prevent duplication of work but I will check out the link. Thank you for sharing that.

[BitcoinSoloMiner]

"bestshare": 4086636637818.405
you got one?

[paid2]

"bestshare": 4086636637818.405
you got one?

Nope, we need one more digit, bestshare is only 4T