Adding an index on hash/index for spendings.
more aggressive pruning - might make the app to slow in starting
Merge remote-tracking branch 'origin/master'
Removed “dnsseed.bitcoin.dashjr.org” from seeds list in bitcoin - seems no longer available.
Purging in a big chunk can be awfully slow, so I don’t want to enforce it now - need to figure out how to speed it up a bit.
removed some wrongly inchecked files that will be changed on every build
New notification system:
You can specify an external program that will be called in case of alerts and other system critical events
It is invoked through Node::notify, and can e.g. be specified on the commandline by the notify option as:
	--notify="/usr/bin/mail -s libcoin_issues admin@mysite.com”
The external program get the notification on stdin.
The default notifications are alerts and if an invalid chain becomes longer than our main chain.
You can in a daemon specify other notifications (like e.g. if your wallet is running out of funds or if a transaction is stuck in confirming)
The design of the notification system is tied into the Filters - so any filters now supports a hook into the notification system that is again controlled by Node.

Also added a BlockChain::confirmations method taking a tx_id hash and returning the number of confirmations.
Fixed bug in BlockChain::confirmations -> spend coins would never get a confirmation - forgot the parameter in the SQL query
Fix compilation with Clang
Merge pull request #67 from Midar/master

Fix compilation with Clang - on Yosemite
README.txt: fix link to Windows build info
Monotonic will return a strictly increasing ns resolution timer, but for s/ms/us two consecutive calls can return the same number (but never a smaller one)

Before each call to e.g. s() would make the second timer increase, which could get it out of sync
Peer interface cleanup - no functionality change
When sending own transactions using Node::post(txn) sometime they are stuck in sending - like all of them are stuck in sending.
Some improvements that could fix this:
1. when resending we also announce again to all peers
2. we are cleaning up better in the inv to send
3. we are flushing in case of a resend
Still, it seems like a node can end in a state where it only receives transactions and blocks, but never is able to send them - boost problem ?
Bug fix: We were never sending Pings - we started the suicide timer instead!
Merge pull request #68 from phelixbtc/patch-1

README.txt: fix link to Windows build info
Updated Dogecoin according to: http://www.reddit.com/r/dogecoin/comments/2egjqg/dogecoin_core_18_released_mandatory_upgrade/ - not tested!

Added DogeTest, not tested though as the DogeTest network seems rarely operating

Fixed Alerts to not notify unless AppliesTo us…

Changed from lazy purging to minimal purging as the default (to keep indexes from becoming too large) - minimal purging is now exactly the maturity for the chain.

Changed async_write_some to async_write - this could be the culprit for the strange behavior of not sending transactions to peers - simply if the connection was never properly flushed.
fixed ponzicoin (defaultPort was changed to unsigned short)
Fixed off by one in estimating confirmations for a coinbase input
Purging to “MINIMAL” can take ages on startup (if you switched from LAZY/FULL) - provided some progress code in the log for this basically cutting the process up in 10 pieces.