v0.6.2

New Features

• bumped the protocol version
• added an option to turn on "invariant checks". These are conditions that if they ever occur mean there is a bug in the protocol or a widespread implementation so the network should halt until they can be fixed. This replaces PARANOID_MODE in the .cfg. It allows you to have stellar core check that the lumen balance in the system is correct and a few other things. (more info)[https://github.com/stellar/stellar-core/blob/master/docs/stellar-core_example.cfg#L233]. It is recommended you run stellar-core with these set to "true" until the load of the checks becomes an issue.
• more extensive tests
• add --base64 command line option
• add --priv2pub command line option

Fixes

• hide database password from log
• fixed several issues with how account data was cached for multiple operations during a single transaction
• fix multiple merge issue that could generate lumens
• fix issues with path payment that could destroy lumens
• fix inflation bug that would calculate the wrong amount under rare circumstances

v0.6.1

New Features

• bumped the protocol version

Fixes

• fixed issue with qsets falling out of cache that was leading to random delays in ledger closes
• fixed manage data issue

v0.6

New Features

• bumped the protocol version
• New signing types
  • hash(x)
  • pre-authorized transaction
• added PREFERRED_UPGRADE_DATETIME as an optional .cfg parameter. Allows the network to better coordinate an upgrade date.
• An account can no longer add a trustline to itself
• --signtxn now allows you to specify network to sign for
• improved error messages

Fixes

• orderbook issue
• speeds up and more reliable catchup
• small bug fixes
• stability improvements

v0.5.1

New Features

• tmp directory no longer specified in config file
• added --signtxn for using stellar-core to sign transactions from the command line
• --info now displays when your clock is out of sync
• man page
• improved peer management
  • added, droppeer, bans and unban

Fixes

• speeds up catchup
• small bugs
• stability improvements

v0.5.0

New Features

• Adding a new DataEntry ledger entry type.
• don't allow new features until the network has upped the protocol version high enough
• add HTTP_MAX_CLIENT config
• Improved load testing

Fixes

• small bugs

v0.4.1

New Features

• Added a CATCHUP_RECENT mode that allows a node to fetch the last N ledgers when joining the network.
• Added checkquorum command. Check quorum intersection from history.
• Added graphquorum command. Print a quorum set graph from history.
• Added inferquorum command. Print a quorum set inferred from history.

Fixes

• Reworked history system. Interface to the world is the same but it should work much better than before.
• Changed the definition of quorum slice to not need to include yourself. Your node is no longer automatically added to your quorum set.

v0.4.0

New features

• New meta data emitted (previous ledger entry state) - see #944
• Perform maintenance on startup by default for nodes not in CATCHUP_COMPLETE mode (this reduces the disk space requirement for those nodes as data is purged more often)- see #947
• Additional QUORUM_SET validation - as described in f9286a6 and fa048e6

Fixes and improvements

• Major history publish/download overhaul, to improve reliability of interactions with history subsystem - see #951
• Validators only forward messages from the extended quorum - this closes a potential attack vector to DoS validators
• Avoid triggering catchup from history when restarting a node after a short downtime
• Improved "quorum" reporting

v0.3.3

• Fix bug causing catch up to get stuck
• Better insight into what SCP is doing
• Better logs for debugging

v0.3.2

fix: crash in SCP when receiving some v-blocking CONFIRM

v0.3.1

Snap implementation of SCP to the version dated November 17 2015