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

Update 20231005-Adding-bluesign-as-multi-sig.md #222

Merged
merged 2 commits into from
Jan 11, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion governance/20231005-Adding-bluesign-as-multi-sig.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
Status: Draft
Status: Released
Flip: 208
Authors: Kshitij Chaudhary ([email protected])
Sponsor: Kshitij Chaudhary ([email protected])
Expand Down Expand Up @@ -76,3 +76,10 @@ The user impact of this proposal is negligible and is primarily related to gover
- Do community members support the inclusion of @bluesign as a signer, and if so, are there any specific expectations from his role?

Your feedback and input on this proposal are highly valued, and we look forward to discussions and consensus-building regarding the addition of @bluesign as a multi-sig signer.

> This FLIP has now been implemented as part of the following service account and staking account transactions, respectively,
>
> https://flowscan.org/transaction/d565222c819d18a8951624ce65a9b8875879c864bcf27cadb6767ea5a1d669e9
>
> https://flowscan.org/transaction/a9aaf36be4d873a31dbd7e671f13709e6b76e9991bdd5344bb54b6ae592b59b1
> >