GuruHubb

We also have rate limits for miners and sharders, which needs to be there for other providers (blobber, authorizer, validator) ``` large_message_th_size: 5120 # anything greater than this size in...

@Sriep Cancellation charge **replaces** min_lock_demand payment and is same to all the blobbers. It is a flat fee set in the global network config. For new allocation, clients need to...

@Sriep @dabasov just so we're clear the blobber receives the cancellation charge regardless of whether the client writes or cancels their allocation and the allocation expires. The blobber can finalize...

I talked to @sum-it08 to sort it all out. There is a lot of confusion and this is the wrong forum for a discussion. Also we have not removed allocation...

Client can use repair to add data to new blobber and the blobber can remove data when they see their contract is expired. @lpoli @Sriep

@Kishan-Dhakan is the add/drop blobber feature part of system tests? @lpoli can we close this issue?

@Sriep, please make this generic that applies to any allocation. We don't need to use the `--nft` flag at all. The defaults can be `true` for all CRUDs, `mutable`, and...

@Sriep item 6 is not necessary. The default for any allocation is all CRUD operations are true. For NFT, the client sets some of them as false if they want...

@avanaur can you work on this. @dabasov this needs to be done on the blobber repo as a table

This is taken care at the blobber side. See https://github.com/0chain/blobber/pull/891