Industry Updates
Viper ASIC Update(Litecoin)
Viper ASIC Update(Litecoin)
Neptunes are still very much in the preliminary design phase. As much as the timeline will be reduced significantly in comparison to a standard engineering project at 20nm, if such exists, because this is absolute bleeding edge we want to be absolutely sure what we commit to silicon will ensure a successful product at the end. This initial phase will not be rushed.
That said we have completely re-written and optimised the RTL code. The Jupiter project was very much focused upon safe speed to market and the window of opportunity hashing power presented in this present finite period prior to significant competition. The Neptune project whilst adhering to aspects of the aforementioned must focus upon power consumption as it's primary trait if customers (you guys) will be able to compete successfully over a longer period. We know that we are reaching limits on standard household circuits, we want you to remain competitive w.r.t. the unfolding mining landscape and we are all to well aware that electricity costs will come into focus in the not too distant future.
So where we are now is that we have a working FPGA code and are in the process of testing that and tweaking any further refinements before it's submission.
With respect to the speculation above we sold out of Neptune's last night.
Viper ASIC Timeline ReleasedThat said we have completely re-written and optimised the RTL code. The Jupiter project was very much focused upon safe speed to market and the window of opportunity hashing power presented in this present finite period prior to significant competition. The Neptune project whilst adhering to aspects of the aforementioned must focus upon power consumption as it's primary trait if customers (you guys) will be able to compete successfully over a longer period. We know that we are reaching limits on standard household circuits, we want you to remain competitive w.r.t. the unfolding mining landscape and we are all to well aware that electricity costs will come into focus in the not too distant future.
So where we are now is that we have a working FPGA code and are in the process of testing that and tweaking any further refinements before it's submission.
With respect to the speculation above we sold out of Neptune's last night.
Quote
On Monday (13/01/2014) we released an outline of our set roadmap, today as promised we will be releasing a timeline with dates on each aspect of the development process. This shows our commitment to transparency and gives a better idea on what exact stage we are on at all times. As we go through multiple developmental stages in parallel, we will be releasing regular detailed updates on our progress. Our next updates will be consistent developmental updates on what is being worked on and what has been achieved.
Timeline:
Project Start: 16/08/13
Project Finish: 15/07/14
<-- Table Snipped See Posts for table -->
Roadmap (recap):
<-- Image Snipped See Posts for Images -->
Timeline:
Project Start: 16/08/13
Project Finish: 15/07/14
<-- Table Snipped See Posts for table -->
Roadmap (recap):
<-- Image Snipped See Posts for Images -->
With respect to Neptune we are where we intended to be at this stage and are still contemplating aspects of the design. Understand that the approach is not the same as that of Jupiter. 28nm was extremely disruptive at the time, of which the effect can plainly be seen. Hashrate was given priority to power consumption, and safety and speed to market even more so, but going forward and acknowledging that power consumption becomes more a critical factor the Neptune has to be created as more a long term solution. We will not skimp or rush the design here. This does not mean I'm indirectly verbalising a delay, so don't go looking for hidden meanings, there aren't any to find, just rest assured I'm stressing we value the integrity of the design more which is why Q1/Q2 was given to ensure that margin is present so we commit the best foot going forward in what is uncharted waters within bleeding edge silicon. We're not rushing the design at the cost of it's ability to function, and function well. The sha-256 implementation is actually relatively simple, but there is still quite a bit we can optimise to remain competitive for you and us.