-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XLS-46: DynamicNFT #5048
Merged
Merged
XLS-46: DynamicNFT #5048
Changes from 24 commits
Commits
Show all changes
47 commits
Select commit
Hold shift + click to select a range
598a0e3
XLS-46 dNFTs PR first
d851678
dNFTs initial
xVet e30addc
added dnft amendment and placed guards
xVet 0848a98
Merge branch 'XRPLF:develop' into dNFTs-XLS-46
xVet 624e11e
added featureDNFT in Feature.h
xVet 4cbde96
Merge branch 'dNFTs-XLS-46' of https://github.com/xVet/rippled into d…
xVet afaa675
Merge remote-tracking branch 'upstream/develop' into dNFTs-XLS-46
tequdev f6418aa
dNFTs
tequdev 44790ab
rename dNFT to DynamicNFT
tequdev ef6ba44
clang-format
tequdev b9becc4
fix flag test
tequdev 8fd988d
add standard license/disclaimer text
tequdev 68a51e1
Merge remote-tracking branch 'upstream/develop' into dNFTs-XLS-46
tequdev 750adda
chore
tequdev 4b3480c
fix tests
tequdev f4ab8c6
Merge remote-tracking branch 'upstream/develop' into featureDynamicNFT
tequdev 47106cc
Merge branch 'develop' into featureDynamicNFT
tequdev 4ca5105
Merge branch 'develop' into featureDynamicNFT
tequdev 579dc25
[FOLD] An incremental approach to the tfNFTokenMintMask variants
scottschurr cae9b62
[FOLD] Extend testNFTokenModify unit test
scottschurr 23ecb99
[FOLD] Avoid NFTPage coalescing and splitting when URI changes
scottschurr 2eb7559
fix sorting testcase
tequdev e9dd06c
Merge branch 'develop' into featureDynamicNFT
tequdev c89f41d
Merge branch 'develop' into featureDynamicNFT
tequdev 1b2cf6d
Merge branch 'develop' into featureDynamicNFT
tequdev d52b659
Merge branch 'develop' into featureDynamicNFT
tequdev 90aeef9
fix testcase name
tequdev 4eea716
chore: fix typo
tequdev 321459d
Merge branch 'develop' into featureDynamicNFT
tequdev b41b98a
Merge branch 'develop' into featureDynamicNFT
tequdev fc81bcc
clang-format
tequdev 0f02668
Merge branch 'develop' into featureDynamicNFT
tequdev fa732bf
Merge branch 'develop' into featureDynamicNFT
tequdev 16541e2
fix bad merge
tequdev a76809a
clang-format
tequdev e3f6542
Merge branch 'develop' into featureDynamicNFT
tequdev 29e7d4d
fix merge
tequdev 727ad8f
Merge branch 'develop' into featureDynamicNFT
tequdev d26ba5a
Merge branch 'develop' into featureDynamicNFT
tequdev a6aaa28
Merge branch 'develop' into featureDynamicNFT
tequdev 7154534
Update src/xrpld/app/tx/detail/NFTokenModify.cpp
tequdev 13156dd
Fix error handling that shoudn't be possible
tequdev f6f8084
clang-format
tequdev ca09114
Merge branch 'develop' into featureDynamicNFT
ximinez 7390b1d
fix build error
tequdev f7311ba
fix tt tag
tequdev ccbed88
Merge branch 'develop' into featureDynamicNFT
tequdev File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The spec (XRPLF/XRPL-Standards#130 August 18, 2023 version) specifies that the
sfURI
field is required. Here it is listed assoeOPTIONAL
. I think thatsoeOPTIONAL
is a good choice, because that matches the behavior ofNFTokenMint
. Perhaps the spec needs to be updated?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since you pointed it out, as of Jun 29 the
sfURI
field has been updated to an optional field.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there any use case for removing the URI from an existing NFT? Is there any difference from burning the NFT compared to an NFT without a URI?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Such a use case may not be common, but it is not impossible to say that there is no use case.
Since the NFTokenMint transaction can be executed with the URI field unspecified, it is reasonable that the NFTokenModify transaction can change the URI field to unspecified.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense. Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should there be a flag for removing the URI from the NFT, like with
NFTokenMinter
, instead of just using its absence?