[0.5.0.1] - 28-June-2019

Added

New catapult.broker process that pushes changes into MongoDB and and ZMQ.
New catapult.recovery process that repairs local state after ungraceful termination.
catapult.server produces file-backed messages that are consumed by catapult.broker.
Inflation support via new config-inflation.properties.
Implementation of harvest fee sharing and beneficiary specification.

Prevent transactions from being replayed on different networks by prepending the network generation hash to transaction data prior to signing and verifying.
Cosigners must opt-in before being added to a multisig account.
Allow use of same secret with different recipients by adding Recipient to SecretLockTransaction.
HashLockTransaction Mosaic supports aliases to to the currency mosaic.
Allow aggregate bonded transaction lifetime to be configured independently of other transactions.

Receipts record any state-dependent change not observable from the block header or transaction data. The block header stores the root hash of all the receipts linked to the block.
You can now attach namespaces and subnamespaces to addresses or mosaics using the AliasTransaction. A namespace can only be the alias of one account or mosaic at a time.
Remote harvesting has been enabled. Remote harvesting enables an account to use a proxy private key that can be shared with a node securely to calculate new blocks.
The base mosaic for currency is now configurable. This means other mosaic different than xem can be defined in private networks.
Properties FeeMultiplier and BeneficiaryPublicKey were added to the block header.
Transaction fee property was renamed to MaxFee.
Dynamic fee handling - Transactions specify max fee and blocks set fee multiplier, which determines actual fee paid.
Node reputation handling - When interacting with other nodes, each node will gather data, which will influence future partner node selection probability.

Mosaics are no longer tied to namespaces. This means a mosaic is no longer identified by the namespace. Instead, the identifier is a random uint64.
Mosaics can be set to not expire. This means there is no need to renew them. However, namespaces have to be renewed after a given count of blocks.
MosaicDefinitionTransaction comes with an additional 32-bit field called nonce. The nonce is a random value used to generate the mosaic ID.
SecretLockTransaction now supports Op_Sha3_256, Op_Keccak_256, Op_Hash_160, Op_Hash_256 hash algorithms.

Accounts can be configured to receive transactions only from an allowed list of addresses. Similarly, an account can specify a list of addresses that it doesn’t want to receive transactions from. The same behavior can be applied to allow or block transactions containing a given mosaic id or only allowing sending certain transactions by type.
Block header now stores the state root hash. Light clients will therefore be able to verify the state in a certain block rapidly.
Nodes can store chain state in a RocksDB when configured. This is useful for networks with a large number of accounts, as it demands less memory from network nodes.