Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modification: Notary allocation address change - fixing Blotocol Japan's DataCap allocation address #106

Closed
dkkapur opened this issue Mar 24, 2021 · 9 comments
Assignees

Comments

@dkkapur
Copy link
Collaborator

dkkapur commented Mar 24, 2021

Issue Description

Based on the initial application in #56, the address granted DataCap is not usable for @MasaakiNawatani until tooling exists to support multisigs. In the meanwhile, it is recommend that we rotate the Notary's address to f1fh53sdaie3yi25qxwcqxpt5h4naex5ibdaffibi.

Impact

@MasaakiNawatani is unable to grant DataCap to clients until this is resolved.

Proposed Solution(s)

  1. Set DataCap allocation of f3rnnecpx2n5cxs5fsjrnqq32r3hacubkt45mnbywvcaskgwpfuzixdmydpcdmujwqwoe6l2oi4tzyj2zakjsq to 0TiB.
  2. Set DataCap allocation of f1fh53sdaie3yi25qxwcqxpt5h4naex5ibdaffibi to 10TiB.

Related Issues

Original application: #56

@dkkapur dkkapur self-assigned this Mar 24, 2021
@dkkapur
Copy link
Collaborator Author

dkkapur commented Mar 24, 2021

@MasaakiNawatani can you confirm that the addresses listed under the "Proposed Solution" are correct?

@dkkapur dkkapur changed the title Modification: Notary allocation address change - fixing Blotocol Japan's datacap allocation address Modification: Notary allocation address change - fixing Blotocol Japan's DataCap allocation address Mar 24, 2021
@MasaakiNawatani
Copy link

Hi Deep, thank you for helping out.

The correct address should be: f1fh53sdaie3yi25qxwcqxpt5h4naex5ibdaffibi

So yes, that is correct.

@dkkapur
Copy link
Collaborator Author

dkkapur commented Mar 24, 2021

Request Approved

Address

f3rnnecpx2n5cxs5fsjrnqq32r3hacubkt45mnbywvcaskgwpfuzixdmydpcdmujwqwoe6l2oi4tzyj2zakjsq

Datacap Allocated

0TiB

@MasaakiNawatani
Copy link

MasaakiNawatani commented Mar 24, 2021

Request Approved

Address

f3rnnecpx2n5cxs5fsjrnqq32r3hacubkt45mnbywvcaskgwpfuzixdmydpcdmujwqwoe6l2oi4tzyj2zakjsq

Datacap Allocated

0TiB

Hi @dkkapur , I checked my ledger and datacap allocation is still not showing on my correct address. Do I need to do anything on my end? Thanks.

@dkkapur
Copy link
Collaborator Author

dkkapur commented Mar 25, 2021

@MasaakiNawatani - at the moment no, we're waiting to ensure this message is being processed and then signed-on by Root Key Holders before proceeding with the next step.

@MasaakiNawatani
Copy link

@MasaakiNawatani - at the moment no, we're waiting to ensure this message is being processed and then signed-on by Root Key Holders before proceeding with the next step.

Got it. Hope it can be done sooner than later. Thank you, Deep.

@filecoin-plus-bot
Copy link
Collaborator

The request has been signed by a new Root Key Holder

Message sent to Filecoin Network

bafy2bzacedcn4cjvmjbu766r5bo3rl5fkrvcsrfco3zcpufqqwvzkwnke6kum

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

@filecoin-plus-bot
Copy link
Collaborator

The request has been signed by a new Root Key Holder

Message sent to Filecoin Network

bafy2bzacedy2e4ku5snnxwsyoha3cvzaec7wuwikcqclehy4jhglqadtr6zm6

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

@dkkapur
Copy link
Collaborator Author

dkkapur commented Apr 2, 2021

#113 was opened to track the corrected allocation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants