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
[Allocator #1015] Unrecognized , Update a new Leger address #25
Comments
Hi @Bitengine-reeta , Thanks for submitting this ticket. Wanted to let you know it was received and being worked. Will echo back shortly when completed (or additional information is needed) Warmly, |
@Kevin-FF-USA Thanks a lot! |
please update as this:
|
@galen-mcandrew @Kevin-FF-USA @willscott @jbenet Any update? |
The associated address is not related to signing DataCap through your pathway, it is used to reference org-level addresses that may be managing multiple pathways. It sounds like you are requesting a new multisig, but that would require the Root Key Holders removing the DataCap and issuing to a new f2. The f2 address was created by your team, and provided to the GovTeam and RKH, so we do not have the ability to add other signers to that msig. This address (f2p2yz6iv33uiz6snsbgheuvwa4cjclcpi46fpbkq) has 1 signer ( |
@galen-mcandrew |
|
|
@galen-mcandrew @Kevin-FF-USA |
Allocator Pathway Number:
1015
Allocator Pathway Name:
Bitengine Reeta FIL+
Change Request:
The unrecognized Leger address needs to be updated to a new Leger address, and then a new multi-signature address is created for the new Leger address.
f15x23zuhctuqz77tvkzthow3xkpvn3q4kjgxpgya
f1km6utrorrtqh572e3ybfu7jq2gfktkgfghscr6i
f2jh575hxrtfjl7uvu5ymfzrpfyq45fnhvhlajjdi
The text was updated successfully, but these errors were encountered: