Only 'backup' notification I can think of would be if NH lets the person who is running the rental know they found a block via a stats page or whatever. I've never seen a reason to rent so I have no idea if NH does that.

For the past several years all of the major miner manufacturers have shown zero interest in making small, quiet miners. Only Sidehack's R606 fits that category and it tops out at 1THs.

That said, Sidehack is working on a new faster (and still quiet) miner but so far has published no specs on it aside from having a target power consumption of around 500w vs the R606's sub-100w.

Bet it is the top board that's dead, right? That is the one I had trouble with on 3 of them. Only 1 still running and has 2 boards working only because I salvaged a replacement board from one of the others.

I've had R4's from batch-1 through their last (6). None have that fan so it has to be a mod and is located to blow over the PCIe power plugs & Vcore regulator areas. Not a bad idea, but I've never had any problems related to that area getting too hot.

 
Sounds like these will be quite nice!
Also expanded on earlier reply

Heh heh!
Actually no, quite the opposite. The substrates (heat spreading ceramic parts of them under the emitters) of around 90% of all high power LED's produced in the world are produced in Taiwan under our patents on the laser drilling process used to put vias in them.  

My company SLI introduced the process to the world in late 2007. In 2006 I was in Taiwan at THEIL (Tong Hsing Electronics Ltd.) installing some new equipment when Management requested I sit in on a strategy meeting with one of their customers (LumiLEDS). LL wanted to know if there was a way to make smaller vias in ceramic to increase emitter density on the chips. I though for a couple seconds then answered with a qualified, "yeeesssss, but I need to do some testing on an idea for doing it..."

You could almost hear the wallets snapping open....
When I got back home we got dev money from THEIL and the rest is history  
https://www.synchronlaser.com/processing-ceramic-substrates-2/
https://www.synchronlaser.com/fiber-lasers-scribing-of-ceramic-wafers/

Just so happens that industrial fiber lasers were starting to enter the market with enough power and near perfect Gaussian beam shape that could do the trick provided there was a way around the problem of the fiber laser wavelength (same as YAG) having very poor absorption in Al₂O₃ and AlN. As in over 85% of the energy just passing through with little to no effect on the materials. I solved that and pattern density increased 3-6x, SLI got the patent on it, in return for their funding development we gave THEIL exclusive rights to use it for 2 years with systems we built for them (to-date now over 45 systems at THEIL alone). Since they also provide services for Cree and all the other major LED mfgrs in the world within a year HP LED's were popping up everywhere with prices dropping like a stone.

Are all miners on the controller the same type? Must be all 841's. Maybe the others are 821's? You cannot mix them on 1 controller.

As for troubleshooting - um, you *did* look at page-1 here right?

@JakobFugger, Actually he was the Egyptian god of mummification and the afterlife as well as the patron god of lost souls and the helpless. He is one of the oldest gods of Egypt, who most likely developed from the earlier (and much older) jackal god Wepwawet with whom he is often confused.
Just clearing that up...

As for the malware, not surprised at all. As others have said, be very careful when surfing the 'net and along with a good AV always use a JAVAscipt blocker such as NoScript.

Query: Who's LED's are you going to use? Cree? LumiLEDs? Osram? Nichia?

^^ So spot-on, one of the few times I quote in entirety. Merit given

Or... Talk to Steve the Global Marketing Director (afaik) at Canaan and strike up a deal. He's here in the Forum and quite approachable. Sounds like a perfect Marketing tool for them - out of the box tweakability. (like Avalons *used* to have...)

Prior to their A10xx on up there was no real need for 3rd party FW because they implemented quite a sizeable laundry list of things you can tweak.

A10xx on up uses what they call FMS vs straight-up cgminer/BMminer and previous OpenWrT/LuCi. Not sure how much of the API is directly supported but - it still has exceedingly good hooks for gathering data and tweaking performance down to the chip level.

Problem is, while basics for setting freq, fan speed, Vcore and a few other bits of Kano's cgminer API is of course supported Canaan has been less than helpful giving us back our switches... Speaking of which, even Kano with his very good dev contacts at Canaan has not been able to get much out of them about what what all the API or lower-level FMS switches are. Think you folks could strike up a deal with them?

There are no "owners" of the darknet. The DN is simple a shit ton of IP addresses to sites that are not registered with any (legal) DNS meaning you have to know the exact ip address to access sites there.

Now arresting owners of DN sites, thass another matter

No one is bidding for a very good reason: Those sellers are looking to ripoff un-educated buyers.

At best they are worth maybe $20 w/o PSU and perhaps $40 with a PSU. Plus shipping of course.

This most likely belongs in the Pools area.
Setup sub accounts in the pool is best. However, not all pools allow it.

See my latest Node size post re: more advances in the pipeline regarding things that will increase performance.

Further reading to prove my point about using just "node size" now being a pointless measure of what a chip's performance can be and why the Semiconductor industry working on a better descriptor:

On replacing Si with Ge as the semiconductor

On using entirely different principal of switching transistor operation

On using an entirely different type of transistor geometry vs current FinFET's

The 1st 2 papers are not exactly recent but still very valid examples of what is being worked on. The last paper is from last year.
All are very good reads that give a lot of insight into how chips operate and are made along with the difficulties that have been mitigated to be where we are currently at and those that have yet to be overcome to advance further/faster.

Excellent. Now if we can just get some input from folks at poolin and Nova we'll be getting somewhere.

re:balls, thanks but not really. I play the long game and just have a lot of patience. Also helps that the majority of my farm is at work where I get the power as part of my compensation.  

Having been mining there since late 2014 I've been paid a fair bit over 100 BTC  - and as an aside plowed the vast majority of that back into the farm for upgrades/expansion over the years... All in all, excellent track record along with a pool op who has impressive IT chops with a passion to do things (programming/testing) right and who is willing to engage with the pools users is what keeps me there.

Assuming the cord on the burnt brick is long enough cut it off at the brick and wire it to the PSU leads. That's what I did for powering my ancient 10GH Jalapenos.

As I said elsewhere bare-bones ckpool with minimal logging for the front-end can be fine for a solo pool where a single miner takes all the risk regarding what they point at it but ckpool can also supply all sorts of performance data about the miners connected as well. That is, provided pool operators chooses to extract, archive, and use it not only to analyze events after-the-fact but also catch/flag them as they are occurring. For a shared rewards pool I feel that should be paramount. Kudos for doing that or at least thinking about it.

Best example of a worst case 'why' is of course the infamous Slush kerfuffle a couple years back.

Ja. The "other" thread went off the rails a while back. I tried to steer it back on point (concerns about the back end) to no avail...


*That* ^^ is what I for one was looking for. Some assurance that the pool is not going to just be running mostly on autopilot with little to no performance logs being kept (and checked) as a certain someone apparently thinks (or now, hopefully - thought - ) a shared rewards pool should do.

Yep.

Fun fact: the 1st transistors created in 1947 were made from Ge and it is still the preferred material for high-radiation areas such as in space because Ge is pretty much immune to lattice damage caused by high-energy particles and gamma rays.

In the early 1960's Si really took over not only because its temperature drift coefficient for switching levels (digital on/off thresholds) and bias needs for analog applications is far more stable over temp changes but also because it can withstand far higher temperatures before thermal avalanche occurs and Si has much lower current leakage than Ge. Those 3 points are what is continuing to be roadblocks to using it.

edit: Found a good article from 2016 on the push to replace Si with Ge

As in f2pool and Antpool mining 4 empty blocks in a row in 2015(?) that were off-chain thanks to their jumping the gun to be 1st out the gate to start a new (un-validated) block by using results from their previous also empty and un-validated block?

Turns out that someone else had won the Orphan race for that 1st empty & un-validated block that Antpool & f2 had based their chain on.... Oops. Thanks to the back-end monitoring that Kano has he was very quickly alerted to the issue and contacted Antpool ops about it who then quickly relayed the info to f2pool who promptly switched tracks back to the valid current chain and of course invalidating the off-chain blocks they found.

Kano.is uses a modified version of ckpool as its front-end in conjunction with KDB which also directly monitors the network via bitcoind. Most of the code is out there in gits. Mind you his changes to ckpool are not there despite him being one of the major developers of it (the 'k' stands for Kano) thanks to a certain someone kicking him off the ckpool github due to irreconcilable differences in their views on proper coding/testing & pool financial safety. Anywho, the core code is there for anyone to peruse & use but Kano's mods to ckpool and updates to his KDB remain private. Since he does not distribute his changes that does not violate the GPL .