We confirm that 1HWKYwZSBVwiug4RZmxv3FsQRuqhHzqkvw is connected with 100 shares.
|
|
|
Update
Online Hashes (theoretical): 24TH/s. Struggling at current 22TH/s in average due to maintenance and troubleshooting (mainly PSU and internal LAN hardware). We are fixing some bottleneck while bringing new hashpower online at the same time.
Shipped Blades: 278. The sales keeps a slow but steady pace.
Shipped USB Sticks: 530. A lot more in the following week.
We are using the same transaction policy of the official Bitcoin client's default behavior.
We also finalized the decision on making the next-gen (65/55nm) chips also fit in a USB powered device so that we could make Block Erupter USB II possible, instead of integrating too many cores into one big chip.
Was that 278 in the last week, or 278 including the 190-odd in the 3rd auction? 278 in total, including the 3rd auction. The 3rd auction turned out to not having 190 in total since some didn't pay till now.
|
|
|
Update
Online Hashes (theoretical): 24TH/s. Struggling at current 22TH/s in average due to maintenance and troubleshooting (mainly PSU and internal LAN hardware). We are fixing some bottleneck while bringing new hashpower online at the same time.
Shipped Blades: 278. The sales keeps a slow but steady pace.
Shipped USB Sticks: 530. A lot more in the following week.
We are using the same transaction policy of the official Bitcoin client's default behavior.
We also finalized the decision on making the next-gen (65/55nm) chips also fit in a USB powered device so that we could make Block Erupter USB II possible, instead of integrating too many cores into one big chip.
|
|
|
While you are here friedcat, are you able to enlighten us on the new revision of ethernet and power delivery boards we will eventually receive. 1) Why have you designed a revision, what is likely to improve? 2) Will you be rolling it out on all your blades already hashing away or just new installs? 3) Can we have another hashing board with them, seems a shame to have perfectly good ethernet and power delivery boards without a friend 1) Mainly for longevity and stability. 2) Just for new installs. 3) Yes. But you need to pay for the hashing board according to the price at that moment.
|
|
|
@Friedcat: Is there a possibilitie to overclock the blade? There is only a pre-defined high clock, iam reaching 13.2 gh/s, but could reach more because my blade Is on the heatsink 23 degrees and on the chips 51 degrees. So is there a way to bring it to a higher hashing rate? I really would like to.
What is the max temp on the chip side?
Not easy. The oscillators are fixed on the hashing board (one 12MHz, one 14.318MHz). Low switches to the 12MHz one while High switches to the 14.318MHz one. If you need more speed you will need to buy a 3.3V 5mmx7mm oscillator that is higher than 14.318, unsolder the current one, and solder the new onto the board. We tried 14.7xx and 15 before. On 1.25-1.26V they begin to work, but producing a lot of heat. Plus, grabbing the oscillators out of the board definitely voids the warranty
|
|
|
can not open 192.168.1.254:8000...what shall i do ?
Is the board powered on? Could you see the LED on the ethernet cable? i did not see the led is light on the ethernet cable.... thank you very much Please make sure that the fuse (small red stuff) is properly inserted. Also the small green LED on the controller should blink for a while after the blade is powered on. The relay should keep silent instead of making clicking noise. If anything goes wrong please report to us via PM or mail.
|
|
|
can not open 192.168.1.254:8000...what shall i do ?
Is the board powered on? Could you see the LED on the ethernet cable?
|
|
|
Thanks Caesium! s/101/100/ was exactly the fix.
The blade is now hashing merrily. Still only one yellow wire, but it's not even warm (keeping a close eye/finger on it though). Noisy but powerful tabletop fan blasting across the blades and behind (it's biiiig).
Five minutes in, hashrate appears to be 5.8 GH/s, power draw ~61W. Are these figures reasonable? I should point out that in the interest of safety I twiddled all those voltage screws down to their lowest setting which appears to be 970mV (varies by a few mV for each screw).
ETA: just noticed the row of chips is about a third 'x'ed. Is that just cause I've undervolted?
1.05V is the recommended undervolting figure. You could try 1.03 but some of the chips couldn't really work on such low voltage due to variety in wafer production. If you are lucky 1.03 should be fine.
|
|
|
Some of the sales are yet to be finalized, therefore should be counted in the next week's income.
|
|
|
The first mass production batch (sapphire) has finished its PCB production and assembly today. It has significant improvements in: Heat reduction: 560mA (emerald) -> 500-510mA (sapphire). Stability: We stressed it with 9 Block Erupter USBs in a row without heatsinks heating up each other in a very dense USB hub with 25C without active airflow. No unexpected (non-probabilistic) HW errors ever happen. Speed: This comes after better stability. Now the hashrate converges to its theoretical value of 336MH/s. Appearance: Manual assembly (emerald) -> SMT machine assembly (sapphire) Standard heat-sink (emerald) -> heat-sink front-case 2-in-1 logo-ed (sapphire). LED added. Four types of front-case: All of them are eager to be powered up and hashing! We had shipped the first 200 USBs today immediately after they are out of the factory. Soon more than 10,000 shiny little stones will be distributed international and quietly erupt blocks.
|
|
|
The transfer to mc_lovin's account is done.
|
|
|
We confirm that the payment has been received from yxt.
|
|
|
Update So we feel that it is most responsible to let the shareholders decide how to do with the abundant Bitcoins.
How will you be taking in input? Will it be through an email based vote per share? Will it be by boardmembers? We mean pay them to the shareholders and let them have the total control.
|
|
|
Update
The mass production of Block Erupter USB is to be done today. Busy testing and packaging will start.
About the argument of dividend payments, our view is that we will distribute the net income after necessary costs are excluded and funds for foreseeable future (expansion, gen-2 chips) are reserved. Bitcoin is already an investment itself having a great potential. Any investment, no matter how profitable, based on "turning Bitcoins to fiat first" requires double consideration. We can invest the RMBs to bonds and they are almost bound to be more profitable than just holding the RMBs, but we can never say the same to Bitcoins.
So we feel that it is most responsible to let the shareholders decide how to do with the abundant Bitcoins. We will of course find other investments (which are focused on helping the Bitcoin economy therefore benefit all Bitcoin holders), but they are all involved in different risk and return model than a mining/mining hardware company. The shareholders of ASICMINER are in principle not supposed to bear the new different risks on doing other business than Bitfountain's. So if there are new investments, they will be as new adventures, in new collaboration structures, and after a significant period of time since ASICMINER is always the most important job for us to do before the company could gradually run itself with a little less founder involvement.
|
|
|
TroubleShooting
Three or four "x" in a row on "Chips": The corresponding power lane does not work or is not supplying enough voltage. Try measuring each power lane to find the dysfunctional lane and tuning it higher. If it doesn't work please ask us to send you a new power module.
More than two "x" scattering on "Chips": Some of the chips could not work on high clock in the current voltage. Try tuning the voltage of the whole power module a little higher. If it doesn't work please downclock to Low.
Hashrate turns to zero and all "x": Either the power module is broken or the whole blade has some problems. If you bought more than one blades, try using other functional ones' power module to test if it becomes OK. If so please ask us to send you a new power module. If not, please return the whole blade back and we will send you a new one. (we cover the shipping fee)
The blade misreports the hashrate to a very high number but hashes at a very low speed: Most probably it's the problem with the ethernet controller. Try hardware-rest it as shown in the online user guide. If it doesn't work please ask us to send you a new ethernet controller. It may also be caused by the misfunctionality of the hashing board. If you bought more than one blades, try using other functional ones' ethernet controller to test if it becomes OK. If not, please return the whole blade back and we will send you a new one. (we cover the shipping fee)
All or most chips are "O" but the efficiency is very low: This happened on two or three blades on our former products. Most probably it's some shortcuts on some of the chips' communication pins. It shouldn't occur in the second (current) batch, but if this happens we will do a free replacement.
(To be extended...)
|
|
|
|