I recently became a web3 developer and created Flovatar (flovatar.com) and I totally agree with all the issues outlined in this article, but I think they are mostly limited to the Ethereum ecosystem and because most projects are not thinking outside the box and using IPFS to store the images.
In my case I decided to build it on the Flow blockchain (flow.com) and to use SVG illustrations and I couldn’t be happier about both choices.
Flow provides a JS library to interact with the blockchain without the need to use browser plugins like Metamask and also allows to store data on-chain with really affordable costs.
Having the SVG stored in the NFT guarantees that all the issues outlined in the article won’t apply in my case and will be guaranteed to exist as long as the blockchain will live (unlike IPFS where someone actually has to keep paying for the servers to store the images).
I could go on by saying that I managed to build a Marketplace that handles 500k$/month transactions with a single and relatively simple smart contract. Doing that in a web2 way would have been much much harder to both implement and maintain.
So from my perspective all the problems outlined in the article are super valid, but if you look a bit outside the current “standards” of the Ethereum world there is definitely hope and lots of solutions available.
In my case I decided to build it on the Flow blockchain (flow.com) and to use SVG illustrations and I couldn’t be happier about both choices.
Flow provides a JS library to interact with the blockchain without the need to use browser plugins like Metamask and also allows to store data on-chain with really affordable costs.
Having the SVG stored in the NFT guarantees that all the issues outlined in the article won’t apply in my case and will be guaranteed to exist as long as the blockchain will live (unlike IPFS where someone actually has to keep paying for the servers to store the images).
I could go on by saying that I managed to build a Marketplace that handles 500k$/month transactions with a single and relatively simple smart contract. Doing that in a web2 way would have been much much harder to both implement and maintain.
So from my perspective all the problems outlined in the article are super valid, but if you look a bit outside the current “standards” of the Ethereum world there is definitely hope and lots of solutions available.