The HW errors in bfgminer can be cut when bfgminer recognises it as a block erupter instead of an Icarus. The device should appear as BES (Block Erupter Sapphire), instead of ICA (Icarus). But you need to "brand" your block erupters for bfgminer to recognise them properly.

See: https://bitcointalk.org/index.php?topic=250326.0

If you are using bfgminer these should appear as BES (Block Erupter Sapphire), instead of ICA (Icarus). But you need to "brand" your block erupters for bfgminer to recognise them properly. There isn't much difference, except the settings and timings are slightly tweaked for optimal performance.

See: https://bitcointalk.org/index.php?topic=250326.0

What is this "Windows 8" you talk of? Haven't you heard of Linux

Its not really a USB connection, its a rs232 serial connection. rs232 can support parity, but this is just for error detection. What I would do, if I had my hands on the firmware would be to modify it to send the 4 bytes of nonce, 3 times in a row (so total of 12 bytes). This would serve as error checking (the 3 nonce values didn't match) and error correction (take the two nonce's that do match). There are more complex schemes for checking and correction codes, that potentially use less bytes, but for the sake of 12 bytes this is about as simple as you can get.

So I am looking through the bfgminer driver: https://github.com/luke-jr/bfgminer/blob/bfgminer/driver-icarus.c

I can't see any evidence of error detection or correction on the protocol, no parity, no checksums, no resend.

The protocol just sends 4 bytes of nonce data. Ok maybe "the nonce *is* the checksum" since it will be checked by the host standard c sha256 routines. But all bfgminer does, in this case, is flag HW error and close/reopen the usb port. I would expect it might at least ask for the nonce again in case of transmission error.

It would be interesting to examine each ends of the communication protocol, I think bfgminer/cgminer are using the icarus protocol http://en.qi-hardware.com/wiki/Icarus#Communication_protocol_V3

The main reason I would like to know is because I would like to know how error handling of transmissions over rs232 is corrected. It would be embarrassing to find that the hardware errors were nothing to do with the asic, but actually due to data transmission errors.

I've noticed a stock erupter plugged directly into usb port gets about 1/2 the HW errors than when plugged in via extension cable.

Edit: ...And BTW I realize that noise over the usb transmission lines would not be a problem, rather noise over the usb power lines would effect the serial between the CP2102 (USB 2 UART) and the T2313A Microcontroller

On the coinlenders front page when you are not logged in you have:

Bitcoin lending
Get BTC loans with sane interest rates
Or earn interest on your deposited coins!

I am sure those should now say 'fees', and 'fee rebates' in accordance with the site being 'fictional'

Edit: I have also since noticed:

Get loans!
Get your credit rating which you choose who to share to, apply for BTC loans.. You choose your interest rate and schedule!

Excellent!

I like this. Is there a button API such that anyone can add a button similar to the Coinlenders "Deposit bitcoins" button on their own website?.

As per this message. Emmanuel claims to have been cleared as not a scam, by the infamous Coin Canary

Inputs.io is really great. I would like an option to link the accounts somehow so I can see my coinlenders balance in inputs.io and just withdraw it, or make payments straight from there without having to make the intermediate step.

I know that's probably asking a lot in terms of architecture change just for the convenience to the user. But it would be nice.

Is his name Emmanuel Abiodun or Emmanuel Adedeji? Its odd how they are such similar names. On the other hand why would he make a post on facebook with a username so similar to his own?

Hello, I have known about bitcoins for a while after reading about them on a 3D printer forum. (someone thought it would be a cool idea to sell 3D prints for BTC) I decided I would buy some back in 2010 (they were about $1 each then) to fund patches to my open source software project called RapCAD. Well that project still exists, but I never got round to setting up the bounty for patches idea. Fortunately  BountySource now exists and they propose to support BTC as payment at some point.

Anyway the only reason I am writing this is so that I can post properly elsewhere on the forum. So I hope anyone reading this enjoyed reading it as much as I didn't enjoy typing it