DC - Decentralized cloud

Ecosystem
1

The project aims to provide a decentralized cloud service for Web3.0 applications that surpasses the current limitations of Web3.0 application scenarios, delivering high performance, high concurrency, low barriers to development, and an enhanced user experience.

  • problems
    Current Web3.0 applications are primarily based on the smart contract model on the blockchain, which has very limited application scenarios:

    1. Performance Bottlenecks of Smart Contracts: Taking Ethereum as an example, the current TPS (transactions per second) of Ethereum is only about 30. This means that only about 30 transactions can be processed per second, which is unacceptable for most web2.0 applications.
    2. Web3.0 applications implemented with blockchain-based smart contracts face bottlenecks in storage and retrieval. Although there are now some relatively mature storage-oriented chains, such as Filecoin, Arweave, and Crust from the Polkadot ecosystem, access and retrieval of data on these chains are still hard to achieve in real-time due to the performance bottlenecks and design patterns inherent in blockchain technology.
    3. The Development Threshold of Smart Contracts: Currently, the development of smart contracts is mainly based on specific languages, such as ink! which undoubtedly increases the learning cost for developers and raises the threshold for development. Moreover, the development model of smart contracts is entirely different from the traditional web2.0 application development model, which is also unacceptable for most web2.0 developers.
    4. The Account Model of Current Web3.0: The account model of current smart contracts is primarily based on a public-private key system, which requires users to safeguard their private keys or mnemonic phrases. This is difficult for most web2.0 users to accept.
    5. Whether it’s a blockchain operating on a Proof of Stake (PoS) or Proof of Work (PoW) consensus mechanism, finalizing a block always requires a certain amount of time. This means that the user experience of Web3.0 applications cannot compete with that of Web2.0 applications, which is a primary reason why current Web3.0 applications struggle to attract more users.

  • solution
    Unlike the existing blockchain model that uses smart contracts to provide services for Web3.0 applications, DC enables decentralized capabilities without the need for Web3.0 applications to invoke smart contracts on the blockchain. It supports a wider range of application scenarios and also possesses higher performance. A brief introduction is as follows:

    • To address performance and storage bottlenecks, DC has made several improvements:
      1. The DCChain public blockchain, developed based on Substrate, inherits the NPoS (Nominated Proof of Stake) model from Polkadot. Compared to the PoW (Proof of Work) model, it ensures the transaction processing performance of the blockchain to a certain extent.
      2. Transactions that would typically be submitted to the blockchain by Web3.0 applications are instead submitted by cloud service nodes. This way, as soon as a Web3.0 application receives a response from a cloud service node, it signifies that the business logic has been successfully processed. The cloud service nodes are responsible for ensuring that transactions requiring consensus are recorded on the blockchain according to corresponding strategies. This guarantees that Web3.0 applications can offer a high-response user experience.
      3. If all consensus actions were to be recorded on the blockchain, the performance and storage bottlenecks on the blockchain would still exist; it would merely shift the problem from the application’s client side to the cloud service node side. DC addresses this issue by introducing local consensus among cloud service nodes to replace the global consensus of the blockchain, eliminating the need to record non-globally essential consensus data on the blockchain, because most business logic does not require consensus to be formed on the blockchain. Below, we will expand on this by using the decentralized database provided by DC as an example:
        1. When an application creates a database, the cloud service node submits information such as the relationship between the database and the user, as well as the storage capacity limit of the database, to blockchain.(Global consensus)
        2. The DC network randomly selects n (currently n is 5) cloud service nodes to store the database’s data and records the relationship between the database and each cloud service node onto the blockchain. (Global consensus)
        3. Every cloud service node that has stored the database will keep track of the database’s capacity usage and synchronize this information with each other. (Local consensus)
        4. When an application maintains table structures or records within the database, the cloud service nodes storing the database will locally accumulate the used capacity of the database and compare it with the storage capacity limit of the database recorded on the blockchain. If the limit is not exceeded, they will directly accept the data and synchronize it with other cloud service nodes that have backed up the database. All nodes that have backed up the database will locally accumulate the used capacity of the database. (Local consensus)
        5. If a cloud service node finds that the database capacity has exceeded the storage capacity limit set on the blockchain, it will refuse to provide service. (Local consensus)
        6. When the application receives feedback from the cloud service nodes indicating insufficient database capacity quota, it guides the user to increase the quota for the database, and the cloud service nodes facilitate the process of recording the increase onto the blockchain. (Global consensus)
        7. If a cloud service node that has backed up the database fails, the DC network will automatically find another available cloud service node to perform the backup and update the list of relationships between the database and cloud service nodes on the blockchain. (Global consensus)
        8. Summary: Applications only form a global consensus on the blockchain when creating databases, configuring database capacity, and updating the location of cloud service nodes that store the database. Frequent operations such as table structure management, data insertion, modification, and deletion do not require blockchain transactions. During these processes, the actual business data that needs to be stored does not need to be recorded on the blockchain either. This ensures the interactive performance of the application and addresses the issue of high storage costs on the blockchain.
      4. In response to the issue of high entry barriers for developers of web3.0 applications based on smart contracts, DC provides a complete set of gRPC interfaces as well as client SDKs covering mainstream programming languages. This allows developers to leverage their existing experience and habits to develop web3.0 applications just as they would develop web2.0 applications, without the need to understand blockchain technology. Developers can simply refer to the interfaces provided by DC to rapidly develop web3.0 applications.
      5. In terms of user guidance, in addition to the mnemonic phrase and the public-private key account system, DC has also introduced an account mode similar to web2.0. This means that users can log in across terminals, applications, and devices just by using an account and password. The advantage of this approach is clear: users familiar with web2.0 can transition to web3.0 users without understanding blockchain, decentralization, or public-private key cryptography. This has milestone significance for the long-term development of web3.0.

  • vision
    To break through the situational limitations of Web3.0 applications, lower the development threshold for Web3.0 applications, and eliminate barriers for users entering the Web3.0 world, thereby rapidly promoting the development of Web3.0 applications.

  • Ecosystem Fit

    The current blockchain mostly provides services to developers through smart contracts, with a few also offering storage services. However, there is currently no blockchain like DC that provides cloud services for web3.0 applications (including file storage, real-time interaction with decentralized databases, decentralized social protocols, and message caching services). Additionally, DC can be called by other parachains through XCM.

    • Use Cases

      • Dapps that require data storage
      • Dapps that require p2p communication
      • Dapps that require real-time interaction with decentralized databases
      • Dapps that require decentralized social protocols
      • Dapps that require decentralized message caching
      • Dapps that require decentralized user account systems
      • Dapps that require Peer-to-peer user communication routing
      • Dapps that require blog and comment functions like twitter

    • Integration of the ecosystem
      DC’s goal is to provide a user experience for web3.0 applications similar to that of web2.0 applications, and to support a wider range of use cases. It also aims to ensure high performance, high concurrency, and low development thresholds for web3.0 applications. This goal cannot be achieved by other chains, so DC is an independent project that will not conflict with other projects.

    • DC will bring explosive growth in user scale to the Web3.0 ecosystem, mainly based on the following points:

      • By providing decentralized, high-performance, and high-concurrency cloud services, it breaks the limitations of application scenarios for web3.0 applications.
      • Allow web2.0 users to use web3.0 applications while retaining the user experience.
      • By providing SDKs covering mainstream programming languages and standard GRPC interface calling services, it eliminates the learning and development costs for application developers, fostering more web3.0 applications.
      • Users between applications are interoperable, eliminating the need for repeated registration, thus creating a virtuous cycle of “more applications → more users → more applications”.

    • The DC network itself focuses solely on the construction of decentralized cloud services. In order to ensure the performance and purity of its functions to the greatest extent, it does not provide smart contract functionality. However, we are working to integrate the DC network as a parachain into Polkadot. If developers need to, they can access various distinctive features on other pa ras through cross-chain access. Our goal is to introduce more daily applications with non-financial attributes (such as storage, blogging, social networking, and IoT access) as Web3.0 applications. When these applications require financial attributes or other distinctive functionalities, they can call the functionalities on other chains within the Polkadot ecosystem through XCMP messaging.

    • In general, we aim to onboard the majority of current Web2.0 users into the Polkadot ecosystem. At the same time, we will also need the distinctive features of various parachains within the Polkadot ecosystem to better provide more comprehensive decentralized services for developers and users of applications based on the DC network.

The development of the DC network start at the end of 2020. We have launched the public test network. For more details, please visit the project website: https://www.dcnetio.cloud.
We have also developed a decentralized “Chain Album” mobile application based on DC network, with web2.0 user experience.
Scan to download Ios app:
iosen下载地址

Scan to download Android app:
android链册下载地址

2

Whether we admit it or not, with the development of the BTC L2 ecosystem, the attractiveness of Polkadot to developers and users in the financial ecosystem is expected to decrease significantly. I have always been very fond of the Polkadot concept and believe it is a very correct path. Polkadot should shift its focus slightly away from existing blockchain users and concentrate on attracting more traditional Internet users to enter the Web3.0 ecosystem, and then guide these users into the Polkadot ecosystem, whether it is finance-related or otherwise. Therefore, after nearly 4 years of effort, we have built the DC network based on Substrate, primarily addressing the following issues:

  1. We have eliminated the performance and storage bottlenecks for Web3.0 applications, allowing DC-based Web3.0 applications to cover various business scenarios of the traditional Internet.
  2. We enable traditional Internet application developers to develop Web3.0 applications based on their traditional development experience, business design patterns, and development languages, which can be based on smart contracts or decentralized cloud services.
  3. We have removed the barriers for traditional Internet users to use Web3.0. While ensuring security, we enable them to use Web3.0 applications without needing to understand public and private keys, mnemonic phrases, and wallets.

Lastly, you can scan the QR code to download the “Chain Album” app and experience it. This is a serverless mobile app based on the DC network, where users have complete control over all their data and can use the same account across multiple devices simultaneously.