So it was the "actual Dragonmint" that found the block??? Seems very convenient. When you say "reported by Slush", is it really Slush? Or a conglomerate of business officials who control Slush Pool??? Very likely the latter, since Slush is a Corporate Entity at this point, who would like to get more users from the coattails of a new technology, from a vague company. At least, -ck announced they were "burning in" Dragonmint miners on his pool. He hit 2 blocks yesterday, and didn't boast this blatant claim, for the purpose of beggars marketing. I hit quite a few blocks on testnet with these quite some time ago, which rolled the version, confirming they worked fine. Halong have been sending half their burnin hashrate to slush and half to ckpool. This is, however, the first version rolled block on mainnet. Coincidentally ckpool.org found two blocks yesterday but neither were version rolled blocks as they were found by the ckpool.org core hasher who is running regular hardware. Slush did indeed find the first block then and, well, he runs a business in his pool and definitely uses publicity to his advantage - posts everywhere on twitter, reddit etc. What he did not advertise was that he was still using the early mask for rolling which we agreed to change quite some time ago, hence the *fff00 version that it rolled to, neither has he updated his documentation to reflect the BIP. Slush has a history of not really adhering to an RFC process, alas. It's also worth noting that 1 in 4 blocks solved by these will not have a rolled version anyway. I can tell you the factory floor is working its arse off trying to measure each board for quality, consistency, and reliability. First runs of silicon are always troublesome in this way and while there are thousands of these things already manufactured, it's taking longer than planned (what doesn't?) I'm not making any excuses for them as I've said before since I'm not invested in them, but I'm involved where possible to try and help this process on the software end. Small nm silicon is much more difficult to deal with than older technology. |
|
|
|
What do you guys think about joining this pool with 23th/s Bitcoin mining?
Go for it man. Support the smaller pools, with the closer community and support. One of the only pools with 0% fees and transaction fees included. You get paid more but less often than other larger pools, so if you're ok with that this pool should work well for you.  Downside of a truly zero fee pool is there is no incentive for the operator to run it and pay all the expenses, or to further develop it. So let's see... first pool to support asicboost publicly. First pool to support native segwit addresses. This all in the last 2 months. Yep, no development whatsoever. |
|
|
|
Cool.
Does that system also help the dust rewards issue that small miners have quite often?
Yes. There is no dust accumulation at all here as there is nothing left over from the block payout that happens instantly with the generation. The shares are basically accumulated block after block till they have a big enough dust payout and then they get it. |
|
|
|
CK I do have a basic understanding of your pool but how does it compare and differ from bitminter?
Well for starters there is no fee and this pool is more no-frills without much in the way of features for miners. The payout is not too dissimilar to PPLNS that bitminter uses, but because it uses generation payouts, you get instant payout as soon as the block is found rather than waiting for a payout. There is never any bitcoin stored in the pool's wallet waiting for you to withdraw because there is none. However because generation payouts add extra data to the miners, I limit payouts to 150 miners - the top 100 miners get a payout every block. The rest of the miners only get a payout when they've accumulated enough shares and have waited in the queue with the other miners. We also have a lower limit of 5640 satoshi for a payout which is the lowest anywhere meaning very small miners will eventually one day get a payout. Some of our smallest miners that toughed it out for almost a year got a payout today. |
|
|
|
Glorious luck. One block at 86.1% and one at an incredibly lucky 1.5% . Congratulations to all our miners and well done wetsuit! [2018-03-23 14:40:44.387] Possible block solve diff 3559100157956.788086 !
[2018-03-23 14:40:44.490] BLOCK ACCEPTED!
[2018-03-23 14:40:44.613] Solved block 514811 by 1EcH7pHYTHLo3cbdXfkf6e6Zh5JzCPGumc.300_1
[2018-03-23 14:40:44.613] User 1EcH7pHYTHLo3cbdXfkf6e6Zh5JzCPGumc:{"hashrate1m": "5.8P", "hashrate5m": "5.8P", "hashrate1hr": "5.82P", "hashrate1d": "5.8P", "hashrate7d": "5.64P"}
[2018-03-23 14:40:44.613] Worker 1EcH7pHYTHLo3cbdXfkf6e6Zh5JzCPGumc.300_1:{"hashrate1m": "1.33P", "hashrate5m": "1.33P", "hashrate1hr": "1.33P", "hashrate1d": "1.33P", "hashrate7d": "1.3P"}
[2018-03-23 14:44:35.388] Hash for block height 514811 confirms block was CONFIRMED
[2018-03-23 21:12:31.286] Possible block solve diff 7385912742826.858398 !
[2018-03-23 21:12:31.380] BLOCK ACCEPTED!
[2018-03-23 21:12:31.384] Solved block 514852 by 1EcH7pHYTHLo3cbdXfkf6e6Zh5JzCPGumc.wetsuit_jeffcolo1300th
[2018-03-23 21:12:31.384] User 1EcH7pHYTHLo3cbdXfkf6e6Zh5JzCPGumc:{"hashrate1m": "5.77P", "hashrate5m": "5.79P", "hashrate1hr": "5.82P", "hashrate1d": "5.81P", "hashrate7d": "5.64P"}
[2018-03-23 21:12:31.384] Worker 1EcH7pHYTHLo3cbdXfkf6e6Zh5JzCPGumc.wetsuit_jeffcolo1300th:{"hashrate1m": "1.37P", "hashrate5m": "1.38P", "hashrate1hr": "1.38P", "hashrate1d": "1.37P", "hashrate7d": "1.27P"}
[2018-03-23 21:28:20.341] Hash for block height 514852 confirms block was CONFIRMED
and http://ckpool.org/blocks/514852.confirmedhttps://btc.com/block/514811and https://btc.com/block/514852And a tweet to celebrate: https://twitter.com/ckpooldev/status/977301409379991553I also note these are the first blocks to have generation payouts to native segwit bech32 addresses  |
|
|
|
similar to what Canaan is doing by having kano.is as the factory default in their burn-in test process.
I figured something related to that is why Canaan don't talk to me any more. These days they only send me advertisements like any other customer. |
|
|
|
And wondering if the new guy 36JMs8rogpizjkkp6eeKMmm3SLbSNo5H9V with (approx) 2P and 200 workers (10th/worker) is Halong warm-up or a whack of T9's
Should we be watching for some 16Th/worker address?
Or is the chip burn in process like running a new race car engine at low rpm?
I'll leave that up to your imagination, but the Halong miners are T1s at 16TH each. |
|
|
|
The recent modest rise in hashrate is halong burn testing their new hardware. Here's hoping for a flood of T1 miners choosing this as their home ground in the future too |
|
|
|
Totally agree! Very cool indeed! Big props to Halong for supporting -ck's pool. It's truly Great to see these newer companies give
something back to the community.
It is indeed the community since there's no fee on my pool and only the miners on ckpool.org stand to benefit. Not directing more hashpower at a large pool is great for decentralisation. |
|
|
|
|
By the way anyone mining on ckpool.org would have noticed a transient rise in hashrate there today. This is burn testing the first batch of hardware.
|
|
|
|
So auto tune like the s-9 with no option to down clock or over clock?
Or do I misunderstand you?
Btw in no way am I voting for or against auto tune
There is a plan to implement options for tuning frequency or for power or efficiency but not in the first firmware. From what I've seen of the web interface it will be pretty sparse to begin with. I also believe that first silicon is probably going to be less efficient while they finalise manufacturing. |
|
|
|
what's the tl;dr answer to March shipping of these units? Weren't the first batch promised to ship by March?
Well I'm not privy to what's going on in the factory but I also never sign any NDAs so I can tell you there is a mad scramble to get hardware out ASAP and they've been leaning hard on me to try and make sure the first firmware it's being released with works as reliably and solidly as possible. There will definitely be firmware updates in the future but for now things seem to be pretty close. I got involved very late in the piece and I've worked very hard in the last couple of weeks but there are limits to my time and just what I can achieve to get working code out. One thing I have managed to achieve is to add tuning to the driver. The driver has a 5 stage tuning process to try and set the lowest stable voltage possible for minimal power consumption and then it tunes each chip individually to the highest frequency it will tolerate to try and optimise the hashrate. It also has a PID type fan controller to try and maintain optimal temperature with minimal fanspeed. There are a few emergency things included too in case of fan failure, chain dropouts etc. |
|
|
|
Hi Mr. Aegean Skipper, the block was found on this pool. I saw it on that day at https://blockchain.info/de/pools?timespan=8daysAnd ist seems like they are mining here because if not there would be no statistic. http://solo.ckpool.org/users/16GsNC3q6KgVXkUX7j7aPxSUdHrt1sN2yNBut I also have a question, maybe somebody else can help me with  I am buying hashrate to mine here from time to time. I see it as a lottery. I think this pool is very trustful but how can i be sure not be be scammed? Not by this pool but from people selling hashrate and submitting fake shares. I heard things like this happening on a miningpool with xmr. Can i really trust only the hashrate?  We have no daily Rewards here, so thats why i am asking... You can't fake hashrate if it shows up at the pool. However it is possible for rental hash to be withholding blocks meaning you can never find a block here - it is a limitation of rental hash that the rental service should be monitoring and responsible for, but they take NO responsibility on this. However over the years plenty of hashrate has found blocks with various rental services so probably good to stick with well known rentals. |
|
|
|
As the T1s with asicboost are about to start hitting the pools, I will be doing a brief restart of the pool within the next hour updating the parameters accepted by asicboost to stay in line with the recommended mask of version bits for them. We are already starting to see some of the hashrate on the pool as it is now being used for some factory testing already.
Restart completed with no downtime. Mine on. |
|
|
|
Edit: It just occurred to me that if someone lost control of their mining address' private key, they wouldn't be able to sign a message with it to prove that it belonged to them. Still, I'm curious to know how such an issue could be resolved here; it wouldn't be ideal to have someone's subsequent payouts sent to a black hole or a thief.
There's a cyclical problem there - if you can't prove you own the address, then even if the payout was just disabled, the pool could wrongly be withholding someone else's valid reward. Private keys are everything with address based payouts I'm afraid. Then again, private addresses with a proper bitcoin wallet are already far more secure than any web based online security. |
|
|
|
Sorry to rehash an old topic, but I've recently upgraded to a segwit address. If I send you a signed verification from my prior address are you able to merge the two?
If not, or it's work on your end don't worry about it. I literally have no hash power so the amounts are pennies, if that. Mostly I'm trying to increase my chances of getting in the payout pool 😁
Sorry no, it would need the pool to be literally taken down and manually edit its database before restarting it. It simply doesn't have that kind of functionality. Given the fee free nature of the pool I'm reluctant to add code for such a feature. |
|
|
|
Has Halong released their version of cgminer that supports overt asicboost? I'm curious to see how the finding the colliding work items has been implemented.
Not yet, no. They'll have 30 days from delivering hardware to release their software under the terms of the GPL (provided someone asks for the code who has the hardware.) If they don't release it after that time, I will myself anyway since I've been working on their driver for the last 2 weeks. |
|
|
|
So is the extra 2 TH/s in the DragonMint only due to the ASICBoost when compared to the S9? I am interested in seeing tests of these machines when they come in.
Asicboost does not in itself increase hashrate, it decreases power usage. If you use that advantage by making your silicon fixed to only work with asicboost, it affords you extra space on the chip which means you can put more hashing units on it. Strictly speaking the answer is no, but yes |
|
|
|
I have approx 1PH. Would it be easy to configure my Avalon’s to point to this pool? I e tried to read through as much as possible, but it seems different than other pools I’ve used. (slush and NiceHash)
You'd be most welcome here. There is no need for setting up an account or registering so it's actually easier. Just set the pool to pool.ckpool.org:3333 , the username to your chosen bitcoin address (use the same on all miners) and any password you like. |
|
|
|
|
Show Posts
