Non Fungible Token (NFT) Standard [Community Consideration]

[benny]

I’m currently drinking from a crypto firehouse (or maybe a blockchain dump truck) and trying to absorb as much as I can. I entered crypto with a casual investment interest. Since discovering IC, I’m now engaged with a developer interest. After listening to Dominic’s interview recently on the Epicenter poscast I knew this was something different (good listen…their was contention/curiosity w/ the hosts trying to imply as-is blockchain technology to IC).

I’m trying to interpret as much as I can from this thread, and the token standard thread, and ending up with some doubt regarding the current handful of NFTs on IC.

Consumers of these NFTs are assuming the (blockchain) implementation is comparable to Ethereum (others). Though given the below references, it seems we’re a dfx command (malicious update, stop, delete) away (via canister owner) from validating the authenticity of what’s currently in circulation.

I’m wondering if anyone else shares these thoughts, or maybe I haven’t fully appreciated the conversations/develops docs yet.

https://forum.dfinity.org/t/how-does-the-storage-mechanism-in-dfinity-works/2733/6

@kpeacock

The state is stored in memory and managed through consensus. In Motoko, it’s as simple as assigning it to a stable variable. Calls simply are not transactions, and there won’t be a list of transactions for your canister unless you choose to add one for your particular use case.

Immutability (Read-Only Code)

@ililic

Due to canisters having an ability to be upgraded over time, there exists a possibility that the API of a canister as well as its underlying implementation may change at any time. This is different from other blockchain environments where contracts are immutable upon deployment and upgrade paths require re-deployment and migration of state.

As a result, there exists the potential for malicious token implementers to deploy a canister that seems benign at first but then upgrade the canister at some later date to some implementation that is not to the end users’ expectations, or which manages to steal funds or do other harm to consumers of the canister.

https://sdk.dfinity.org/docs/developers-guide/working-with-canisters.html

If you want to permanently delete a specific canister or all canisters for a specific project on a given Internet Computer network, you can do so by running the dfx canister delete command.

Deleting a canister removes the canister identifier, code, and state from the Internet Computer network.