You are viewing a single comment's thread from:

RE: HIVE Could Face a Massive Class Action Lawsuit for Intellectual Property Theft

in #hivelast year (edited)

Funny. You know what? I don't want to steem hold my intelectual content. I'm gonna sue steem/it.

Steem has no my permission to hold, view or publish my content.

I hope it is clear.



You can create Hard fork and remove your posts

I don't believe you can though.

I'm not familiar with how STEEM blocks might differ, but in a PoW system like Bitcoin, you cannot fork to remove historic data. That historic data is built into the hashes and part of what chains every block together. If we decided "Let's exclude post #1231 from 10K blocks ago", that block would have a different hash, which would ripple through every block after it. You would no longer be able to validate the last 10k blocks, the fork would have had to have occurred 10k blocks ago.

The fork is as of last week, therefore we split as of last week. History up until that point is the same, because STEEM is HIVE and HIVE is STEEM. They were one chain, then at version 22.5 some witnesses say "Version 23 has X updates" and other witnesses say "Version 23 has Y updates" Its why you can go see the HIVE witnesses on STEEM and the STEEM witnesses on HIVE, both systems still detect the others witnesses as being valid consensus nodes running different versions than their respective top 20 are running.

Everyone needs to stop making claims they know nothing about. I'm a DApp developer and blockchain researcher, my thesis was on taking blockchain and DAG tech and trying to retrofit it to power MMO's instead of a coin, and I am sitting here thinking "Whether we can or can't do these things is determined by the structure of a block and unless STEEM did it very different than it isn't possible". If I don't know what we can and can't do without taking a dive on my own, I am positive that most users won't know either. I don't even think the new Steemit Inc. knows enough about the system they purchased to make that decision. As far as I'm aware, only the witnesses and other devs working on core/working with core code would know enough to make that call. Random users in comment sections are probably not qualified.

Generally, you can do this in Bitcoin (Hard Fork), but the community doesn't want them. Hard Fork is a violation of consensus, community division, and tragedy in general. In my opinion the reason is simple - Bitcoin is a big network, so censorship (like in Hive) will not pass.