Former-commit-id: 66f0baa03b21f972e974b89cd89890568043f2a7

Former-commit-id: 27ea40292b1061972f3742eaf9191703cc4b0e16

Former-commit-id: 88e56abad7e5780aafecb4b05fbb5b38732f010f

Former-commit-id: 0b81c6f358edd56ccd4919318f36659b99410fc0

Former-commit-id: 7b67fa100f4582c58f139afae34c332a355d826a

Former-commit-id: 03c3669604dcba0751ff138bbeb9095182a89f21

Former-commit-id: fb9d82924a0adaca8e18a99db1e3be6693ab4274

StakeBox authored 8 years ago and Fabian Olesen committed 8 years ago

* allow throne enforcement

* protocol bump

* disconnect from older clients after 14:55 UTC September 1 2016


Former-commit-id: 67d7f946fd8f4418e6decad5cfddca4b3f789f8a

This is, basically, the patch developed also for Isracoin with only
minor modifications.  Adaption and testing still needs to be done.

Implement CBlockIndex::GetBlockHeader for auxpow block headers.  In this
case, load the header from disk.  Add a function to do that (as opposed
to reading the full block).

Not yet very well tested, and still missing getauxblock.  But it still
accepts the existing blockchain, which is a good start. :)

Rebased-From: 730b1ed1
Github-Pull: #5154

Normally bitcoin core does not display any network originated strings without
 sanitizing or hex encoding.  This wasn't done for strcommand in many places.

This could be used to play havoc with a terminal displaying the logs,
 especially with printtoconsole in use.

Thanks to Evil-Knievel for reporting this issue.

Conflicts:
	src/main.cpp
	src/net.cpp
	src/rpcserver.cpp

Rebased-From: 28d4cff0
Github-Pull: #5770

Refactor common -alertnotify code into static CAlert::Notify method.

There is no reason to store thousands of orphan transactions;
normally an orphan's parents will either be broadcast or
mined reasonably quickly.

This pull drops the maximum number of orphans from 10,000 down
to 100, and adds a command-line option (-maxorphantx) that is
just like -maxorphanblocks to override the default.

Rebased-From: 7b45d943

Prevent denial-of-service attacks by banning
peers that send us invalid orphan transactions
and only storing orphan transactions given to
us by a peer while the peer is connected.

Rebased-From: c74332c6

Rebased-From: 540ac451

Rebased-By: Wladimir J. van der Laan <laanwj@gmail.com>

Rebased-From: def2fdb4
Rebased-By: Wladimir J. van der Laan

Rebased-From: 89d91f6a

Rebased-By: Wladimir J. van der Laan <laanwj@gmail.com>

Removes the limits on number of pubkeys for P2SH CHECKMULTISIG outputs.
Previously with the 500 byte scriptSig limit there were odd restrictions
where even a 1-of-12 P2SH could be spent in a standard transaction(1),
yet multisig scriptPubKey's requiring more signatures quickly ran out of
scriptSig space.

From a "stuff-data-in-the-blockchain" point of view not much has changed
as with the prior commit now only allowing the dummy value to be null
the newly allowed scriptSig space can only be used for signatures. In
any case, just using more outputs is trivial and doesn't cost much.

1) See 779b519480d8c5346de6e635119c7ee772e97ec872240c45e558f582a37b4b73
   Mined by BTC Guild.

and use it for most strings being serialized.

Rebased-From: 216e9a44

Generally useless information. Only updates on connect time, not after
that. Peers can easily lie and the median filter is not effective in
preventing that.

In the past it was used for progress display in the GUI but
`CheckPoints::guessVerificationProgress` provides a better way that is now used.
It was too easy to mislead it. Peers do lie about it in practice, see issue #4065.

From the RPC, `getpeerinfo` gives the peer raw values, which are more
useful.

Rebased-By: Wladimir J. van der Laan <laanwj@gmail.com>
Rebased-From: 305ccaa2

Size specifiers are no longer needed now that we use typesafe tinyformat
for string formatting, instead of the system's sprintf.

No functional changes.

This continues the work in #3735.
Rebased-By: Wladimir J. van der Laan <laanwj@gmail.com>
Rebased-From: 783b182c

Fixes issue #4139.