Fix use of anchor/bundle opret/tapret dichotomies #277
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.
Due to use of two different DBC commitment schemes, tapret and opret, a witness transaction may contain two different DBC commitments, and, thus, anchors. Before v0.11.0-beta.6, there was a 1-to-(1,2)-to-(1,2) relation between witness transactions, anchors and state transition bundles. v0.11.0-beta.6 introduced that each bundle must be used just in a single anchor, and thus, has to commit to a specific DBC scheme. This PR completes implementation of this feature basing on test-driven approach from RGB-WG/rgb-tests#6