Uniques V2 Roadmap 2022 (Tracking Issue)

[jsidorenko]

Goals

The main goal is to apply the best standards we currently have in the NFTs space while keeping the pallet as generic as possible.

Roadmap

Changes to the existing core (Uniques V1):

• auto-incremental collections ids (Nfts: Fix Auto-Increment #12223)
• new approvals structure (Discussion thread) (Nfts: Multiple approvals #12178)
• feature flags (bitflags) [Uniques V2] Feature flags #12367
• nested ownership (Discussion thread)
• support tips when buying an NFT ([Uniques V2] Tips #12168)

New features:

• new minting methods (Discussion thread) [Uniques V2] Minting options #12483
• Atomic NFTs swap [Uniques V2] Atomic NFTs swap #12285
• smart attributes (as described here) [Uniques V2] Smart attributes #12702 [NFTs] Update attributes with offchain signature #13390
• multi-assets support
• new methods to sell NFTs with off-chain signatures (Discussion thread)
• basic support for marketplace functionality (Discussion thread) ([Uniques V2] Basic marketplace functions #12189)

Nice to have:

• refactor roles (extract into a separate data store) [Uniques V2] Refactor roles #12437
• extract logic into features/[feature].rs files [Uniques v2] Refactoring #12570
• advanced claiming options (Merkle tree claims, claims with the off-chain signature) [NFTs] Offchain mint #13158
• support 1155 token standard NFTs fractionalization #12565

[Szegoo]

What would the new approvals structure exactly be? Could you please provide a bit more details on that? Is there a document where these tasks are a bit more detailed?

[jsidorenko]

What would the new approvals structure exactly be? Could you please provide a bit more details on that? Is there a document where these tasks are a bit more detailed?

Sure, I've created multiple topics in the Discussions section to discuss the ideas and approaches. Once we come to a common agreement, we would start the implementation.
The tasks above were updated with the links to the appropriate discussion threads.

[Polkadot-Forum]

This issue has been mentioned on Polkadot Forum. There might be relevant details there:

https://forum.polkadot.network/t/uniques-pallet-nfts-september-update/410/2

[JayPavlina]

What is multi-assets support?

Also, I saw smart attributes mentioned in the forum, but I don't see it here. It would be interesting to see your approach to access control with attributes.

I also don't find tips intuitive to understand. How do they relate to royalties?

[Polkadot-Forum]

This issue has been mentioned on Polkadot Forum. There might be relevant details there:

https://forum.polkadot.network/t/uniques-pallet-nfts-september-update/410/4

[shawntabrizi]

@JayPavlina tips is an opt-in approach to royalties, rather than building royalties, and knowing that users can bypass it easily using things like wrapping the token.

In this case, there is still a way for an original NFT creator to get paid some portion of a sale, which is via the TIP feature. You can imagine, if you buy any NFT on a platform which supports tips, they will make sure that the final purchase transaction handles the TIP amount, and the artist is paid. Obviously this is something that needs to be supported by the platform, but this is already true for enforcement of royalties

[jsidorenko]

@JayPavlina Multi-assets support is the ability to specify the price for your NFT in a non-native token.
No dex or conversion between tokens will be supported. If you set the price in USDC, then it will be possible to buy that NFT with USDC only.

Re smart attributes, I'll add them to the roadmap. Thanks for the heads up!

[takahser]

Can you include support for SFTs (semi-fungible tokens, which are supported in EIP-1155) in the roadmap as well? Major NFT marketplaces have been supporting it for a while already.
If not for this release, at least for the subsequent one?

[jsidorenko]

I'll put it into Nice-to-have section for now. I think we should merge the new pallet into the master once we get the opened pull requests ready + the smart attributes implemented. After that, we could start to gather feedback and think about the next wave of improvements

[evilrobot-01]

The mint call/dispatchable currently requires an item to be specified, which could lead to transactions failing with AlreadyExists in a hyped public mint which sells out in seconds. Perhaps consider adding an option which allows items to be automatically assigned based on a requested quantity, to allow minting more than one item in a single transaction. This may also require mint limits per transaction and transaction limits per mint phase tho, depending on mint mechanics.

PS - There also currently does not seem to be a way to determine how many items have been minted (CollectionDetails.items) from another pallet, which could be used to determine the next item identifier to use with the current api.

[Polkadot-Forum]

This issue has been mentioned on Polkadot Forum. There might be relevant details there:

https://forum.polkadot.network/t/statemint-update-roadmap/1200/1

[Polkadot-Forum]

This issue has been mentioned on Polkadot Forum. There might be relevant details there:

https://forum.polkadot.network/t/polkadot-release-analysis-v0-9-37/1736/1