FLIP GOV-6 - Addition of @bluesign as a multi-sig signer #207
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Editing FLIP sponsor description
* random function updates: * update name to revertibleRandom * add new optional modulo argument for randoms less than N * extend function signature to all fixed-sized unsigned integers * clarify behaviour for function called within a script Co-authored-by: Bastian Müller <[email protected]>
Add a new "released" status for the FLIP
Tweaking the formula to introduce the 90kB storage bonus - based on community feedback
Update 20201125-bip-44-multi-account.md Update 20201125-bip-44-multi-account.md
Update 20221108-fcl-specification.md Update 20221108-fcl-specification.md
|
Why is the FLIP in the PR description? Why is the PR merging |
|
Is there any documentation on what being a Flow "multi-sign signer" means? |
Yes thanks - my bad. Closing this and starting a new one. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Objective
The objective of this FLIP is to seek community approval for the inclusion of @bluesign as a signer in the multi-signatory process on the Flow blockchain. This addition aims to leverage @bluesign's expertise and experience to enhance the governance and decision-making capabilities of the network.
Motivation
@bluesign is a distinguished member of the Flow community, boasting a track record as a serial founder, game developer, and a strong background in mathematics and engineering. This combination of skills and experience makes @bluesign an ideal candidate to contribute to the governance process on Flow.
The motivation behind this proposal is to benefit from @bluesign's unique insights, industry knowledge, and commitment to the Flow ecosystem. By adding @bluesign as a signer, we aim to bolster the network's decision-making capacity and further align our governance with the best interests of the community.
User Benefit
The addition of @bluesign as a signer in the multi-signatory process will strengthen governance processes with a diverse set of perspectives, leading to enhanced decision-making capabilities to address critical issues and drive improvements to the Flow network.
Design Proposal
Drawbacks
There are minimal drawbacks associated with this proposal; however it's essential to ensure that @bluesign's role as a signer is in line with community expectations and the network's long-term goals, and is transparently communicated - which is one of the goals of this FLIP.
Alternatives Considered
@bluesign's unique qualifications and contributions to the Flow community make him a compelling choice for this role.
Performance Implications
This proposal is not expected to have any significant performance implications on the Flow network. It primarily concerns governance and decision-making processes.
Dependencies
This proposal does not introduce new dependencies to the Flow blockchain. It is a governance-related change and does not affect core functionalities or dependent projects.
Engineering Impact
There is no direct engineering impact associated with this proposal. The addition of @bluesign as a signer involves administrative and governance considerations.
Best Practices
This proposal aligns with best practices for enhancing governance by adding experienced and knowledgeable community members to decision-making roles.
Tutorials and Examples
No tutorials or examples are required for this proposal, as it pertains to governance and signer addition.
User Impact
The user impact of this proposal is negligible and is primarily related to governance improvements. Users can expect a more robust decision-making process with the addition of @bluesign.
Questions and Discussion Topics
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.