You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is the Github Account used to file this request is already recorded on the Allocator JSON for your organization?
No
Additional Information
Hello, due to internal personnel changes, the previous account is no longer associated with Metaera and has been deactivated. We have created a new account specifically for management purposes. Kindly update this account as the official Metaera allocator account. Thank you for your support!
The text was updated successfully, but these errors were encountered:
Hello @Kevin-FF-USA and @galen-mcandrew
The previous account is no longer associated with Metaera and has been deactivated. Sorry for the inconvenience we caused. I will dm you through our slack account to prove my identity.
Additionally, there is still 4 PiB of capacity in my previous channel that hasn’t been signed yet. Will this impact the dc allocated to my address? What steps should I take next to record the json file to this new account?
I still have control of the ledger. I don't have to change the singer address, just modify the GitHub account.
Organization
Metaera
Applicaiton Number
1029
Updated Github
metaeraworkops
Would you like to
Modify an existing Github Handle
Is the Github Account used to file this request is already recorded on the Allocator JSON for your organization?
No
Additional Information
Hello, due to internal personnel changes, the previous account is no longer associated with Metaera and has been deactivated. We have created a new account specifically for management purposes. Kindly update this account as the official Metaera allocator account. Thank you for your support!
The text was updated successfully, but these errors were encountered: