Downloading the x64 DVD right now via BitTorrent, should be able to get a virtual box of this up within the day. Should get a x64 compile then for bitcoind when it's all done, I'm curious myself to see how it runs.

$600 is a great deal for pizza I thought? 

It should run, I was able to run it on their (cc1.x4xlarge, 23GB) CentOS Cluster even though it's not a x64 build, the x86 still worked for me. I didn't even need to install the full bitcoin, I just uploaded the bitcoind and ran it right from root  

It was very expensive, $1.60/hour per "Cluster Compute Quadruple Extra Large" basically.

I only ran a 1 hour instance just to see how it performed (too expensive to be practical) and I was checking the debug.log file to see what it was recording for khash/s.

I wonder if a x64 build would run faster on that cluster than the x86 build?  

Well, you could cheat I guess and copy the full blocks from another machine if you have one (Linux box) to see if it hangs or if it can continue from that point.

That is really strange though, if anything the CentOS build downloads blocks faster than anything I've seen yet. I can download the entire block chain in a few minutes with this build.

I've compiled an x86 version with the 0.3.8 source, can you try using that one? If you already have it, the only thing I can think of is have it start from the beginning by deleting the blocks and let it start fresh in case something was corrupted in the beginning.

Yeah, been moving around folders to try and organize things. I have about a dozen virtual box now of many different distro so as I get time, I'll compile other releases and label them properly. I don't have a x64 build yet because I haven't built a x64 virtual box with Centos 5.5 yet 

I did notice it works with CentOS 5.4, so I fired up an Amazon EC2 instance running CentOS 5.4 on 16 cores and loaded it up. After it downloaded blocks, it starting churning away on 16 cores, but only managed about 8,800 khash/s, kind of disappointing for an EC2 instance.

I'll pledge 500 BTC for a good animated movie that has a laymen explanation of how things work, maybe a sprinkle of technical stuff about why it's safe/secure/etc.

It can't be too technical, people's eyes will glaze over if it starts talking about SHA256 and p2p block chains.

I've been running mine since I made the first post about where to download it.

Everything seems to be fine and the bitcoind is using 100% doing coin generation at the lowest prioirty from when I checked top

From what I can tell on your output, it seems to be hung at that block for some reason. When you stop the daemon and restart it, does it continue on then?

If you want, you can try a direct connect mine with ./bitcoind -server -connect=12.53.130.10 to see if it's a build thing.

I appreciate your concern; the current release version already limits connections to 8, this one won't establish hundreds of connections to a single client or node, it's just modified to allow hundreds of connections back to it from independent clients. I figured since I have the CPU and bandwidth horsepower, why not put it to good use for Bitcoin?

I've posted the binary up here (32 bit only - bitcoind):
Click Here

There are two versions, one built from stock code, the other modified to accept up to 1,000 nodes (hence the super node name)

Will probably tackle the GUI client build another day, this one wore me out. Donate some BTC to my sig if you are feeling generous  

Oh, but there's more! 

Even after I did that, I couldn't get it to compile due to linking errors. I was able to get a solid compile of bitcoind though, this is the extra steps it took.

After compiling and installing the BerkeleyDB4.7, you need to add it's include path to the makefile.unix

Add -I"/usr/local/BerkeleyDB.4.7/include"

Then you need to copy all the libraries from "/usr/local/BerkeleyDB.4.7/lib" to "/usr/lib"
BUT WAIT, there's MORE! 

Yes, and if that was not annoying enough, now it will fail to compile because of an OpenSSL error, Grrrrr..

Now you must copy libcrypto.a and libssl.a from "/usr/local/ssl/lib" to "/usr/lib"

Yes, those can be linked, but I got tired of chasing down compiler errors, was easier to just copy them. 

After all of that, then you should be able to compile a bitcoind binary.

I'm testing it now, seems to be working just fine. Downloading blocks and such. When it finishes, I'll experiment with some coin generation and coin transfer.

I'm still caught on the GUI client compile, currently hangs at
If anyone is good with Google, let me know. 

Ok, conquered the DB issue after pestering an Oracle developer all day 

When you compile DB 4.7.25, you have to use an extra config command or else the compile will be missing those vital header files (why???)

Anyway, here is what it was
When you compile the source, this fixes the DB compiling related errors.

I just saw that myself, I haven't had time to dig through all the links to see what the process is since the Administrators don't have a direct "contact me" button anywhere. 

Interesting info, so other than some double-spending issues, as long as the block chain isn't separated for more than 100 or so blocks (or 16+ hours), it should be able to merge back to together without too many issues. So coin generation would probably be the only victim (if no double-spending cheats took place), or more technically, coin generation would be assigned to someone else that was generating at the same time as those that split off.

If there a hard coded limit on split delay? Meaning if I had a small network split from the public network, spent some coin around, came back a few days later and got them sync up to the public network (other than coin generation if it happened) transactions should be fine?

I'm probably going to load up a virtual machine of CentOS 5.5 and work with that. I've really barfed up the server I was experimenting on trying make it build the binary, LOL.

Oh you mean official binaries in package form hosted by the Ubuntu folks?

Just for kicks, tried to compile with DB4.8 got the same error, LOL (the line number was slightly different, but at the same class)

Didn't get this on other Distros, might be a CentOS related error, but not sure why.

I've built the client and daemon for Ubuntu 9.04 (should work in later versions ?)
Not a package per say, but you can just download the current Linux release and just overwrite the binaries. Not perfect, but it will get a working version for you that way.

Why not break it down to continent? 

Yeah, the bitcoind build gets around any errors for those, but I still get stuck at the DB error.