v0.7.6
Pre-release
Review the Node Operator guide for instructions and hardware requirements for running a node.
There is a new component called the casper-node-launcher, which implements CEP-0032 . This component runs the node software, and switches the version of the software at a future upgrade point when the point is reached. This is how upgrades will function on the Casper network.
The system will not issue refunds for payment-amount. It assumes that all of the payment amount is consumed as transaction fees. Provide 1000000000 for your payment-amount parameter when sending a bid.
Bids for validator slots need to be sent to localhost. Do not send bid transactions to another node. This prevents liveness faults, as your node will not gossip a deploy until it is synchronized with the network.
As a best practice, we recommend updating the trusted hash in config.toml (for a running node) to be updated at some interval of your choice. This way, in the event of an unforseen restart, synchronization will be faster and more efficient.
The structure of the chainspec.toml file has changed to support the node launcher.
There will be information in the status endpoint that expresses the version of the node launcher that is installed. This is to help inform the validators which of the peers that are ready for an upgrade in the future.