Second that, SR was the critical kickstarter for bitcoin, and litecoin is more than
just another alt because of Atlantis. Ok, thats exaggerated, but still... you can buy cheap E with it, it must have value. 

It says "Trollbox Trader will buy 0.1LTC at market value",
is market value the ask price, ask + fees, midpoint between bid and ask or midpoint + fees?
That would make a lot of difference over time.

Yes, should definitely work with 0.8.1, just a bit slower than with the older (0.7.x) versions.

What about non-DR IOUs, is it possible to send Bitstamp IOUs to DR’s ripple address?
(without risk of instantly getting a bad conversion rate for the specie when there is no liquid DR-IOU/Bitstamp-IOU market)

It's packed with suspense... what will happen first?
-server code gets open-sourced
-OpenCoin shut down by authorities
-server successfully reverse engineered (like World of Warcraft
-a ripple clone starts and is the hit of the day

Given the current XRP market cap (if market is right)
it will get finally decentralized and fixed rather than hacked or busted.

To spend Bitcoins (whenever conveniently possible) and just buy them back immediately is the rational thing to do.
The deflationary nature of Btc is not the problem here, you can still hoard.

If you don't find someone who lends them to you, there could still be a futures market.

For example, some big bank sells Btc futures (using dollars for collateral), some ETF buys them and people can
"invest" in Bitcoin without actually driving the price...

If Ripple++ depends on computing power like Bitcoin why is it still vulnerable to Sybil attack?

Another daemon compile error, "Building headless Bitcoin and Bitcoin-qt on Windows" says
 3.3 From a Windows command prompt run:
 cd C:\bitcoin\bitcoin-master\src
 mingw32-make -f makefile.mingw


That's ok for bitcoin-master, litecoin0.6.3c gives me this error:
make (e=5): Access is denied

But it works from MinGw/MSYS shell.

Yes, literally an asterisk.

Ip address of Default Gateway (from Ipconfig on the guest side) seems to work too.

VMs are the solution to everything because they can run different clients or different versions of the default client
at the same time (directly connected to each other with "connect=..." in config file), and you have all the
functionality of a special client which supports multiple wallets. Probably more.

in Util.h
https://github.com/litecoin-project/litecoin/blob/0.6.3/src/util.h

and only the first 4 "pthread_t" out of 8 (i.e. between "#ifdef WIN32" and  "#else",
it's better to leave the Linux part alone)


But -D__NO_SYSTEM_INCLUDES would be the clean solution.

Found the cause of this error: it's a naming collision, pthread_t in the Ltc source is something different
than pthread_t in Berkeley DB. (and pthread_t doesn't appear in Btc0.8.1)

EDIT: Solution: rename all occurrences of pthread_t between "#ifdef WIN32" and "#else" in Ltc0.6.3 to pthreadfoo_t
Now it compiles with the new Berkeley DB deps. (but is still compatible to the old ones)

qtgui_deps_1.zip: Old link is dead, no mirror,
uploaded what I think is the original: http://www1.datafilehost.com/d/8561ef9a
I don't have the .sig file. Md5 checksum of uploaded file is a3840184ea3bedb8eedb755265ca6e42.

To unpack, copy \lib and \include folder over C:\MinGW\lib and C:\MinGW\include, respectively.

If QtSDK is installed, there is also C:\QtSDK\mingw\lib and C:\QtSDK\mingw\include
but these are normally not used. (?)

Not sure about litecoin-master, or the daemon/makefile.mingw, but the 0.6.3c (the official release) Qt-client is fine.
(compile from Qt4.8.4 command prompt started as admin, not from Qt-Creator)

Also, only DLLs from C:\MinGW\bin and C:\Qt\4.8.4\bin work.
(other versions of the same DLLs crash the executable)

A quick fix for the "pthread_t has a previous declaration as..." error: use the old qtgui_deps_1.zip
for database and only the newest boost and openssl versions, i.e. in the  .pro file:


To get it to compile, I also commented out the  "# regenerate src/build.h"
section, and changed


and

This would be impossible to enforce...

Many alt-coin/modded/patched clients are very interesting but less than fully trustworthy,
and VirtualBox has no good GPU support.

So, for solo mining the miner should run on the physical host machine and connect to the client
in the virtual machine, via "virtual box port forwarding".
Expert level manuals are easy to find, but is there a simple step-by-step howto for beginners?


Very short version would be like:

-Miner: connect to localhost 127.0.0.1 and to some unused port xxxx.

-VBox network settings (for this virtual machine): networking mode: NAT (default)
                                            port forwarding: host IP <empty>
                                                                    host port <the unused port xxxx>
                                                                    guest IP <empty>
                                                                    guest port <the actual rpc port>

-in config file for client in guest machine: rpcallowip=*

This should do it. Guest firewall (in its default state, tested on Linux mint and Win7) is mostly harmless.

There's a strange little quirk when Bitcoin-qt is built on Windows (7, 64bit, new VirtualBox installation) with Qt4.8.4.

If Qt4.8.4 is uninstalled (or on a different PC) the update spinner in the lower right corner (update_spinner.mng)
is no longer displayed. It's back after (re)installing Qt4.8.4.

All the DLLs in the Qt subfolders don't make a difference. (if copied to bitcoin-qt folder)
Same for libmng.dll (not even included in Qt\4.8.4\src\3rdparty\libmng).
Qt4.8.4 installer unpacks files mostly in the Qt\4.8.4 folder, except a few links.
Does it secretly install codecs, and which?

The Qt Sdk from Nokia is actually a very good IDE (the best free-as-in-beer one, I think),
and because bitcoin code comes with the project file for it, you should use it for editing.

Most of the time it's randomness, fooling you...