ERC 721 Enumerable: OpenZeppelin Solidity implementation

3:57 Enumerating tokes by address
12:14 Token transfers in ERC 721 Enumerable
18:26 Why ERC 721 Enumerable matters
OpenZeppelin's ERC 721 Enumerable interface is an optional interface that allows enumerating the tokens owned by an address.
In this video, I walk through the OpenZeppelin code to explain how the interface works.
github.com/Ope...

[@hantony5361]

Great explanation, quickly points out the key points of the ERC721 Enumerable and shows helpful examples along with the effects on the data structure. Besides that the considerations of different scenarios also expand my thoughts.

[@dimitarbochvarovski4356]

Great explanation! Something like this for ERC20 Snapshot would be very helpful :D

[@sefatuncer3285]

Thanks for great explanation. It is very helpful..

[@konstantinschwemlein2809]

Thank you again! You are a big help :)

[@nikosc]

Excellent video. Technical with great examples. Thank you

[@МихаилБегунов-б8с]

Thank you very much for your effort!

[@seskamol]

cool channel man thanks

[@reyesdani84]

super helpful, thanks!

[@BlockchainBob]

hi Daniel, I'm happy to hear that =)

[@eltucangaming8332]

Very clear thanks for sharing

[@BlockchainBob]

Thank you for supporting the channel! Feel free to let me know if you have any suggestions for other video ideas =)

[@johnj.rivers7318]

Hi!very helpful video!i have a question: what if i want to combine this extension with uristorage?is it sufficient to extend this and copy paste the implementations uristorage implements(but i guess i don't need Counter)

[@BlockchainBob]

I think a faster approach would be to use the OpenZeppelin wizard to choose the extensions you want. The wizard will automatically combine extensions (and deduplicate common classes/interfaces) for you. docs.openzeppelin.com/contracts/4.x/wizard

[@johnj.rivers7318]

@@BlockchainBob thx again, that worked like a charm. One final question though, do you perhaps know how this enumerable extension work with burning the tokens?does it correctly update data structures or will it break something?

[@rodrigota7432]

great work sir, thanks

[@brandonfowler1592]

Awesome brotha! Great job. So in fact it is our job to ultimately maintain the list as far as the gap is concerned? Correct? Basically, dependent on the use case, 9 out 10 times we are going to transfer and allow our users to exchange tokens. So we will be the ones to swap the transferring token to the back once we've locked-on the particular token we want to transfer (via our our smart contract.) I do have a question or better yet I would like to get a fellow devs opinion. I'm creating a type of CMS and I was wondering what you recommend as far as NFT standards are concerned? ERC721 or 1155? I'm thinking it might be a better bet to go with 1155, It's been a minute since I read the 1155 standard (I'm going to have to go back and study it, I took a little dev break for nearly a month now.) If I remember correctly, 1155 doesn't handle the same way. Correct? Before my little break I was heading towards use of 1155 because I wouldn't have to maintain the in the same way. That's besides the point that it's a newer standards with more functionality (NFT and Fungible features). I will be implementing my own JSON Metadata standard too for my project. So, just FYI, no real need to adhere to ERC721 for compatibility reasons between platforms. This will for the most part be an independent platform (non-art function) I'm more so interested in using because of the decentralized nature of the blockchain tech. Any suggestions, thoughts, or opinions on the matter would be amazing. Thank you for the awesome information, I really do appreciate your thorough break-down.