Technical Release notes and Changelog for 0.9.1 - draft
Things you need to know:
There are updated contracts. Obtain a fresh set of contracts & recompile. Visit docs.casperlabs.io and review the Node Operator guide for instructions.
There is a new component called the casper-node-launcher. 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.
The genesis files are now stored within a version directory. The first version is 1.0.0 - therefore the chainspec, and config.toml are under /etc/casper/1_0_0/ .
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.
To test the rotation of validators in the auction, we have reduced the number of auction slots to 75. We recommend that folks try unbonding & withdrawing rewards during this phase also.
Use the --gas-price =1 parameter now in all transactions. The client doesn’t require it yet, but it will soon
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 unforeseen restart, synchronization will be faster and more efficient.
There is a new chainspec.toml file. This is to support the node launcher. Here is the diff.
There will be information in the status endpoint that expresses the version of the node launcher that is installed. This is to help track the peers that are ready for an upgrade in the future.
Delegation rate has changed from u64 to u8.
Known Issues
Nodes that go offline cause liveness faults. Before turning off your node, please ensure you unbond and wait for the unbonding wait period before shutting your node off. Help us to keep the network up!
If your bids don’t go through, or you get a weird auction error, you need to update your contracts. Grab the contracts for release-0.9.x and compile them.
There are a lot of deploys in the network, if you observe an error on the event stream like this, it is because the data is streaming faster than curl can process it. Simply restart the curl.
curl: (18) transfer closed with outstanding read data remainingWith heavy usage, disk grows. For production, we recommend 1TB of storage. We have planned work to reduce disk requirements.
Network Info
chain_name: "delta-11"
genesis_root_hash: "8fe7..4899"
github tag for compiling contracts: release-0.9.1
Contract Compilation instructions
git clone https://github.com/CasperLabs/casper-node.git
cd casper-node
git fetch
git checkout release-0.9.1
make setup-rs && make build-client-contracts -jNode Installation Instructions - to be updated
#### delta 10 ####
sudo systemctl stop casper-node
sudo systemctl stop casper-node-launcher
cd ~
sudo apt remove -y casper-node
sudo apt remove -y casper-client
sudo apt remove -y casper-node-launcher
# Clean up old genesis file location
sudo rm /etc/casper/config.*
sudo rm /etc/casper/accounts.csv
sudo rm /etc/casper/chainspec.toml
sudo rm /etc/casper/validation.md5
curl -JLO https://bintray.com/casperlabs/debian/download_file?file_path=casper-node-launcher_0.2.0-0_amd64.deb
curl -JLO https://bintray.com/casperlabs/debian/download_file?file_path=casper-client_0.7.6-0_amd64.deb
sudo apt install -y ./casper-client_0.7.6-0_amd64.deb ./casper-node-launcher_0.2.0-0_amd64.deb
cd /etc/casper
sudo -u casper ./pull_casper_node_version.sh 1_0_0
# Get trusted_hash into config.toml
curl -s 18.144.176.168:8888/status | jq -r .last_added_block_info.hash
# Or do this automatically
sudo sed -i "/trusted_hash =/c\trusted_hash = '$(curl -s 18.144.176.168:8888/status | jq -r .last_added_block_info.hash | tr -d '\n')'" /etc/casper/1_0_0/config.toml
sudo logrotate -f /etc/logrotate.d/casper-node
sudo /etc/casper/delete_local_db.sh; sleep 1
sudo systemctl start casper-node-launcher
systemctl status casper-node-launcherDetailed List of Changes
Pull Request Number & Title | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|