Closed
Conversation
Contributor
Author
|
Closing in favour of #96 |
Contributor
Author
|
Re-opening. This caters for functionality not covered in #96 |
Contributor
Author
|
Sorry. Yes it's the same. Closing... |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This sapient can function effectively as a kill switch by using it as a 2/2 signer in conjunction with whatever feature we want to protect. e.g. OtherSapient (w:1) + FixedSapient (w:1) = threshold 2
Expect
FixedImageSapientto return 0x00 under active operations. Any change in value will result in an invalid signature on the wallet. This can also work as a versioning flag or similar for more complex situations.In the case of Trails, this would not block recovery etc as the owner can still be on the intent wallet as a 1/1 signer.
To disable, this must be updated on all affected chains.