Show the timestamp for the block.

wrap lines
Upgrade to Boost 1.49 on Win32
Fix #956 the Boost 1.49 way.
Revert "Disable bitcoin: URI handling on Windows for the 0.6 release"

This reverts commit 7b90edb5a6cada7176012d09d748847b5f966585.
Do not consider inbound peers for outbound network group exclusion.

Bitcoin will not make an outbound connection to a network group
(/16 for IPv4) that it is already connected to. This means that
if an attacker wants good odds of capturing all a nodes outbound
connections he must have hosts on a a large number of distinct
groups.

Previously both inbound and outbound connections were used to
feed this exclusion. The use of inbound connections, which can be
controlled by the attacker, actually has the potential of making
sibyl attacks _easier_: An attacker can start up hosts in groups
which house many honest nodes and make outbound connections to
the victim to exclude big swaths of honest nodes. Because the
attacker chooses to make the outbound connection he can always
beat out honest nodes for the consumption of inbound slots.

At _best_ the old behavior increases attacker costs by a single
group (e.g. one distinct group to use to fill up all your inbound
slots), but at worst it allows the attacker to select whole
networks you won't connect to.

This commit makes the nodes use only outbound links to exclude
network groups for outbound connections. Fancier things could
be done, like weaker exclusion for inbound groups... but
simplicity is good and I don't believe more complexity is
currently needed.
Fix signed/unsigned warnings in {script,serialize}.h (fixes #1541)
Work around a distcc bug where -MMD output isn't copied.
Merge pull request #1548 from TheBlueMatt/warnings

Fix signed/unsigned warnings in {script,serialize}.h (fixes #1541)
Merge pull request #1546 from gmaxwell/allowsamenetinbound

Do not consider inbound peers for outbound network group exclusion.
RPC: break out high level JSON-RPC req/resp into their own functions

This prepares for JSON-RPC 2.0 batches.
RPC: add support for JSON-RPC 2.0-style request batching

If the top-level object is an array, it is assumed to be an array of
JSON-RPC requests.  An array is returned, containing one response (error or
not) per request, in the order submitted.

In a slight change in semantics, batched requests -always- return
an HTTP 200 OK status, even ones full of invalid or incorrect requests.
Merge pull request #1512 from jgarzik/json-batch

Support JSON-RPC 2.0 request batches
Remove duplicate GetHash() in ConnectBlock
CTxMemPool: eliminate redundant lock, GetHash() call

::addUnchecked()'s only caller already takes the necessary lock,
and has already calculated the TX's hash.
Fix remaining warnings.
Merge branch 'buildupdates' of https://github.com/TheBlueMatt/bitcoin
Merge pull request #1555 from TheBlueMatt/warnings

Fix remaining compile warnings.
Rework gettransaction / getblock RPC calls

This PULL reworks new (post-0.6.*) features of the
gettransaction/getblock RPC calls as follows:

It removes the 'decompositions' object argument from getblock,
replacing it just a list of transaction hashes; equivalent
(I believe) of passing the {"tx":"hash"} decomposition.

It replaces the 'decompositions' object argument of
gettransaction with a boolean flag; if true, returns
the same stuff that the {"script":"obj"} decomposition
would return (txins/txouts as hex, disassembled, and bitcoin
addresses).

It adds a "rawtx" field to the output of gettransaction,
that is the entire transaction serialized and hex-encoded.

It removes the "size" field from gettransaction, since the size
is trivial to compute from the "rawtx" field (either take the
length after hex-decoding, or just compute it as hex-length/2).
Refactor: SignSignature/VerifyScript

Minor refactor to support signrawtx signing/verifying transactions
when it might only have the previous transaction's txid and
txOut.
RPCTypeCheck method to make type-checking JSON Arrays easier.