-
Notifications
You must be signed in to change notification settings - Fork 33
Add TransferHooks, Budget fix and upgrade to Polkadot v0.9.36 #261
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
Conversation
…s for implementation downstream for custom logic
Upgrade to polkadot-v0.9.33 & Add checkAllowTransferFn Trait
…when Nesting child NFTs to a parent.
Fix budget issue with Nested NFTs
Upgrade to polkadot-v0.9.34 and fix benchmarking
Update to polkadot-v0.9.36 and add call_index to pallets.
ilionic
left a comment
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.
LGTM
merged current main to polkadot-v0.9.29.
Let's merge this one so other benchmarking PRs could be updated as well.
Thank you!
I need to fix an odd build error. I didn't see this building and running locally. I'll have update asap. |
|
@HashWarlock do you think we can merge this one? So we can update other benchmarking PRs with API changes |
Good to merge now. Then we can update the rest |
Description
TransferHooks implementation
For implementations downstream of the RMRK pallet there needs to be an ability to add custom logic in the case that there are multiple pallets using the RMRK NFT pallet, but want to keep the business logic mutually exclusive. This implementation allows for a trait called
TransferHooksto be implemented with 2 functionspre_checkandpost_transferthat default totruewhen not implemented.Budget trait fix
There are 2 problems with the current Budget trait:
NFTs are currently allowed to mint and send NFTs to a parent NFT that can meet up to the threshold of NestingBudget::get() + 1. This allows for NFTs queries like lookup_root_owner to return errors like TooManyRecursions. Having this error is okay, but the NFTs should be prevented from being minted to or sent to a parent NFT if the Budget threshold is met.
Currently the code will do a calculation on functions like burn_nft and this will perform an arithmetic subtraction at the end of the function, but this should be added as a field in the Value type & implement a function from Budget to get the budget that has been consumed and budget that is left.
Update pallet index macro for pallet functions
This is a small change introduced in
polkadot-v0.9.36to add the pallet indexTargets
polkadot-v0.9.36TransferHookstrait withpre_checkandpost_transferfunctionsNestingBudget::get()value.budget_consumedand budget_left` to track & through errors is an overflow is detected.Budgettrait to get the 2 new fields.