Add NFT to TokenManagement #4365
Open
+634
−203
Conversation
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
vncoelho
reviewed
Dec 5, 2025
| { | ||
| Notify(engine, "NFTTransfer", uniqueId, from, to); | ||
| if (!callOnPayment || to is null || !ContractManagement.IsContract(engine.SnapshotCache, to)) return; | ||
| await engine.CallFromNativeContractAsync(Hash, to, "onNFTPayment", uniqueId, from, data); |
Member
There was a problem hiding this comment.
So, if the NFT creator wants to implement royalty, it will use this callback, right?
Member
Author
There was a problem hiding this comment.
This is a callback to the receiver contract.
ajara87
reviewed
Dec 6, 2025
| if (nft.Owner != from) return false; | ||
| if (!engine.CheckWitnessInternal(from)) return false; | ||
| StorageKey key = CreateStorageKey(Prefix_TokenState, nft.AssetId); | ||
| TokenState token = engine.SnapshotCache.TryGet(key)!.GetInteroperable<TokenState>(); |
Member
There was a problem hiding this comment.
Suggested change
| TokenState token = engine.SnapshotCache.TryGet(key)!.GetInteroperable<TokenState>(); | |
| TokenState token = engine.SnapshotCache.TryGet(key)!.GetInteroperable<TokenState>(); | |
| if (token.Type != TokenType.NonFungible) | |
| throw new InvalidOperationException("The asset id and the token type do not match"); |
Should not add a check like the fungible case?
Member
Author
There was a problem hiding this comment.
No need. It is obtained through nft.AssetId.
shargon
reviewed
Dec 7, 2025
| /// </summary> | ||
| /// <param name="integer">The integer value to set.</param> | ||
| public void Set(BigInteger integer) | ||
| public BigInteger Set(BigInteger integer) |
Member
There was a problem hiding this comment.
This can be void as before, just return the sum in the Add method
| [ContractMethod(CpuFee = 1 << 17, StorageFee = 1 << 10, RequiredCallFlags = CallFlags.All)] | ||
| internal async Task<UInt160> MintNFT(ApplicationEngine engine, UInt160 assetId, UInt160 account, Map properties) | ||
| { | ||
| if (properties.Count > 8) |
| const FindOptions options = FindOptions.KeysOnly | FindOptions.RemovePrefix; | ||
| var prefixKey = CreateStorageKey(Prefix_NFTOwnerUniqueIdIndex, account); | ||
| var enumerator = snapshot.Find(prefixKey).GetEnumerator(); | ||
| return new StorageIterator(enumerator, 21, options); |
Member
There was a problem hiding this comment.
Suggested change
| return new StorageIterator(enumerator, 21, options); | |
| return new StorageIterator(enumerator, Prefix_NFTOwnerUniqueIdIndex, options); |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Description
Add NFT to TokenManagement
Type of change
How Has This Been Tested?
Checklist: