[Proposal] :Next generation ID should not be content dependent

CID is currently depending on the content.
It makes the ID hard to predict when we don’t know the content.
If people can predict the future ID that means it’s possible to sense when the next state is up, which enables a bunch of possibility, to allow clients and users to become aware of the new objects and trust that this is what they are after because only they can generate the id

(post deleted by author)

(post deleted by author)

Using arbitrary names to refer to a piece of data is effectively how URLs already work. IPFS has something that tries to do something similar which is IPNS, though it could definitely use more work.

In practice, content dependent IDs are a major feature of IPFS with their immutability being their greatest strength and their greatest weakness. The fact that IPFS is content-addressed means that you know that requesting the same CID multiple times will give you the exact same data every time. It also because possible to verify the data since its identifier is also its hash that it can be checked against. Using mutable data with a fixed identifier would remove these strengths. In fact, IPNS is so slow largely because it can’t use the guarantees provided by normal CIDs. It can’t take advantage of the fact that the data will never change, so it has to worry about whether or not what it already has is out of date, which is hard to check because of the decentralized nature of the network.

(post deleted by author)

no body cares anyways