architecture-docs
architecture-docs copied to clipboard
rchain
Comparison Table TPS Statement
RE: https://github.com/rchain/architecture-docs/blob/master/introduction/comparison-of-blockchains.rst
In the "Scalability/Transaction Throughput" row, I think a better distinction should be made between what a "COMM" event is and what a "transaction" is. At RCon3 there was a clarification over the network throughput for test net. It was stated that the aim of RChain was 40K+ COMM events/second - not transactions. I think it's important to distinguish between these two things, as COMM events are atomic. It's important to note that [Single COMM Event != Single Token Transaction].
Comm events certainly are atomic. They fit the definition of transaction to a T:
... ACID as shorthand for Atomicity, Consistency, Isolation, and Durability... . These four properties describe the major guarantees of the transaction paradigm, which has influenced many aspects of development in database systems.
We could clarify the distinction between comm events and token transfers, which are calls to the BasicWallet.rho contract.
I've written up such a distinction for an article summarizing testnet performance. We can reuse it here too.
