Stellar, the blockchain payment network, announced that a new version of the stellar-core has been successfully released.
The stellar-core is the backbone of the Stellar network. It maintains a local copy of the ledger, communicating and staying in sync with other instances of stellar-core on the network. Optionally, stellar-core can store historical records of the ledger and participate in consensus.
The full release notes and source can be found on GitHub.
See highlights of the release below:
- Now distinguish peers that it never heard of from peers that have been able to be connected to. This should increase the overall quality of peers that are being used by the network.
- SCP: there was a minor issue in the SCP code (nomination protocol) that could cause excessive timeouts in some cases.
- archive nodes would sometimes fail to publish, causing retries and delays in publishing new snapshots
- fixed issue where the COMMANDS config was not working properly on startup
- improved performance when processing failed trades in the order book
- fix crash when starting two stellar-core processes sharing the same buckets folder
- improved performance and reliability when downloading files during catchup
- performance: avoid creating too many files in the same folder during catchup
- performance: avoid forwarding too many messages when peers connect to each other
- updated to latest asio release
- metrics have been simplified and documented
- added progress meter when catching up (applying bucket)
- ability to log (debug/trace) transactions and their results
- SCP status includes delayed validator information to help identify slow validators in quorum
- new command line format now accepts global switches anywhere (ie before or after sub-command name)
- Removed deprecated config element MAX_PEER_CONNECTIONS – use MAX_ADDITIONAL_PEER_CONNECTIONSinstead (review docs/stellar-core_example.cfg for more detail)
- Removed built-in NTP client to warn operators that their machine has a drifting clock. Use operating system NTP client instead.
- “info” endpoint got simplified (removed detailed information on archives)
- “peer” endpoint got expanded to include outbound/inbound information