Dev Log (Day 14)

"https://" sucks, but "Ipfs://" is confusing

I'm trying to write an NFT deployment script in Python. One of the limitations of Algodot (Algorand SDK in Godot engine) is that it cannot currently produce NFT'S in the engine although it can create asset tokens. Tbh, It doesn't affect gameplay much as I feel creating NFT'S in python isn't so hard once there's a template for it in place.

Today, I finished setting up an in game wallet and now for today, I want to deploy an NFT, parse it's .Json meta data in game, get the image Url, then download the linked image from the Url.

https:// sucks

Ipfs:// is confusingAnyone that says NFT'S are just expensive jpegs has never done any bit of research on the technology behind them.

NFT'S are image meta data hosted on

ipfs:// and https:// web servers

The meta data which is stored on the Blockchain, contains links to the NFT'S image url.

The technology is immensely complex and I'm talking as a builder. I've used GDscript, Python, Rust, and teal, 4 programming languages just to create an NFT experience. It looks simple from a casual user's perspective, but beneath the veneer, the technology behind it is complex.

Finally set up a https:// web server and I can mint NFT'S to it, even though my web browser throws up this warning sign in the images above. Next, I'll be minting an NFT, parsing the NFT'S meta data and then I'll download the image from within Godot, using the NFT'S meta data. The image's are illustrations done for an old competition. They're placeholders images for the final NFT'S