@VladZamfir@VitalikButerin @aparnalocked @Evans_obiwuru@jamiepitts How about consider scalability from another aspect? e.g. Compositionality (RhoCalculus's RhoMachine A + RhoMachine B = RhoMachine C) it is born with sharding naturally.
@amrithoney@zilliqa 3. The class of useful programs that can't be written without unbounded recursion, i.e. in a non-TC language in the context of smart contracts is probably non-existent.
@amrithoney@zilliqa 2. The pdf says RhoVM runs contract with "the parallelism at the node level", and that is totally wrong. Rholang breaks up the contract into processes, which run concurrently on multiple nodes. It is quite like AKKA's actor.
@amrithoney@zilliqa 1. I am not saying PoS is better, each consensus gets its pros/cons and the best area to fit. It is biased to say PBFT is better than PoS in a public chain as you at least ignored PBFT communication‘s quadratic growth by node number.that's a serious problem in public chain.
@zilliqa The comparision betw @zilliqa and @rchain_coop is not the truth.
1. pBFT is better than PoS in public chain?
2. Rholang contract is made up with processes executing concurrently on network!
3. Zilliqa's non-Turing-complete lang is better than Turing-complete?
falsehood!