Piers Shepperson

Providers

2

# Provider A provider is one of currently five objects that perform services for 0chian. There will be a linked wallet that can control the provider's settings. Each provider will...

EventDb: BlobberBlockRewards table

3

Table to hold blobber block rewards paid every block. This is dependant on https://github.com/0chain/0chain/issues/753. | BlobberBlockReward | Field | Note | |-------------------- |------- |-------------------------------- | | BlockId | uint |...

Cancel allocation request and BlobberChallenge object - improve performance

3

https://github.com/0chain/0chain/issues/533 should improve cancelAllocationRequest benchmark performance. This should be enough for `finalize_allocation`, but `cancel_allocation` had another problem due to its need to handle open challenges. The second problem is in...

Event db: Summary of changes

4

# Event database This issue gives a summary of the changes needed for the new event system. 0chain and 0chain smart contracts emit events that are picked up and used...

We need to make changes to the event database. I created this issue so we could brainstorm ways of increasing event database efficiency. Either for inspecting the code, load testing...

Make API naming consistant

1

We should make our API naming consistent, and according to guidelines https://adidas.gitbook.io/api-guidelines/rest-api-guidelines/evolution/naming-conventions we should use spinal-case (hyphens `-`).

The owner or other selected user should be able to kill a provider. This can use common code associated with a new embedded object (Provider or Killable) - For each...

Block rewards for miners and sharders

4

Currently, these are working fine, but use the [sc.yaml.minersc.block_reward](https://github.com/0chain/0chain/blob/staging/docker.local/config/sc.yaml#L46) entry. We want the miner and sharder block rewards to work on the same value as blobber block rewards https://github.com/0chain/0chain/issues/753. Plus...

Update allocation request - improve performance

2

Update location request is linear in the number of shards. The benchmark suggests taking around 2-4ms per shard, so only takes around 15 shards before exceeding 50ms. We could either...

Go import on each Pr commit

1

I noticed some files being committed that were not go formated. There is no reason to depend on developers for this. So I suggest a GitHub action to run `go...