So let me get this straight... you wrote all that stuff about compiling the code from source and about how the board and test machine didn't have any kind of internet connection, and then you neglected to mention that you'd used a laptop set up and provided by BFL which could've had a hidden wireless connection to anywhere.  Did you even make sure that the binaries you were running actually corresponded to the source code you received, or did you use binaries that BFL provided too?

I just got home after meeting with Sonny in person from BFL and their engineer via Skype.  We had a fairly long conversation and I live over 30 miles away, so that's why it's taken me this long.

We did some simulated testing, but no live testing tonight.  We elected to put that off until tomorrow or possibly Sunday to allow for proper testing instead of just throwing some tests together.  I have, however, seen several units (and I will post pictures of them) and seen them power up.  Beyond that, I have nothing definitive to say, other than so far, so good.  I will be meeting with them again this weekend to conclude the testing on the live pool on an isolated network with no net access.

While I was not able to inspect the chips under the two main heat sinks, the other chips are plainly visible and inspectable.  There is nothing on that board to indicate any sort of cellular connection, for those of you suspecting that sort of nefarious scheme.  It was hard to take pictures at the location we were in and I will have better pictures once they let me take a unit over night - I will put it in my light box and get some properly lighted pictures.

I don't know why it says 0.  It wasn't a live test, so I wasn't too concerned, I was more interested in putting into a test loop to see what the power consumption was (which was 17.6W) - I took pictures of the Kill-A-Watt, but my flash blanked out the LCD screen of the Kill-A-Watt - I will get some non-flash pictures of it tomorrow or Sunday.

The demo plan is that I will:

A) connect it to a non-routable development side of the pool, so that the box is unable to communicate with the internet.  I will then let it submit shares to the pool and I will have one of the getwork servers in debug mode and I will see what is sent out and what's sent back.  As I found no evidence of any wireless communications on the board, and since the computer it's connected to will not be on the internet, it won't have any way of falsifying the shares submitted.

B) I will take a unit home that evening, disassemble and take more robust pictures.  I will NOT be removing any heat sinks, however.  

C) I will do further testing that evening on my own with a packet analyzer to see  what packets are being transmitted, when and where they are going and coming from.

That's the plan as of right now, at any rate.