Releases: casper-network/casper-node
v0.5.1
Release for Delta 8
This includes:
- changes to .deb logging to remove non-JSON prefix.
- Memory usage fixes
- Fix for bug when node does not join network if it finishes syncing immediately prior to an Era change.
v0.4.0
v0.3.1
v0.2.2
v0.2.1
v0.1.5
v0.1.4
This delivers additional economic and security features and a functional Rust network. Validators will receive seigniorage and the network will detect equivocations and slash validators in most cases. Nodes are able to join the network through ‘bonding auctions’ and validator set rotation. It is possible to observe where a given bid ‘ranks' and the number of open validation slots via a command line interface, and via queries of the status of the auction contract. Nodes can sync up state prior to participating in the auction and then join the network. New nodes joining the network will do so by obtaining a trusted hash from a bonded validator and then request finalized blocks from the validators and begin building up global state. As the network processes transactions, the node will emit ‘events’ through an ‘Event stream’ that will send event data to all subscribers. The first events that will be available are: ‘blocks_finalized’, ‘blocks_added’ and ‘deploy_processed’ events.
The network will emit all necessary metrics and logging as required by the SRE to monitor performance of the network itself as well as the validators on the network and debugging of any bugs.
DApp developers can use a Rust Client to create keys, send deploys, sign deploys and query nodes when using the system. DApp developers can also spin up a local network by using the network control tool - a set of bash scripts that enable to creation and destruction of networks for the purposes of testing