Features/updates for tsc spec compliance#1
Merged
Conversation
…liance - Rename `PaymentRequest` -> `PaymentTerms` as `PaymentRequest` was the old BIP270 terminology for this struct - Update the payment.go:Validate() method for the new `Payment` struct
…ing to place each of the three dpp message type structs in their own folders
…Envelope` wrapped `PaymentTerms` as the standard.
…hese fields do not feature in the TSC specification
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
2 participants
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.
See here for original description:
libsv#69
The ElectrumSV develop branch has been running against this version since July 2022 so it's time it was merged. Hence the fork.