Modification: Notary allocation change - Fleek not serving as a Notary in the near term

[dkkapur]

Issue Description

Fleek (Notary App: #47) is stepping back from Notary responsibilities for the time being. As a result, DataCap granted to their address should be removed.

Impact

100TiB of DataCap has been granted to an address opting not to serve as a Notary at the moment.

Proposed Solution(s)

Set DataCap allocation of address f2lda563hy3q2oxnoo265elynct3u2ft27ae7ptfy to 0TiB

Related Issues

Original Notary application: #47

[dkkapur]

This was discussed in the previous two Notary governance calls and there was consensus among those present that:

• this is an acceptable step a Notary can take
• the course of action is to set the Notary's DataCap allocation to 0
• if in the future, the Notary chooses to serve again, they must go through the application process as would be the case with any new Notary applicant applying
• the decision to step back from a Notary role is not held against the Notary in future application rounds

[dkkapur]

Request Approved

Address

f2lda563hy3q2oxnoo265elynct3u2ft27ae7ptfy

Datacap Allocated

0TiB

[filecoin-plus-bot]

The request has been signed by a new Root Key Holder

Message sent to Filecoin Network

bafy2bzacedazlqqahqin5gvzdhqvckqu6dcgvmzs7asbrubigj5i6smlyr3k4

You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedazlqqahqin5gvzdhqvckqu6dcgvmzs7asbrubigj5i6smlyr3k4

[filecoin-plus-bot]

The request has been signed by a new Root Key Holder

Message sent to Filecoin Network

bafy2bzaceaxeji3w2gyiwnzmqexfu6rg4tuh6mgiobniuoppafmd6jwqcud5a

You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceaxeji3w2gyiwnzmqexfu6rg4tuh6mgiobniuoppafmd6jwqcud5a