Do not keep explicit data on seal close method in DBC anchor #105
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.
The anchor contains an explicit DBC proof, which commits to the seal closing method by its type.
This PR also relaxes 1-to-1 match between DBC data type and closing method: before a DBC type was usable only for a single close method (since it
dbc::Proof
had aMETHOD
as a const). Now, enumeration DBC types, with different closing methods for each of the variants are supported. This API change was required for fixing a bug downstream in RGB crates prevending from using operations involving multiple seal seals with different closing methods simultaneously.