Piers Shepperson

Needed for https://github.com/loomnetwork/loomchain/pull/865/ Needed for https://github.com/loomnetwork/loomchain/pull/995

Cancellation charge

6

## Fixes * Add cancellation charge - paid whenever an allocation shuts down. * The allocation write pool should start with the total allocation cost. * Ensures there is always...

Misc endpoint changes for block rewards system tests

3

## Fixes `/transactions` did not work for getting transactions between two rounds. `/get_blocks` add the missing filter to get blocks between two rounds. add options to include the transactions in...

Modify Event database to avoid corruption on sharder shutdown

1

When the sharder shuts down event database processing is stopped, all local information in RAM is lost. This currently can lead to the event database getting corrupted.

StorageNode.Information, we don't need to store this in the MPT. Need to confirm whether we need this in the event database. Remove as necessary from transactions and objects. ```go //...

Blobber and validator, health check kill and shut down

10

## Fixes Closes https://github.com/0chain/0chain/issues/1040, Closes https://github.com/0chain/0chain/issues/1044, Closes https://github.com/0chain/0chain/issues/1045, Closes https://github.com/0chain/0chain/issues/1046, Closes https://github.com/0chain/0chain/issues/1020 1. New `health_check_period` setting. 2. Providers can now be deactivated. While deactivated providers will not be available for...

Add round number to [nodeStat](https://github.com/0chain/0chain/blob/staging/code/go/0chain.net/smartcontract/minersc/handler.go#L56). Other endpoints to be added ...

Miner sharder, kill and shut down

2

## Fixes Adds kill and shutdown endpoints for miners and sharders. Related to https://github.com/0chain/0chain/pull/1439 issues: https://github.com/0chain/0chain/issues/1040, https://github.com/0chain/0chain/issues/1044, https://github.com/0chain/0chain/issues/1045, https://github.com/0chain/0chain/issues/1046 ## Changes ## Need to be mentioned in CHANGELOG.md? ## Tests...

Add challenge pools to event database

2

We should add the challenge pool to the event database. We can add to the [event.Allocation table](https://github.com/0chain/0chain/blob/staging/code/go/0chain.net/smartcontract/dbs/event/allocation.go#L16). Change to [getChallengePoolStat](https://github.com/0chain/0chain/blob/staging/code/go/0chain.net/smartcontract/storagesc/handler.go#L670).

Challenges from interval

1

Add fields to [Challnge](https://github.com/0chain/0chain/blob/staging/code/go/0chain.net/smartcontract/dbs/event/challenge.go#L14) table. * The data the challenge was resolved * pass or fail These values can be added to the `TagUpdateChallenge` emitted from verifyChallenge. https://github.com/0chain/0chain/blob/staging/code/go/0chain.net/smartcontract/storagesc/challenge.go#L534 and https://github.com/0chain/0chain/blob/staging/code/go/0chain.net/smartcontract/storagesc/challenge.go#L600...