Pages:
Author

Topic: [∞ YH] solo.ckpool.org 2% fee solo mining 256 blocks solved! - page 79. (Read 89163 times)

hero member
Activity: 504
Merit: 1065
Crypto Swap Exchange
no block found in Blockparty Run 27, now plan the next one

here ist the topic for our Blockparty Run 28

##############################################


Hello Willi  Smiley

Hope you are doing good !

Any update about the next run ?

member
Activity: 60
Merit: 20
I don't understand why my ckpool shows different parameters than the Antminer:

In Antminer the following parameters come out:
[minerPool] [minerPoolTip]   Diff   Priority   Accepted   DiffA   DiffR   Rejected   Stale   LSDiff   LSTime


But none of this matches CKPOOL, anyone who can make me understand this, also it would be nice to know what each Antiminer parameter indicates, I find information but it is not well explained.

Thank you very much in advance


I do not use Antminer pool and Antminer mining program. I just guess.
Diff  may be network difficulty.\
Proority  ?
Accepted  may be  how many numbers of acceptance of your submit to the pool.
Rejected  may be  how many numbbers of rejection of your submit to the pool.
DiffA:  sum of all difficulty of accpted submit to the pool.
DiffR:  sum of all difficulty of rejected submit to pool.

Actually useful information for a transparency for pool and miners, I believe, are:
Network current Difficulty, eg 36.8T
Last accpeted submit's difficulty by the pool, and when
Maximum accpeted submit's difficulty by the pool, and when
Number of accepted submit.
Number of rejected submit.
Other statistic?
jr. member
Activity: 85
Merit: 1
I don't understand why my ckpool shows different parameters than the Antminer:

In Antminer the following parameters come out:
[minerPool] [minerPoolTip]   Diff   Priority   Accepted   DiffA   DiffR   Rejected   Stale   LSDiff   LSTime


But none of this matches CKPOOL, anyone who can make me understand this, also it would be nice to know what each Antiminer parameter indicates, I find information but it is not well explained.

Thank you very much in advance
jr. member
Activity: 37
Merit: 5
The link you referred to means "SOLO mining on an own full-node". In this case you are using solo.ckpool.org and you can use a bc1q... address of course. Just look at so many posting, a lot of users mining on soloCK pool with Bech32 address. In case it would not have been supported, you would have received an error message Wink All good, you are ready to mine Wink
All right, thanks a lot for your reply!
full member
Activity: 582
Merit: 149
I copied and pasted the url.  But, for the username.  I don't know the worker name(s), so I just put my BTC address; since it said I could do it without the worker name(s). Then I put x for the password.  It still shows inactive.

Make sure you don't have any extra characters or spaces in your BTC address.

Also once you save and if you have it setup correctly in the Apollo Gui then make sure you click on Miner and then click start and you should be mining.

If not then it could be your network / router blocking you from mining or your apollo is not working correctly in which case you should head to the Apollo support thread here in the hardware area https://bitcointalksearch.org/topic/official-futurebit-apollo-btc-softwareimage-and-support-thread-5340015
hero member
Activity: 630
Merit: 731
Bitcoin g33k
The link you referred to means "SOLO mining on an own full-node". In this case you are using solo.ckpool.org and you can use a bc1q... address of course. Just look at so many posting, a lot of users mining on soloCK pool with Bech32 address. In case it would not have been supported, you would have received an error message Wink All good, you are ready to mine Wink
jr. member
Activity: 37
Merit: 5
When I point my USB-Miner (GekkoScience Newpac) to solo.ckpool.org and I'm running cgminer as mining-software, is it technical possible to use a Bech32-adress as payout-adress Huh

I am refering to this post https://bitcointalksearch.org/topic/solomining-with-cgminer-against-bitcoind-bitcoin-core-v0181-5373190 where user 100knot2dae said cgminer does not support Bech (bc1...) addresses for solo mining.

So this command in cgminer would not work?!
Code:
sudo ./cgminer -o stratum+tcp://solo.ckpool.org:3333 -u bc1q-my-btc-payout-adress.gekko -p x --suggest-diff 256 --gekko-newpac-freq 400
newbie
Activity: 2
Merit: 0
New to this.  Bought a futurebit apollo btc to try it out.  It keeps showing inactive for my status connection to ckpool.  Does anyone know why?

You must have your pool configured incorrectly.

Use this as your pool url:

stratum+tcp://solo.ckpool.org:3333

Then enter your BTC address . miner name... For an example on the Username if my worker name was ApolloBTC01 I would enter  bc1qzmntuax0kgys5elzwcn6sj04yxxxxxxx.ApolloBTC01

And enter a lower case x as the password.


Then save and restart the apollo and you should be mining.




I copied and pasted the url.  But, for the username.  I don't know the worker name(s), so I just put my BTC address; since it said I could do it without the worker name(s). Then I put x for the password.  It still shows inactive.
jr. member
Activity: 85
Merit: 1
Looking through the logs I can see one miner submitting mostly rejects - all below target level, suggesting dodgy firmware on his hardware, but I don't see anything else untoward. That might be enough on its own. I suggest each individual user check their own stats and see if their hashrate at the pool reflects their hardware - ckpool reports hashrate based ONLY on accepted shares.


Reviewing one of my miners, he has been mining in CKPool for 18 days and yields the following data:

Diff   Priorit   Accepted         DiffA             DiffR   Rejected Stale           LSDiff           LSTime

105K     0         458879 38400602087   19012175     227         22           104698            0:00:00

Would it be possible to get a screenshot of what my miner is doing?

I try to look for information in Spanish about what the miner actually does, what data it takes into account, the Hashes it sends but I can't find any information about this.



hero member
Activity: 630
Merit: 731
Bitcoin g33k
Solo miners - Attention

If you are interested in group based solo runs, you are welcome to join the BLOCK SOLVERS group



Stake is only 0.001 BTC, we rent hashpower 2-3 PH/s and send it to soloCK pool. The motto of this solo mining group is: participate cheaply and regularly with the hope of mining a block and collecting the reward.

All info can be found in the citb0in Solo-Mining Group - BLOCK SOLVERS thread. Join now, may the luck be with us  Wink

jr. member
Activity: 97
Merit: 5
Looking through the logs I can see one miner submitting mostly rejects - all below target level, suggesting dodgy firmware on his hardware, but I don't see anything else untoward. That might be enough on its own. I suggest each individual user check their own stats and see if their hashrate at the pool reflects their hardware - ckpool reports hashrate based ONLY on accepted shares.

Thank you for the info ck. That's good to know. So if the difficulty is too low on a particular miner, even one with a relatively low hash rate, it's possible to rack up a large amount of rejected shares. That's good to know!
full member
Activity: 582
Merit: 149
New to this.  Bought a futurebit apollo btc to try it out.  It keeps showing inactive for my status connection to ckpool.  Does anyone know why?

You must have your pool configured incorrectly.

Use this as your pool url:

stratum+tcp://solo.ckpool.org:3333

Then enter your BTC address . miner name... For an example on the Username if my worker name was ApolloBTC01 I would enter  bc1qzmntuax0kgys5elzwcn6sj04yxxxxxxx.ApolloBTC01

And enter a lower case x as the password.


Then save and restart the apollo and you should be mining.


newbie
Activity: 2
Merit: 0
New to this.  Bought a futurebit apollo btc to try it out.  It keeps showing inactive for my status connection to ckpool.  Does anyone know why?
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Looking through the logs I can see one miner submitting mostly rejects - all below target level, suggesting dodgy firmware on his hardware, but I don't see anything else untoward. That might be enough on its own. I suggest each individual user check their own stats and see if their hashrate at the pool reflects their hardware - ckpool reports hashrate based ONLY on accepted shares.
jr. member
Activity: 97
Merit: 5
Question for you all. I was looking at the solo pool stats and noticed the number of rejected shares versus total shares accepted.

"accepted": 24575964250308, "rejected": 8543041616789,

Is it normal to have such a high ratio of rejected to accepted shares? It's almost 35%.

Just curious...



It's not normal, it's likely shitty asic firmware. If the reported hashrate is still fine and consistent with the hardware then just ignore it, it means it's submitting shares below difficulty or something stupid.

So there's enough shitty firmware out there running in miners solo mining on this pool to cause over 1/3 of the total shares submitted by the entire solo pool to be rejected? That seems crazy! I could understand if a small portion of the miners connected to the pool had that issue but over 1/3 of our shares submitted are being rejected. Is this due to rentals maybe?

I'm not an expert by any stretch in this area which is why I'm trying to understand more about it. It just seems like a very gross inefficiency if 1/3 of our total shares on the solo pool as a whole are being rejected.
It's probably one miner, likely a rental related phenomenon. I might investigate.

Thank you ck. I'm curious what you find. Looking at it today, rejected total seems to still be ticking up quickly. If our average hash rate since the last block was let's say 15PH, it's concerning if we, as a "pool", had 5PH worth of those shares rejected. Something just doesn't seem right but again, I'm not an expert in this.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Question for you all. I was looking at the solo pool stats and noticed the number of rejected shares versus total shares accepted.

"accepted": 24575964250308, "rejected": 8543041616789,

Is it normal to have such a high ratio of rejected to accepted shares? It's almost 35%.

Just curious...



It's not normal, it's likely shitty asic firmware. If the reported hashrate is still fine and consistent with the hardware then just ignore it, it means it's submitting shares below difficulty or something stupid.

So there's enough shitty firmware out there running in miners solo mining on this pool to cause over 1/3 of the total shares submitted by the entire solo pool to be rejected? That seems crazy! I could understand if a small portion of the miners connected to the pool had that issue but over 1/3 of our shares submitted are being rejected. Is this due to rentals maybe?

I'm not an expert by any stretch in this area which is why I'm trying to understand more about it. It just seems like a very gross inefficiency if 1/3 of our total shares on the solo pool as a whole are being rejected.
It's probably one miner, likely a rental related phenomenon. I might investigate.
jr. member
Activity: 97
Merit: 5
Question for you all. I was looking at the solo pool stats and noticed the number of rejected shares versus total shares accepted.

"accepted": 24575964250308, "rejected": 8543041616789,

Is it normal to have such a high ratio of rejected to accepted shares? It's almost 35%.

Just curious...



It's not normal, it's likely shitty asic firmware. If the reported hashrate is still fine and consistent with the hardware then just ignore it, it means it's submitting shares below difficulty or something stupid.

So there's enough shitty firmware out there running in miners solo mining on this pool to cause over 1/3 of the total shares submitted by the entire solo pool to be rejected? That seems crazy! I could understand if a small portion of the miners connected to the pool had that issue but over 1/3 of our shares submitted are being rejected. Is this due to rentals maybe?

I'm not an expert by any stretch in this area which is why I'm trying to understand more about it. It just seems like a very gross inefficiency if 1/3 of our total shares on the solo pool as a whole are being rejected.
jr. member
Activity: 85
Merit: 1
Question for you all. I was looking at the solo pool stats and noticed the number of rejected shares versus total shares accepted.

"accepted": 24575964250308, "rejected": 8543041616789,

Is it normal to have such a high ratio of rejected to accepted shares? It's almost 35%.

Just curious...



It's not normal, it's likely shitty asic firmware. If the reported hashrate is still fine and consistent with the hardware then just ignore it, it means it's submitting shares below difficulty or something stupid.

Ck, I think you are referring to the Ckpool Pool data, now marked as rejected 8544606234606 and accepted 25021741637908.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Question for you all. I was looking at the solo pool stats and noticed the number of rejected shares versus total shares accepted.

"accepted": 24575964250308, "rejected": 8543041616789,

Is it normal to have such a high ratio of rejected to accepted shares? It's almost 35%.

Just curious...



It's not normal, it's likely shitty asic firmware. If the reported hashrate is still fine and consistent with the hardware then just ignore it, it means it's submitting shares below difficulty or something stupid.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
I would add that CKPool has been almost two months with an average of 19P more or less without hitting a block, could it be due to the increase of the difficulty in these last months?

I think that 19P is like 190 asics of 100Th/s and it scares me to believe that it takes so many machines to not hit a block in 2 months.
Nope, it's just because 19P is a piddly small amount of hashrate. The difficulty increases have only been modest recently.
Pages:
Jump to: