//Alex Mizrahi: Some Crazy Facts About Chromia

Alex Mizrahi: Some Crazy Facts About Chromia

You can do a hard-fork in about a second. Some people joke that e.g. EOS and Ethereum are doing many hard-forks per minute. Chromia can actually do it. Quite plausibly you can do e.g. 10000 hard-forks a day. Only the blockchain code is subject to an automatic hard-fork, the framework code needs to be updated manually, so people might argue that these aren’t really “hard-forks” in a traditional sense. But given that blockchain code controls pretty much everything about blockchains, and system blockchains can be updated this fast too, I’d say it’s good enough.You can spawn a new blockchain in seconds. Want to spawn a million blockchains? You can do that on Chromia. Maybe. We haven’t actually optimized for running millions of blockchains yet, so actually trying to run a million is likely to run into a perf issue of some sort. But running e.g. a hundred shouldn’t be a problem.Hard-fork policies can be controlled using high-level language. “Hard forks”, which we actually call “blockchain configuration updates”, are controlled by a directory blockchain. The directory blockchain is itself implemented in Rell like any other blockchain in Chromia. Thus you can implement any policy, e.g. “do a hard fork only if everyone agrees”. These governance policies can be implemented in relatively few lines of code and in a very readable way, so bad code concerns are absolutely minimal. So assuming a good governance policy can be described in English, it can be implemented in Chromia.More information on Chromia is available via the link:Official Website: www.chromia.comWhitepaper: https://ift.tt/2PXDEz9 dApps: https://ift.tt/32Sp2FP https://ift.tt/2KvkP4t https://twitter.com/teamchromiaTelegram: https://ift.tt/31cmu4u

  1. You can do a hard-fork in about a second. Some people joke that e.g. EOS and Ethereum are doing many hard-forks per minute. Chromia can actually do it. Quite plausibly you can do e.g. 10000 hard-forks a day. Only the blockchain code is subject to an automatic hard-fork, the framework code needs to be updated manually, so people might argue that these aren't really "hard-forks" in a traditional sense. But given that blockchain code controls pretty much everything about blockchains, and system blockchains can be updated this fast too, I'd say it's good enough.
  2. You can spawn a new blockchain in seconds. Want to spawn a million blockchains? You can do that on Chromia. Maybe. We haven't actually optimized for running millions of blockchains yet, so actually trying to run a million is likely to run into a perf issue of some sort. But running e.g. a hundred shouldn't be a problem.
  3. Hard-fork policies can be controlled using high-level language. "Hard forks", which we actually call "blockchain configuration updates", are controlled by a directory blockchain. The directory blockchain is itself implemented in Rell like any other blockchain in Chromia. Thus you can implement any policy, e.g. "do a hard fork only if everyone agrees". These governance policies can be implemented in relatively few lines of code and in a very readable way, so bad code concerns are absolutely minimal. So assuming a good governance policy can be described in English, it can be implemented in Chromia.

More information on Chromia is available via the link:

Official Website: www.chromia.com

Whitepaper: https://chromia.com/documents/Chromia-_-Platform-white-paper2019.pdf

Programming dApps: http://rell.chromia.com/en/master/ https://try.chromia.dev/

Twitter: https://twitter.com/teamchromia

Telegram: https://t.me/hellochromia