This problem originally came from users of PRESSone, but it is actually a common problem in the blockchain+content industry.

PRESSone CTO's answer is as follows:

Huo Ju's words are concise, and programmers may have understood it when they see it here.

As for friends who don't know so much about technology, they still don't know what to do. Share my understanding here. If there is any deviation, please comment and correct me.

When using blockchain technology to serve the content industry, it will involve a key issue:

Is the content on the chain?

In the implementation of PRESSone, the content is not uploaded, but the hashed content is uploaded. As we all know, even if a content simply changes punctuation, the hash after re-hashing will be different.

But the fact is that users will always encounter the situation of article modification and picture adjustment. Although the article/picture has been modified, it is still the article/picture from the user's point of view.

What should be done to solve the above contradictions?

Not satisfying users? This is not right.

Make the unbreakable blockchain network "modifiable"? Very bad.

Below, I use Huo Ju's answer to speculate how PRESSone will realize content modification. Once again, in the PRESSone network, digital content is not directly entangled, but hashed.

Take an article as an example.

When PRESSone opens the function entrance of "Modify Content and Re-submit Signature" to users through the web or app, and users can use it as needed, the following situations will occur:

At this point, there are two versions in the chain, A and B.

When a user visits an article on a PRESSone website or application, PRESSone will show the user the latest version.

In this way, from the user's point of view, PRESSone meets the requirements of content revision. From the perspective of PRESSone, it is just a version of association and pointing.

Can you understand me when I say this?