Merged
Conversation
Three end-to-end tests exercising coalition reificator revocation: - revocation accepted: RevokeReificator governance tx removes key from datum - settlement rejected: spend attempt with revoked reificator key fails - negative: revocation of non-registered key rejected by validator
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.
Summary
DevnetRevocationSpecwith three end-to-end devnet scenarios for reificator revocation (US4 — Devnet E2E: full protocol flow test #9)RevokeReificatorgovernance tx removes key from coalition datum, shop key preservedOn-chain
RevokeReificator(Constr 2) and off-chainGovRevokeReificatorwere already implemented — this PR adds the test coverage.Test plan