You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently working on an escrowless NFT marketplace utilizing Core assets. I've identified a potential issue where the owner of a Core asset can remove TransferDelegate plugin using RemovePluginV1 at any time, even if the TransferDelegate plugin has been approved to a PDA. This limitation prevents the marketplace from fully managing the Core asset.
I need the TransferDelegate to function similarly to the FreezeDelegate, where the owner cannot revoke it once it has been approved to a PDA and is frozen.
Has the team already addressed this issue, or is there an alternative approach to ensure the marketplace can handle Core assets without owner interference?
The text was updated successfully, but these errors were encountered:
I am currently working on an escrowless NFT marketplace utilizing Core assets. I've identified a potential issue where the owner of a Core asset can remove
TransferDelegate
plugin using RemovePluginV1 at any time, even if theTransferDelegate
plugin has been approved to a PDA. This limitation prevents the marketplace from fully managing the Core asset.I need the
TransferDelegate
to function similarly to theFreezeDelegate
, where the owner cannot revoke it once it has been approved to a PDA and is frozen.Has the team already addressed this issue, or is there an alternative approach to ensure the marketplace can handle Core assets without owner interference?
The text was updated successfully, but these errors were encountered: