Poor performance and developer experience on public chains
Performance, often measured through the Transactions Per Second (TPS) benchmark, is one of the main limitations limiting public chain adoption. Paypal Payment Solutions Corporation is currently operating with around 100TPS while Visa, a multinational financial services group, can process up to 2000TPS1. In contrast, Bitcoin and Ethereum can only handle about 10 TPS2. The difference in scalability between centralized and decentralized platforms has hindered the development of blockchain payment applications while also preventing the mass adoption of payment DApps.
With the continuous development of DApps, the volume of on-chain data is increasing rapidly, leading to a relentless inflation of the total cost of resources, and has significantly limited the growth of the public chain. Citing an example, EOS RAM usage is currently around 62%3 and has affected the usability of some DApps built on the EOS platform. Concurrency issues cannot be solved by relying solely on Protocol Layer Smart Contracts to store DApp4 data.
There is also the issue of Trilemma5 Scalability, whereby the requirements for decentralization, scalability and security cannot be satisfied with the existence of opportunity costs. This means that public chains cannot improve performance without ignoring some aspect of decentralization or security. Faced with this situation, DIGITAL - HI TECH (DHT) has proposed an alternative method to improve scalability through the development of βSmart Pipelineβ technology, similar to the Layer 2 solution, to improve scalability. batch data processing.
Last updated