r9mh87k7dHJH1XrNzkiQAMmqzShzWStWj9

Have you heard of the Interplanetary Internet? It's how NASA is solving that exact problem, with a lot of backing from Google as well. It's based around delay-tolerant networking protocols, and is being designed by Vint Cerf (amongst others), one of the original co-designers of TCP/IP.

Great, thanks. I launched an instance and tried logging on as Administrator with the password you gave on this thread, but no dice. Did you set this up with a different password? Or set it up to use auto-generated passwords?

Sure, that wouldn't be a problem for me. Good idea.

Caston, you'll have to sign up to Amazon's EC2 services, and then you can search for the image and launch an instance of it from the online AWS management console.

Gavin, do you have / can you make public the image for the dodgy 0.3.20 VC10 build? I'd like to have a look and compare it to my home build to see if I can reproduce that rendering artifact problem. Thanks.

0.3.20.01 runs fine for me.

FYI I successfully built 0.3.20.00 using VC10 on my Windows machine, and haven't been able to reproduce the same WxWidgets problem that the build from the Amazon EC2 windows virtual machine had. So far.

Library versions I built with:

Berkeley DB 4.7.25.NC (projects converted to VC10)
OpenSSL 0.9.8r
Boost 1.43.0
WxWidgets 2.9.1

I'll try to match the OpenSSL and Boost versions more exactly up to the virtual machine build, but the other two libraries match.

I'm having trouble linking with the Berkeley DB library.

The Berkeley DB 4.7 download doesn't include the static library libdb47s.lib (specified in the most recent makefile.vc), so I have to build myself (I googled to see if anyone online was offering the binary, but found little).

The problem is that the code is only supported up to VC8 (2005, uses .dsw and .dsp project files), but VC8 is now severely deprecated and you can't download it from Microsoft anymore. I've been trying to build with MinGW but that has thrown up a slew of problems by itself.

For the official build, where did you get the static library from? Did you build with VC6 or VC8 originally?

Maybe I should just link the bitcoin client against the non-static lib and DLL provided with the download...

Any thoughts or advice much appreciated!

C'mon, this is from the National Enquirer. Not the most reputable source of factual news... I for one am not going to give much credence to this at the moment!

What's the recommended build configuration for WxWidgets, for use with the Bitcoin client, regarding MONOLITHIC, SHARED and RUNTIME_LIBS (both MinGW and VC10)? Or rather, what configuration is used on the build server...?

Edit: looking at the libs linked in makefile.vc, I'm deducing MONOLITHIC=1, SHARED=0, UNICODE=1, and RUNTIME_LIBS=dynamic for VC10 build.

I just downloaded the 0.3.20 client and noticed the same problem.

I'm happy to have a look at it, but it depends on how much of my time I can spare over the next few days. I may not be particularly quick though, given that I only got the source from the git repository a couple of days ago and this will be my first look at the code.

I agree with theymos. We want to make it as easy as possible for people to find out and become involved with bitcoin, not make people jump through hoops to become part of the community.

I know there was some spamming on threads early yesterday, but has this been common up until now? Is it really enough of a problem at the moment that we need to take such a measure? Either way, using captchas would be a better way to stop spam than requiring a login.

As for "protecting members opinions", this is intended to be a public forum. If you don't want your posts indexed by a search engine, then I can only respectfully suggest that you don't post anything...

Exactly. It may be on the school curriculum, but most people have no interest in, or a need to use, scientific notation. Or any numbers outside of what they have to deal with in their daily life. And what you don't use, you lose.

If bitcoin wants to be taken seriously by a wider audience, it will need to address this. It is (or will be) one more hurdle to acceptance, and there are more than enough hurdles for an idea like bitcoin to deal with in the first place.


The rate of this change is fairly key to the discussion. If the change from bitcoins to milli-bitcoins happens over a couple of generations, fine. If it happens in the space of 10 years, that's a problem.

People need to be able to compare prices over time to be able to make useful decisions about purchases now compared to the past, and their relative value. Large-scale deflation raises the same problems with this, and with menu costs, as large-scale inflation does.