Just for fun, I pointed my small miner (150-175GHs) here to watch it move up through the ranks and see if I can eventually break into the top 100; however, I have a question about a difference I noticed after the most recent block was found:
As the Home page of the website states--or maybe an old ck post--it seems that since I'm nowhere near getting a payout yet that my HERP (or shares?) that I accumulated prior to the most recent block were added to my HERP on the Work page. For example, my HERP on the Work page is 8,700,000 higher than it is on the User page.
So... Will this I get this type of boost each time we get a new block, or is that only because I was probably still under the 0.00000500 BTC dust threshold at that time?
Also, I saw it mentioned in an old post about a Postponed count that increments each time you've been passed up for a payout. Is that still around, or was that functionality deprecated a while back?
Thanks in advance for the answers... Mine on!
Yes your herp gets added each time you don't get into the payout otherwise it's not fair since you missed out on a payment that block. The postponed data is still all there in the interface-less pool pages if you type in your btcaddress here: http://ckpool.org/users/btcaddress |
|
|
|
Hi, in the postponed list are numbers like that : 63,949,036.6,385 what does this mean ? Have an  ice day It means you mined the equivalent of 64 million diff shares but haven't mined enough to reach the payout list. |
|
|
|
Perhaps such things as suggestions/proposals should be accompanied by an incentive and/or working code...
#JustSayin'
Sure. For every byte present in the completed code, I will pay: 1 satoshi*0.003176*pool_hashrate*1.00038*last_block_diff*0*1.22819*total_users. Or I can add 1 PH to the pool  I code for PH on this pool |
|
|
|
-ck, could you add some more stats to the pool, such as "All time Diff"/"Last 10 blocks average Diff", "Total pool payout count", "30 day hashrate", "Hashrate within this PPLNS"(The user's hashrate, calculated by the users herp submitted within the '5x network difficutly' period)?
Would that bring us another 100PH of miners? Investing more and more time in this pool for free gets harder as time goes on if the pool doesn't take off much more. |
|
|
|
Congrats, everybody! That one was almost right on schedule.
Indeed. Now if only it actually worked like that, mining would be much simpler to explain to miners without needing a luck explanation... though no mechanism could make that possible and fair at the same time  |
|
|
|
[2018-02-28 10:45:40.381] Possible block solve diff 4659424304660.333984 !
[2018-02-28 10:45:40.528] BLOCK ACCEPTED!
[2018-02-28 10:45:40.537] Solved block 511309 by 1EcH7pHYTHLo3cbdXfkf6e6Zh5JzCPGumc.wetsuit_jeffcolo594
[2018-02-28 10:45:40.537] User 1EcH7pHYTHLo3cbdXfkf6e6Zh5JzCPGumc:{"hashrate1m": "1.83P", "hashrate5m": "1.86P", "hashrate1hr": "2.19P", "hashrate1d": "5.41P", "hashrate7d": "5.58P"}
[2018-02-28 10:45:40.537] Worker 1EcH7pHYTHLo3cbdXfkf6e6Zh5JzCPGumc.wetsuit_jeffcolo594:{"hashrate1m": "482T", "hashrate5m": "492T", "hashrate1hr": "498T", "hashrate1d": "463T", "hashrate7d": "403T"}
[2018-02-28 10:52:36.139] Hash for block height 511309 confirms block was CONFIRMED
\o/ How close to 100% can we get haha, 100.8% diff. Also a big 1.47MB block chock full of segwit transactions now that 2 major exchanges are finally doing segwit and bitcoin core 0.16.0 has come out with native segwit support. Full work and payout details: http://ckpool.org/pool/blocks/511309.confirmed |
|
|
|
Good morning,
It's almost a month I am hashing on this pool. Have mixed feelings and uncertain if it was the right decision. With a new block , hope in week or so, I would reach a payment 4-5 times less than i.e. I would be mining on nicehash...
Are these derp numbers are correct and shows the exact payout? I would be having 4 times more than current
Thanks you / regards
Yes those derp numbers are correct if we find a block at the exact moment you are looking at the derp value which changes by the minute. If it's less than you see on other pools it's because you haven't mined here long term, but you'll continue to get paid on subsequent blocks as well, even if you pull out now. It averages out over many blocks rather than per day or per week or month even. If our pool was 100x larger it would be different and you could do a daily comparison. Luck will be the main determinant of whether you'll end up getting substantially more or less on this pool than if you mined elsewhere, which is much more of an effect than the pool's fee which is zero. |
|
|
|
Great! So, does HERP reset after getting a payout so others can make their way to the top, or is that a stupid question?
No, because herp is the record of your contributed shares. |
|
|
|
1) So, I noticed the Active Miner page isn't always sorted by descending hashrate. Does it sometimes seem out of order due to those with less hashpower just having mined long enough to earn a spot that high or what?
2) Does being in the top 100 on the Active Miner page denote who will get a payout during the creation of the next block?
It is sorted by highest current 1 minute hashrate which is not shown on that page for brevity. Active miners does not correlate with shares contributed. Being in the top 100 share contributors guarantees a payout. |
|
|
|
I would have just wrote "No.", but I didn't want to presume to speak for ck.  Not really "speaking for him" when he's already made his feelings adamantly known on a subject (I'm just too lazy to search for a quote). Feel free to. Everyone knows my stance on shitcoins. The price for doing shitcoin work has remained 100BTC up front. These days I can't imagine anyone forking out the fee to pay it. |
|
|
|
Where can you see the work_diff data mentioned during the following section of the website: sqrt (MIN (share diff, network_diff) / work_diff) * work_diff / 2
I see DERP, HERP, shares, etc.; however, I don't see work_diff so I can run through few mathematical scenarios. Depends on your mining hardware and what diff it's currently mining at. |
|
|
|
The current dust limit is the smallest amount you can spend on the bitcoin network. However even if you get above the dust limit it means you will then get into the queue for a payout in one of the subsequent blocks, but you will eventually be paid provided you keep mining. The only caveat is that blocks are so infrequent at our current hashrate it could be a year or more before that happens unless through some miracle our hashrate gets much larger.
Correct me if I'm wrong but at the current hashrate plus difficulty you should be hitting around one block per month. That's about right. I said a year because he won't get into the first block found after breaking the dust limit and add the time taken to reach the dust limit. That and diff keeps rising. |
|
|
|
I hope this isn't a dumb question...
Going through some of my debug logs, I noticed that the generated stratum header has the version like this:
[2018-02-15 23:08:23.772] Generated stratum header 20000000ed37665c908b8f6b9120d09918afa1ef1c3bd3fa0024d3f700000000000000005fb360c99001606 f4f9aeb9293c5776d6e3e666adf0e6dacdbb9526ae3561fa95a86592f1761e9f800000000000000 8000000000000000000000000000000000000000000000000000000000
Shouldn't it be like this?:
[2018-02-15 23:08:23.772] Generated stratum header 00000020ed37665c908b8f6b9120d09918afa1ef1c3bd3fa0024d3f700000000000000005fb360c99001606 f4f9aeb9293c5776d6e3e666adf0e6dacdbb9526ae3561fa95a86592f1761e9f800000000000000 8000000000000000000000000000000000000000000000000000000000
I didn't see anywhere in the code where the bbversion was reversed. Unless I missed it. I did see some previous posts from way back where the block version is shown in the logs like my second example.
The version gets put in the header_bin as in the first example, not reversed. Raw block headers have the version reversed and when test hashed, produce the correct hashes.
Thanks,
-Ken
Take a look at some blocks to see what version looks like these days, eg: https://btc.com/00000000000000000077140243064000ba35b22d3e2440e936a722b90cd09365Compare with older blocks, eg: https://btc.com/00000000000000001ed61d4b7dd337c8eb1de0f21a0bd310a8733fb35f21991c |
|
|
|
"...provided you keep mining"
So, just to clarify, if I get in the payout queue after finding a block and then stop mining before the next block - Does that mean I'll evenly cycle through and be paid? Or do I have to keep mining to maintain the spot?
My understanding is that you pay out only 150 at a time and the smaller miners that have earned a payout go on a payout list - but when they actually get to the top of that list is just a matter of time... Or does it mean we have to keep mining to hold our place on the list?
If you don't keep mining when you hit the payout list there is a chance, however slight, that we end up having a block that is over 500% diff and then you won't get anything whereas continuing to mine will maintain your spot. |
|
|
|
Thinking of pointing my new miners over here. They aren't very big, though. I am trying to see if it is worth my effort. What is the current dust limit to get on the payout list?
And just to confirm my understanding after reading through these last few pages : if I contribute shares and earn above the payout threshold, as a little guy I go on the list to eventually get paid, even if I stop mining here in the interim?
The current dust limit is the smallest amount you can spend on the bitcoin network. However even if you get above the dust limit it means you will then get into the queue for a payout in one of the subsequent blocks, but you will eventually be paid provided you keep mining. The only caveat is that blocks are so infrequent at our current hashrate it could be a year or more before that happens unless through some miracle our hashrate gets much larger. |
|
|
|
|
My bad sorry, bitmain warranty is now called myrig. BTW I have absolutely no financial stake in the company whatsoever beyond being paid to do cgminer driver cleanups so I have nothing to gain by staking my reputation on them.
|
|
|
|
|
I've been hired by bitmain warrantymyrig, I know the person by name personally who hired me, the scope is extremely flexible just to clean up whatever's involved with the driver, my reputation speaks for itself, the device is definitely real but I couldn't possibly speak for timelines of production and guarantee delivery ffs that has nothing to do with me.
|
|
|
|
I'm now renting 82T for about 72 hours using port 3333. I did see the too low error message for about 30 minutes, but now everything has level out.
The default port should scale to any hashrate. Port 4334 won't go below 1 million and is purely for shit rental services that limit connections to 1M+ |
|
|
|
Just out of curiosity why did the difficulty drop from 190' to low 180's? Also with the group best share it has not changes for weeks. Are we trying to find everything in between? I have heard that best share dose not mean much but just looks like we are stuck.
Bitcoin network difficulty rose to over 3 trillion, therefore our percentage of diff dropped. We simply haven't found a higher share in that time. |
|
|
|
|
Show Posts
