Performance Results from 2x Gridseed Blade Miner ASICs

8 Apr


A few days ago we have posted our first test results from the new Gridseed Blade Miner. We got early remote access to a single unit that we were able to test and report our findings before the devices actually started shipping thanks to our friends at MinerEU who are an official Gridseed EU distributor. Meanwhile we got a second unit attached to the system we were testing, so we were able to run some longer tests with two devices in order to see what variance we can expect from device to device. We also expanded the tests to cover various usage scenarios to check what hashrate you can expect to get if mining for a fixed higher difficulty coin such as LTC as well as if you are mining in auto profit switching mode to mine the most profitable crypto coin. Meanwhile the new Gridseed Blade Miners should start shipping tomorrow, so the people that have ordered them should start receiving their units very soon.


We are starting up with a result showing the two Gridseed Blade Miners, each of which is reported as two separate devices, fixed in mining for LTC with a worker difficulty of 256 at the scryptguild pool. The Blade Miners are running at 800 MHz, a frequency that can normally provide up to about 5.6 MHS in mining a fixed crypto currency with higher worker difficulty. Note that one of the PCBs, namely the GSD 1 device does report a lower actual hashrate and that is a direct result of getting some HW errors from that PCB. It seems that this could be related to the cooling not giving a good contact to one of the PCB sides for example, so we recommend to inspect your miners and if needed to optimize them a bit before running them, just in case and to get the best performance. This is something that we recommend doing for the smaller 5-chip Gridseed ASIC devices as well, especially if you plan to overclock and voltmod them, you need to check the contact between the cooler and the chips.


Notice that the poolside result is pretty much consistent with the local reported actual hashrate. Do note the other worker above the Blade miner, it is from a voltage modified 5-chip Gridseed ASIC running at about 490 KHS local hashrate (1150 MHz). You can see that with close number of submitted shares to the pool, the number of rejected (stale) shares is almost twice as high on the smaller ASIC as compared to the Blade Miner. The reason for that difference is that the small miner is running on automatic profit switching and 64 worker difficulty, so it gets more stale shares due to the often switching between different crypto coins and due to the fact that some are with lower difficulty and many blocks are calculated quickly.


So how about leaving the two Gridseed Blade Miners for a few days to run in auto profit switching mode at 64 worker difficulty at scryptguild, the miners were running in 800 MHz. The result is quite interesting, local hashrate reported at about 5 MHS per device with about 6.8-6.9% of stale shares (the percentage is higher as expected) and more HW errors that you would normally get if mining for a specific coin only. What you should be well aware of is that based on the pool and the type of mining you are doing you might be getting different performance that could be lower or higher than what the official specifications about the miner say. Using automatic profit switching pool might help you get more profit than mining directly for LTC for example, though the extra percentage you might get may be lower in reality than what your raw calculations may show initially as you could be getting more stale shares as well as more hardware errors this way. So far we are satisfied from the results we are getting from the new Gridseed Blade Miner, though at the moment due to the uncertainty and the lower Bitcoin and Litecoin prices, people seem to be very careful in general when considering to buy ASIC hardware. And we are not talking only about investment in very powerful and very expensive mining hardware that is expected to ship later this year.

For more photos, specifications and information about the new Gridseed Blade Miner…

Other Similar Publications:

6 Responses to Performance Results from 2x Gridseed Blade Miner ASICs


April 20th, 2014 at 17:23

any one has a working binary that shows the real hashrate of the blades?

cgminer or bfgminer …


April 20th, 2014 at 18:26


April 20th, 2014 at 19:38

Ah nice, thank you … I was looking for a raspberry binary … .-)


April 26th, 2014 at 06:10

Where can one find a copy of bfgminer that works with the 80-chip blade? The 3.99.0 I pulled off of here will only look at the blade as a traditiona 5-chip miner? Maybe I am missing something in the config? Thanks!


April 26th, 2014 at 10:24

JoeFabritz, bfgminer works fine, the only problem is the improper reporting of local hashrate, though poolside it is fine. There is no official update to fix that, but again not that big of an issue. There are already versions of cpuminer and cgminer with proper local hashrate support for the G-Blade available.


April 26th, 2014 at 17:16

Thanks admin. The only reason I am asking is that I am using the cpuminer version with no problems, but I cannot use that to connect to a solo mining setup – it fails without an error. I am guessing it has something to do with the http versus the stratum connection. I was able to use bfgminer to connect to the solo, but it would not register more than 5 chips.

Leave a Reply

Your email address will not be published. Required fields are marked *