Are NFT standards future-proof? Here is a generic solution for token mechanism

Hi! I would like to get the opinion of some of you on this idea that I have been working on. I believe that the rise of contract-based accounts will lead to the need to replace NFT standards and fungible tokens, because many of their limitations or difficulties can be better solved by user configuration. For instance, you now have to approve each marketplace as an operator on every NFT contract you want to sell, but it would be more convenient for the account to have a user-defined permissions setting that marketplaces and NFT contracts can access.

On the other hand, I have done several projects that operate with tokens and I got tired of having to re-implement the logic for each standard type, which are usually 6 that I use (ERC20, ERC721, ERC1155, LSP7 and LSP8). It makes more sense to me to abstract the functionality of the tokens in a single controller so that developers can use the same code for any token.

And that’s what I did, a client to use tokens in a generic way. I think is interesting, not just to save time developing, but because it’s an elegant way to separate the decision of which standard you support, from the implementation itself, giving your token mechanisms the ability to be token agnostic and future-proof.


Can you take a look at it and give me feedback or tell me what you think or give it a star if you like, please?

View Source

Categories NFT

2 thoughts on “Are NFT standards future-proof? Here is a generic solution for token mechanism”

Leave a Comment