Releases: casper-network/casper-node
v1.1.1
First Upgrade for MainNet
- Include chainspec.toml version in handshake
- Limit deploy size to 1 MB
- Limit message size in chainspec.toml
- Deduplicate block validity criteria update
- Recursive query protection
- Additional costs for addBid (bonding and delegating will cost 3 CSPRs)
v1.0.1
v1.0.0
Summary
The Casper node is a pure Proof of Stake blockchain node that implements Highway Consensus on top of a Turing complete Virtual machine with smart contracting capabilities for wasm smart contracts. A single node client has been developed in Rust that implements the protocol. Development on the node client commenced in June, 2019 with the VM and global state store.
The Testnet program started in March 2020 with a naive Casper blockchain with 30 community participants. Participation was extended to 50 participants in July. The final testnet phase (Delta) commenced in November, 2020 and concluded with the launch of mainnet. The Delta phase demonstrated the permissionless protocol and hosted over 600 active participants
The node is configured to include 2500 token transfers and 100 wasm (smart contract) deploys per block.
The Casper Association has requested and CasperLabs plans to present and recommend a software upgrade to network participants in the next 30 days. The goal of the upgrade is to increase the performance of the network.
Installing node from Scratch:
https://github.com/make-software/how-to-casperlabs/blob/master/docs/ubuntu/setup-validator-from-scratch.md
v0.9.4
v0.9.3.1
v0.9.3
v0.9.0
v0.7.6
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.
v0.7.5
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.