A proposal to manage NFT by the user’s smart contract wallet, which provides a new way to manage assets, utilizes the programmability of the smart contract wallet, and also provides more playability.
EOA wallet has no state and code storage, and the smart contract wallet is different.
AA is a direction of the smart contract wallet, which works around abstract accounts.
The smart contract wallet allows the user’s own account to have state and code, bringing programmability to the wallet. We think there are more directions to expand. For example, NFT asset management, functional expansion of NFT transactions, etc.
The proposal aims to achieve the following goals:
-
Assets are allocated and managed by the wallet itself or plugins. such as approve , which are configured by the user’s contract wallet, rather than controlled by the NFT asset contract, to avoid some existing ERC-721 contract risks.
-
Add the nftTransfer function, the transaction initiated by the non-smart wallet itself or will verify the approves.
-
The user wallet itself supports approve. Add nftApprove, nftGetApproved, Used to approve specify one asset under the nft contract.
-
add nftSetApprovalForOneAll, nftIsApprovedForOneAll, Used to approve specify all assets under the nft contract.
-
add nftSetApprovalForAllAll, nftIsApprovedForAllAll, Used approve for assets under all nft contracts.
-
The users can choose to add hook function before and after their nftTransfer to increase the user’s more playability
-
The user can choose to implement the nftReceive function