Removing Fantom from BIP-681 #1282
Merged
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
…Balancer chain, nor does it have the standard DAO signers as a starting point.
|
pertains to #681 and |
gosuto-inzasheru
approved these changes
Aug 26, 2024
There was a problem hiding this comment.
removes fantom msig from bip681 payload. fantom is not a prod chain for balancer and its current list of owners is not up to date
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.
as it is not a DAO multisig on a active Balancer chain, nor does it have the standard DAO signers as a starting point.
Note that #916 deals with the safe in question, it has still not been executed as the Fantom Safe UI dropped all state in the middle of the signing process and we have not yet taken the time to try again.