Currently tooling exists that will attempt to partially automate the removal process in reaction to inactivity. It would also be valuable to have a way to manually request removal of datacap, either that an allocator has mistakenly given, or as a result of identification of compliance violations.
We're working on a tool for this purpose, and will be requesting the addition of verifier accounts to be added to the verified registry that can perform the 'verifier signatures' associated with removal requests. Root Key Holders will, through the current technical process, remain as humans in the loop for any removal of datacap, but we hope to reduce the associated friction from the current 4 manual steps down to 2 manual steps.
willscott
commented
6 months ago
There has been work on automating the datacap removal process previous, .e.g https://github.com/filecoin-project/notary-governance/issues/983
Currently tooling exists that will attempt to partially automate the removal process in reaction to inactivity. It would also be valuable to have a way to manually request removal of datacap, either that an allocator has mistakenly given, or as a result of identification of compliance violations.
We're working on a tool for this purpose, and will be requesting the addition of verifier accounts to be added to the verified registry that can perform the 'verifier signatures' associated with removal requests. Root Key Holders will, through the current technical process, remain as humans in the loop for any removal of datacap, but we hope to reduce the associated friction from the current 4 manual steps down to 2 manual steps.