main: cap orphan transactions held in memory (#16)

A transaction naming a parent the node does not have is never validated,
just stored in mapOrphanTransactions -- and there was no ceiling. Sending
them costs a peer nothing: no proof of work, no valid signature, no fee,
and the node keeps every one. Any peer could grow that map until the node
died of memory exhaustion.

Cap at 100, evicting at random rather than in map order so an attacker
cannot keep its own orphans resident by choosing hashes that sort low.

Local policy, not consensus -- no effect on block or transaction
validity.

1 files changed, 6 insertions, 0 deletions

diff --git a/src/main.h b/src/main.h
index 533974c..40f8d45 100644
--- a/src/main.h
+++ b/src/main.h
@@ -15,6 +15,9 @@ class CWalletTx;
 class CKeyItem;
 
 static const unsigned int MAX_SIZE = 0x02000000;
+// Ceiling on transactions held waiting for a parent that has not arrived.
+// They cost a peer nothing to send and are never validated, only stored.
+static const unsigned int MAX_ORPHAN_TRANSACTIONS = 100;
 static const int64 COIN = 100000000;
 // Total Bitflash emission: identical to Bitcoin (21 million).
 // MAX_MONEY guards against the value overflow bug (CVE-2010-5139), which in
@@ -106,6 +109,9 @@ void ReacceptWalletTransactions();
 void RelayWalletTransactions();
 bool LoadBlockIndex(bool fAllowNew=true);
 void PrintBlockTree();
+void AddOrphanTx(const CDataStream& vMsg);
+void EraseOrphanTx(uint256 hash);
+void LimitOrphanTx(unsigned int nMaxOrphans);
 bool BitcoinMiner();
 void ThreadRPCServer(void* parg);  // rpc.cpp -- .btf pool server
 void GetParticipantMiningStats(uint64& sharesSent, uint64& sharesAccepted, double& hashRate);