ZSA integration (step 5): Modify Orchard proptest implementations to support ZSA #18
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.
Updates the existing Orchard property-based test implementations to include transaction V6 ZSA fields (
burn
inShieldedData
andorchard_zsa_issue_data
).Changes:
TestArbitrary
trait toorchard_flavor_ext
to conditionally modify the list of constraints forEncryptedNote
andBurnType
associated types.Arbitrary
fororchard::ShieldedData
as a generic type.Burn
, which wrapsVec<BurnItem>
. Implemented serialization/deserialization for it and placed it inorchard_zsa/burn.rs
. Also movedNoBurn
there fromorchard_flavor_ext.rs
for better code structuring.serialize.rs
tocommon.rs
in theorchard_zsa
folder.v5_strategy
andv6_strategy
functions intransaction/arbitrary.rs
to work with V5 and V6 transactions, and to handle burn and issuance for V6.Note: This is draft code that needs to be cleaned up, possibly refactored/improved, and the FIXMEs resolved.