Not already supporting gridseed orbs/blades may have been something you'd want to have disclosed before selling them to people who buy them for their blades. 

In fact, any limitation over some of the other RPi distro's out there, like the lack of API access is actually quite important to a lot of us.

You said you'd be adding in support for blades tonight, I'll be looking for it.

Jesus, do you know how many people have been looking for this datasheet all over the internet? Where did you find it? This part is used on GPUs as well, and that community has been looking for it too. As I understand it, the part is covered by an NDA, and is part of the reason the datasheet has been hard to find.

Back up link to Datasheet

Also: http://www.upi-semi.com/sales/sales.aspx to purchase a replacement. Order a sample, or contact one of the companies somewhere in Asia. I'm sure at least one of them will do business with you.

Everything is fine until it's not. The factory need only keep it working for as long as the warranty period lasts.


That is one of their functions, yes. Switching pools, temporary disconnections, even coin switches might cause current surges. Eventually, that is going to kill some parts. With the incredibly rapid pace of profitability, I imagine these will need to be running a long time to make back their cost. That is a consideration for me, anyway.

I've had a soldering iron in my hand since before I was of a reasonable age to be using one. That said, I grew up working on electronics long before SMD were available, let alone mainstream. Back then, when you bought a 'computer' it was more like buying an unassembled arduino kit now. You built the whole thing, soldering your components by hand, then wrote your own programs in assembly or copied it out of some magazine.

My point is, I have plenty of experience working on circuit boards, just not with SMD components. I'm quite sure it isn't beyond me. The time I was speaking about with the SMD I was working on was a decade or more ago. Back then I couldn't have purchased new solder tips, let alone a rework station even if I had known they existed. Most jobs, including this one are tremendously easier with the proper tools -- and less caffeine.


You might consider adding a ferrite core on the supply wires if you opt with using resistors on the board. Just bridging with solder could add a considerable amount of inductance, and causing EM noise problems down the road, and I believe that to be a bad idea. This may not present as a failed blade, and may instead just limit your ability to ramp up the proc frequency because of HW errors due to unstable supply.

You still need to reattach them with something. You can't solder the pad underneath with a pencil, I think. I was looking at my blade today, and that damned resistor is so tiny.

The last SMD IC I tried to replace (not mining related) was a damned disaster. I ended up using a razor blade to carve the solder out between the pins because they kept bridging.

I was thinking about the power jack problem, 8 pin EPS connectors are (unoffically) rated to >300w. An extension cable would provide the connectors needed, and one would only need to cut it in half and creatively solder the pig tail to the board properly. I don't suppose it would be pretty, but GC should really have equipped the board with it in the first place. That should comfortably supply 12.5A to each blade. PCIe would also work, but should really connected observing the ATX spec (3 +12v, 5 GND), in case someone actually plugs a PCIe cable into it to power it, and that's rated to 150w. Using either would stop the melting power connectors, I suspect.

It's not entirely clear what you are asking, but it sounds like you didn't read through the thread.  

You want to O/C your blade? Stop skimming and read through the entire thread. I've read all 17 pages many times, you can do it at least once.

Those of you doing mods, are you using rework stations or a pencil iron?

Only if you want to fry your power MOSFETs in short order. It's not the set speed that damages the components, it's the current your trying to push through them. AFAIK, 43k is the highest anyone has gone, and that creates enough heat to melt the power jack.

So many people just soldering crap on and off, not even really understanding what they are doing, or the consequences of it. Makes me wish there was a root privilege lock out for hardware.

Sold out, but thank you. I took advantage of a similar offer.

At current BTC prices this is almost $700. 

I'm Interested in purchasing a 5.2MH/s Gridseed blade.  

Offering 1.0 1.15 BTC, must include 2 Day shipping, and I'll take care of any escrow fees.

Found one.

I specifically addressed this problem with you in response to your post in my rep thread before all the trouble I had. It sounds awfully familiar to how my prices declined so much, doesn't it?  

The 'problem' is that you rented my rig for 72 hours for less than the price of 1 hour due to some pricing 'glitch' on leaserig. Of course I cut your lease off. You got 7 hours out of me at a rate of .00013333/hr. You paid in total 0.01220000 BTC for 72 hours. My normal rate (this week) for 72 hours is .97250000 BTC, or .01350000/hr. The power used to run and cool the rigs for the time you had them costs more than what you paid. So no, there is not going to be a refund.

Since all the changes to Leaserig, I am unable to actually cut your lease short or even cancel it. Instead I've been forced to disconnect my rigs from leaserig for the time being. I don't know what the hell is going on with their service, but this is the second time I've been mining for customers at my expense, to the tune of approx .5 BTC loss this time.

OK, So can anyone explain to me how I adjusted my stated hash rate from 31.0 to 30.5 (to cover some minor fluctuations) and my price went from .00133534 to .00013333??  

I didn't see any sort of major price change at all when I made a change to the hash rate. I go about my business, and nearly a day and a half later I find that I've been paying other people to mine with my equipment because my prices went down by 90%. This is the 2nd major rip off I've received due to some glitch on Leaserig.

Is it personal? I have to question if someone went into the DB and edited my prices because I sure as hell didn't go on a 90% sale myself.

Further, there is no way for me to cancel the existing 72 hour lease at this point. I can't do 'negative' extensions, I can't disable the rig with an active lease, you've essentially trapped me. I've killed the proxy for now, but I've no way to actually manage my own leases because of your changes.

The guy rented my rig for 72 hours for less than the cost of 1 hour, and got 7 hours of his time. I'm not going to issue any refund to him. Another guy before him got 20 hours of mining time for less than the cost of an hour.

First the captcha bug, then the phantom free lease extension, and now the glitched prices. WTF maiviator?

Edit: You know, I want to thank cryptoprime for shooting me an email. I go to bed last night, take my kid to a birthday party today, try to handle some chores on the weekend. I don't have time to stare at the screen 24 hours a day and watch for stuff like this. No less than 27 hours of rental went out and not one customer says to me: hey man, looks like something might have happened your prices are ridiculously low. If I hadn't gotten an email from him, it might have been another full day before I caught this. Thank you Crypto.

Shouldn't it really be up to me to decide how I should respond to customers' posts in my own rep thread? I see what you are getting at, but if a customer actually takes the time to read through my thread, and based on that one unanswered post decided not to rent my rig -- well that's on me. I consider the issue settled, and didn't want to drag the details of the drama into my thread. My customer has no more cause for complaints, and I didn't think bitching about him getting so much free time off me was really worth adding to the thread. The whole situation was irregular, and I'm pretty certain only happened in response to a glitch on Leaserig's side, as leaserig said my box was still being rented that entire time. However, what's done is done, and there is no point in dredging it up.

To be perfectly honest, maybe you should spend your time fixing your website instead of poking around in people's rep threads telling them what they should respond to. BTW, your recent change to the "Modify renting plans prices by:" is broken. It still requires you to use .98 instead of 98, but the insertion of '100' in there (instead of 1.0) implies otherwise and is confusing.

This is bullshit, and another example of LR getting too involved in the process. You posted in my rep thread a couple hours after the renter with a screenshot of the speed graph, which tells nothing about what the problem actually was.  

I handled that issue entirely through email, and the renter never deleted his post, nor did he indicate that he got 12 hours extra of free time on a 3 hour lease due to some problem between LRP and Leaserig.net, that was only resolved when I repeatedly enabled/disabled my rig through the website. *I* couldn't even change the damn pools on the website, and resetting the proxy had no effect on this. My rigs were working fine, and I manually changed the pools on them to a multipool while I worked out the problem on the website.

It's a *rep* thread, not a support thread. 99% of issues are handled via email, if for no other reason than it being faster. The only reason people post support issues in the rep thread is because they have no other way to make contact with providers because of a (IMO) long standing design flaw of leaserig.net. Common sense says there should be a contact form for renters to send providers messages without exposing the providers email address unwillingly.

As to the changes to the website, I like the red header. I still think all the extra icons you are adding look like crap, make it more cluttered, and more confusing.

Cryptsy provides this service, but also charges me a withdrawal fee. I agree with you in that it would be a massive headache to try to watch hourly prices and exchanges. I'm not terribly fond of the idea at all.

I do this for income, to pay back the loan I took out to purchase the equipment. Until LTC ends up on Coinbase, BTC is unfortunately the only thing I'm genuinely interested in getting paid. The more steps in between that and what my customer wants to pay, the worse it is.

In the end, I'm left wondering why the burden of exchanging coins should be put to the providers? We are priced in BTC, the payments are pegged against their exchange value to BTC, and payments are tracked in BTC equivalent. It seems a lot more straight forward to let customers do their own exchanging to BTC from DOGE/LTC/Whatever and leave it at that. Accepting DOGE has been a headache I don't need, but I do it to stay competitive. I don't like the extra fees, and I don't like all the manual steps needed to get paid. IMHO, Leaserig should have stuck with BTC and left it alone.

Are the amber color and the icon really needed? Shouldn't just the amber highlight suffice as notice enough?

Aesthetically, it looks cluttered. The LRP and */! icon should be right justified, or in a separate column on the far left in front of 'Provider'. For that matter, most text is left justified, and should be centered. 'Available! Hire' Should just read 'Hire' in larger font. Obviously, it's available.

To alleviate payment type headaches, perhaps you should consider something like the 'multipool.us' approach; Allow people to pay in multiple types, but offer people the option to either keep the payment in the coin it was paid in, or Leaserig will convert it to BTC for a small fee and pay it out that way. Since you are pushing the hourly payment approach, that puts you squarely in the middle of the transaction already. In for a satoshi, in for a BTC, right?  

Also, I have historically under rated my rig by 1-2%. It's nice to finally see some kind of differentiation to providers that consistently over rate themselves.

Thank you for extending the session time.  

This morning I had an interesting problem. Lease rig failed to switch my rig back over to my default pools when the last customer's lease expired. It continued to mine for that guy for 9 12 hours? The lease rig website graph indicated that my rig was actually still rented out, which it wasn't. The configuration page showed the rig as having been disabled, it wasn't -- or at least I didn't do it. It wasn't until I re-enabled, disabled, then re-enabled again AND added my own pool that leaserig website finally showed the rental as having ended and the hash rates stabilized.

My customer has indicated the rig stayed connected to his pool (on my dime) up until a few minutes ago when I pulled the plug.

The red lines indicated the paid for period. At some point into the second fake rental, my connection to lease rig was being dropped every few minutes, but the hashing was steady.  

OK, I think I found the problem.

On the provider log in, intentionally fail the captcha the first time, you'll get an error message "Error, wrong captcha". Hit the back button, it should take you back to the log in page you were just at. Now, try to log in normally, doing the new captcha correctly. Failed? Hit back, try it again. Still failed or does it work? Because for me, it doesn't no matter how many times I try. If I fail the captcha for the first time, I can't log back in. I have to actually navigate away from from leaserig, then go back to the home page and click the provider link again.


Am I mad bro? Yea, I'm mad. I get emails from users complaining it's not hashing right (usually it's the pool or diff they selected), and I can't log in to look at anything to fix the problem. It's happened to me several times, and it's frustrating. Now that I think I've identified the problem, I can work around it. I still think the captcha is a joke, and completely unnecessary.

I'm not 'trying to hard'. I'm simply inputting the characters as I see them like everyone else. Discounting leaserig, I have problems less than 1% of the time with captchas.

Now, Miaviator is being quiet on the issue, but I recognize when a change has been made. Maybe you just aren't logging in at the same times I am. Three times I've had significant difficulty with captcha on his website, and each time was after an update was released. After some length of time, the problem was fixed. In any case, I'm not the only one complaining about it and it's completely unnecessary for regular logins. Of all the changes being pushed out, I don't understand the resistance to this particular QoL change, which is really just a rollback. Under the previous owner, I only ever had an issue logging in once, and that was due to the provider & customer logins being different and me not recognizing that. Since Miaviator's team has been implementing changes, the log in policy has basically been "Having a hard time? Well, here's my middle finger, deal with it.". They aren't stopping thieves, they are stopping actual paying providers from logging in.