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

Label multisig as unsafe, not experimental, as #8149 isn't merged #8387

Closed
wants to merge 2 commits into from
Closed

Label multisig as unsafe, not experimental, as #8149 isn't merged #8387

wants to merge 2 commits into from

Conversation

kayabaNerve
Copy link

These aren't maybes. These are facts which need to be communicated. "experimental" was a term chosen expecting #8149 to be merged. Since it hasn't been yet, it's being misapplied to the current multisig code while simultaneously implying #8149 (the experimental code) was merged. This clarifies expectations and ensures a lack of confusion/misunderstandings.

The other option given the current state of multisig would be to disable it at the compilation level, which would provoke distribution of modified binaries which is its own mess. This is the path of least resistance to ensure proper communication in the next release despite #8149's current non-presence.

Update to #8328. Prompted by the most recent MRL meeting.

Copy link
Contributor

@UkoeHB UkoeHB left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Until @8149 is merged, this would communicate the state of multisig more accurately.

@selsta selsta closed this Jul 13, 2022
@kayabaNerve kayabaNerve deleted the unsafe-multisig-label branch July 13, 2022 04:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants