-
Notifications
You must be signed in to change notification settings - Fork 58
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
Comments
@MasaakiNawatani can you confirm that the addresses listed under the "Proposed Solution" are correct? |
Hi Deep, thank you for helping out. The correct address should be: f1fh53sdaie3yi25qxwcqxpt5h4naex5ibdaffibi So yes, that is correct. |
Request ApprovedAddress
Datacap Allocated
|
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. |
@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. |
The request has been signed by a new Root Key HolderMessage sent to Filecoin Network
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedcn4cjvmjbu766r5bo3rl5fkrvcsrfco3zcpufqqwvzkwnke6kum |
The request has been signed by a new Root Key HolderMessage sent to Filecoin Network
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedy2e4ku5snnxwsyoha3cvzaec7wuwikcqclehy4jhglqadtr6zm6 |
#113 was opened to track the corrected allocation |
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)
f3rnnecpx2n5cxs5fsjrnqq32r3hacubkt45mnbywvcaskgwpfuzixdmydpcdmujwqwoe6l2oi4tzyj2zakjsq
to 0TiB.f1fh53sdaie3yi25qxwcqxpt5h4naex5ibdaffibi
to 10TiB.Related Issues
Original application: #56
The text was updated successfully, but these errors were encountered: