Tari base node v0.5.6 released

Tari Base Node v0.5.6 released with hard fork changes
Release v0.5.6 comes with a number of improvements to the distributed hash table (DHT) network and block propagation
strategy. These aim to solve the problem of nodes getting isolated from the network.
This version also has some consensus rule changes that some into effect on block 120,000. This should be mined some
time on Sunday 18th October. These changes will fork the chain, so we encourage all testnet node operators and miners
to upgrade to v0.5.6 as soon as possible. The rule changes fix, among others, an issue on the monero block difficulty calculation
and switching the emission curve to pure integer-based math.
Major features since v0.5.5
Propagate block hashes to all connected nodes
Fixed difficulty calculation on Monero proof of work blocks
Remove floating-point calculation from achieved difficulty
Introduce peer syncing and network discovery to improve a node’s overall knowledge of the network
Improve
Closest
broadcast strategy and use it for SAF transaction broadcast
Implement variation of block percentage between proof of work algorithms
Use an integer-based emission curve to replace floating-point emission curve after testnet block 120000
Minor changes since v0.5.5
Allow client application to control when transaction broadcast protocols are restarted
Expose kernel excess, public nonce, and signature via wallet FFI
Fix possible inflation bug
Only update mempool after block sync is complete
Add the ability to search for blocks containing transaction kernels via GRPC
Refactored to get the actual reason a tx failed to be logged
Reduce ban time for sync peers
Decouple Mempool and BlockchainDatabase
Optimisation for MMR + clippy fixes
Delay UTXO validation process until after initial blockchain sync has been achieved
Implement tools to produce network graphs in memory net examples
Add daily binary build for Tari Base Node with S3 upload
Allow fee to be larger than the amount per configuration setting, to allow spending dust in some edge cases
Fix Name collision in
Add reason peer is banned
Implement STXO validation in the wallet’s Output Manager Service
Handle runtime error by removing an unnecessary dial-peer command, otherwise, when sometimes it is not successful, the code panics
Add examples for Service Framework
Fix target difficulty for block 1 on rincewind
Cache orphan pool results in memory
Refactor basenode/wallet/p2p initialization
Add the Mempool RPC service
Add list-banned-peers command to base node
DHT RPC get_peers returns all peers and “on connect” mode for NetworkDiscovery
Add recovery mode
Add chain tip tracking of all peers
Allow the chain meta service to react to banned peers by removing them from its internal collection
Base node shuts down cleanly