You are viewing a single comment's thread from:

RE: We Need A Hundred Forks Of The Steem/Hive Code Over Time

in Threespeak - OLD4 years ago

100 new forks is technically possible. More competition is great.

I just want to make sure we're not talking about forking Steem and/or Hive, with all the account history 100 times. That is theoretically possible, but not practical.

If everyone forks their own chain like that (with account history x100), do they continue to work on the previous fork? Do they work on all of them? In some cases, it means 100 times the work, prima facie.

Not always. Sometimes a tool can be designed to work on all 100, if it's well designed. Sometimes an app can also work on all 100, also if it's well designed.

But if there's 100 forks, that at least implies 100 times the blocklogs. I think at some point, a block signer would only pick one or two forks to run. Most certainly, someone running a full (fat) RPC node would only run on one fork at most because the costs are too high.

So if one one person will run one full node per fork, even if there's 100 different people doing that, this represents the main limiting factor in app deploy.

Realistically, there would not be 100 full nodes on each fork. Realistically, there would only be one fork, perhaps two forks out of the 100 forks that would receive a full node.

There are 5,000 crypto-projects. Hive managed to avoid being ranked 5001. That was not luck.