ens VS flow-nft

While creating these tutorials, I choose Ethereum Name Service as an example, because it's a famous project, and quite frankly, also because I take these changes to study some subjects I am interested in (sue me! 😛).

> I hope this idea catches on

This already exists with Ethereum Name Service (ENS) https://ens.domains and Sign-in With Ethereum.

One of the first applications of blockchains was DNS. (Namecoin) ENS is a modern form. (https://ens.domains)

I would say there's still some degree of centrality for ENS, but it is more decentralized than DNS.

DNS - ENS + LIMO

"Launch censorship-resistant decentralised websites with ENS. Upload your website to IPFS and access it with your ENS name."

Thanks, don't let these dorks discourage you. Pointing to websites is one of the first use cases mentioned on https://ens.domains. It links here: https://medium.com/the-ethereum-name-service/cloudflare-and-fleek-make-ens-ipfs-site-deployment-as-easy-as-ever-262c990a7514

In this example, we use the ExampleNFT contract to create a basic functionality where any account that wants to receive an ExampleNFT must have a collection.

This usually refers to code or data that lives on the blockchain. It can be stateful or not. When minting an NFT, for instance, there is usually a variable on the smart contract that is incremented to record the total supply. The incrementing of the variable is happening 'on-chain'. In the case of Flow, we can easily store data in smart contracts or even within digital assets like NFTs. It works kind of like this – all NFTs on Flow implement the Flow Non-Fungible Token standard. The NFT itself is just a block of code that conforms to that standard. In addition to the requirements of the NFT standard you can store other data inside as well. So if the NFT represents something like a ticket to an event, then that block of code is where you have an opportunity to store things like an image of the ticket or other metadata like the event name, performers, and so on. It's up to the developer to implement what else goes there in addition to the Flow NFT standard requirements. Adding these 'extra' things to the NFT or a smart contract – things that are meaningful to the experience you're trying to build – are also part of what we colloquially refer to as 'on-chain'.

I thought that was still in ideation phase[1].

[1]https://github.com/onflow/flow-nft/issues/9

AngelHack is proud to announce that we're partnering with Tribe to host this online 6-week hackathon is designed to bring together the brightest creators and innovators from around the globe to challenge boundaries in the world of blockchain technology. Join us from September 20 - October 31, 2021, together with the experts from Filecoin, IPFS & Flow for Developer Hour sessions, technical workshops, and a whole lot of adventure and fun.